-
Notifications
You must be signed in to change notification settings - Fork 1.9k
[Bug] - XF 5 CarouselView PeekAreaInsets crashing #14311
Comments
Hi, @Pandu-V - thanks for submitting this issue. I tested with our CarouselView samples, and wasn't able to reproduce the issue. Which version of XF 5 exactly are you experiencing this on? And on which devices/platforms? |
Hi Team, I have this issue only on iOS[All phones] when we set PeakAreaInsets property in CarouselView for XF v5.0.0.2. |
Hi, @Pandu-V - would you be able to share a sample? I just tested again on an iOS device, with XF 5.0.0.2, but wasn't able to reproduce any issues |
Tried but cannot reproduce the issue. Could you attach a small sample? |
I still have this bug in version 5.0.0.7775 of Xamarin Forms |
Just hit this myself. UIKitCore error message is: MonoTouchException: Objective-C exception thrown. Name: NSInternalInconsistencyException Reason: negative sizes are not supported in the flow layout. In my case, I was experiencing this when PeekAreaInsets was set > 0 AND the view was also rotated around the Y-axis, which is common enough in animations. |
Maybe linked to #15191 |
I'm having a similar problem with the CarouselView. If set PeekAreInsets I get the following failure: *** Assertion failure in -[Xamarin_Forms_Platform_iOS_CarouselViewLayout _getSizingInfosWithExistingSizingDictionary:], UICollectionViewFlowLayout.m:1501 |
@rachelkang facing the same issue with XF 5.0.0.2012 only on iOS. I tried to set it after page load without success. I tried with the CarouselViewDemos sample and it's actually working fine. It's really annoying as it's a nice UI feature and having it completely crashing the app was not expected.. |
Looks like it's not gonna be handled anytime soon, used collectionview instead it looks similar... |
Description
Steps to Reproduce
.
Expected Behavior
CarouselView with PeekAreaInsets should work
Actual Behavior
Crashing while using PeekAreaInsets in CarouselView
Basic Information
Environment
Show/Hide Visual Studio info
Build Logs
Screenshots
Reproduction Link
Workaround
The text was updated successfully, but these errors were encountered: