Bug 39548 - CarouselPage does not work in UWP on Windows 10 Mobile
Summary: CarouselPage does not work in UWP on Windows 10 Mobile
Alias: None
Product: Forms
Classification: Xamarin
Component: Windows ()
Version: 2.0.0
Hardware: PC Windows
: Normal major
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2016-03-11 12:40 UTC by blitzillu
Modified: 2016-04-26 17:52 UTC (History)
3 users (show)

Tags: ac
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 blitzillu 2016-03-11 12:40:40 UTC
You can take the code sample from https://developer.xamarin.com/api/type/Xamarin.Forms.CarouselPage/. If you try to swipe through the pages it doesn't do anything. On the simulator you get some arrows, but they are not available on Windows 10 Mobile.

Problem was also noticed by another user (see https://forums.xamarin.com/discussion/62236/carouselpage-does-not-work-in-uwp-on-windows-10-mobile-and-has-bugs-under-uwp).
Comment 1 blitzillu 2016-03-21 10:13:30 UTC
Seems that this has been fixed in Xamarin.Forms 2.1.0
Comment 2 Parmendra Kumar 2016-04-26 17:52:08 UTC
I ma not able to reproduce this issue with Xamarin.Forms 2.2.0-pre4.

Hence closing this issue.