This repository has been archived by the owner on May 1, 2024. It is now read-only.
Android crash from FrameRenderer caused by VisualElementPackager #5614
Labels
e/2 🕑
2
good first issue
help wanted
We welcome community contributions to any issue, but these might be a good place to start!
i/high
Completely doesn't work, crashes, or is unusably slow, has no obvious workaround; occurs less often
inactive
Issue is older than 6 months and needs to be retested
p/Android
t/bug 🐛
up-for-grabs
We welcome community contributions to any issue, but these might be a good place to start!
Description
When I use CarouselView inside a ListView (where each cell has its own carousel view), it crashes in an Android emulator with the following exception:
Full stack trace
When I debugged it using a local Xamarin.Forms nuget package built from the latest master, I noticed that the children of the CarouselView (
newChildren
) were not in the same order as the corresponding renderers (_childViews
) in theVisualElementPackager.SetElement
method, which caused the FrameRenderer to be applied to the ContentView that resulted in this exception.The image below illustrates this issue, where the Frame-based arrow controls and the indicator are the last 3 children, while their (frame) renderers are the first 3 elements in the _childViews.
Do you have any ideas on what's causing this, and how it can be fixed?
Note: This issue has been reported in the corresponding CardView repository, and the author agreed that it seems to be a Xamarin.Forms bug.
Steps to Reproduce
Expected Behavior
The form should scroll through items without crashing.
Actual Behavior
After some swiping the app crashes with the exception above.
Basic Information
The text was updated successfully, but these errors were encountered: