Hello Thomas,

After thorough investigation, it appears to be an issue in latest Xamarin update. In our recent test, we simply created an empty Xamarin iOS project (even without any references to Crosslight), change the device target to iPhone 5s 7.1, then hit Run. This simple blank app crashed, similar the symptom you described.

Could you please test the empty iOS project and run it in your Mac? See if it encounter such issue. If that's the case, we'll be contacting Xamarin to report this issue.

UPDATE: Xamarin apparently crashed only when the iOS 7.1 project is located in /Library folder where Crosslight library and samples are located. If you moved out the sample project to Documents folder or somewhere in the current user folder, the sample works fine. Make sure a full clean and rebuild have been performed prior to running the sample.

Hope this helps. Thanks!

Hello Thomas,

An updated installer is now available for download. Please download the Mac setup again from the same download link.

Please update how it goes in your end.

Thanks!

Hello Thomas,

Here's a hotfix build that address the iOS 7.x issues including improvements to Navigated event consistency between 7.x and 8.x, as well as the truncated Post button fix.

Simply update the iOS assembly to the bin folder of the installation, as well as any Packages folder in your project, if any.

Please update how it goes in your end.

Hope this helps.

Thanks for reporting the iOS 7.x specific issues. The truncated Post button appears to be an issue due to the recent iOS 8 support. We will address the issue quickly in the next update.

Dear Leo,

Yes, Crosslight supports composite view scenario since its data binding is built specifically for each view component. In your case, your view can have any number of list controls such as table view and collection view. Of course, you will have to register different ID for each of your view using the RegisterViewIdentifier method in the code behind of your view controller (you'll find this in most of our samples).

In your ViewModel, you need to have the property that represent the datasource for each list control. For instance, your ViewModel can have these properties:

public IList<Album> HotAlbums {  ... }

public IList<Album> EditorPicks { ... }

Finally, make sure you bind these properties to the correct target ID in the binding provider. At the most minimum, you will need to bind the ItemsSource property and ItemBindingDescription property.

Hope this helps.