Bug 28626 - Using carousel on android will not work with anything but index 0
Summary: Using carousel on android will not work with anything but index 0
Status: RESOLVED DUPLICATE of bug 29257
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 1.4.2
Hardware: All All
: Normal normal
Target Milestone: ---
Assignee: Rui Marinho
Depends on:
Reported: 2015-04-01 08:03 UTC by William
Modified: 2015-08-20 07:48 UTC (History)
6 users (show)

Tags: ios functionality
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description William 2015-04-01 08:03:29 UTC
I have attached a sample project that shows the problem.  With Xamarin forms, on android, the carousel page will not work correctly with anything but index 0.  If you select from the a list view an index that is not the first one, you will get a blank screen.

It works as expected on an iPhone.
Comment 1 William 2015-04-01 08:04:10 UTC
Attachment failed to save might be too big
Comment 2 Jason Smith [MSFT] 2015-05-21 21:40:16 UTC
Can you please provide a smaller reproduction case if your current one is too big?
Comment 3 Rui Marinho 2015-08-20 07:48:44 UTC
Dupe of #29257

*** This bug has been marked as a duplicate of bug 29257 ***