[Bug] [UWP] Regression bug on CollectionView included in FlyoutPage.Detail #15356
Comments
@YZahringer I know it has been a while, but still wanted to ping you to see if you maybe have an idea on this one :) |
@jfversluis I think the regression is caused by the As commented, I had my doubts in the past about this, but the memory leak persisted otherwise. A possible way to solve this regression and avoid the memory leak, would be to assign a new |
So... can this be tested or will we have to remain on the old version forever? |
@jfversluis & @YZahringer |
Any ETA for fix? |
@shajiraghav Do you have any example code I could reference for your work around? I'm having this issue in a production project and would like to update to the latest build, but can't because of this issue on UWP |
Hello, To make my apps responsive I usually put a ScrollView in my content pages, and put a grid in the scroll view. Then I use this pattern I picked up somewhere on the internet:
I call the above in |
Description
Service Release 9 (5.0.0.2337) introduced a regression that leads to an exception/crash on UWP whenever we revisit a view that contains a CollectionView.
We use a FlyoutPage in our mainpage and whenever we present a FlyoutPage.Detail with a CollectionView for the second time, it will crash with a stacktrace containing the lines
Downgrading to Service Release 8 (5.0.0.2291) eliminates the crash.
We suspect the regression was introduced with PullRequest 14780 since it includes a check for StructuredItemsView
Steps to Reproduce
Expected Behavior
FlyoutPage renders the content, including all CollectionViews
Actual Behavior
Crash with "System.NotImplementedException: The layout is not implemented"
Basic Information
Reproduction Link
Please see the attached reproduction project
UWPCollectionViewNavigationCrash.zip
Workaround
Downgrade to Service Release 8 (5.0.0.2291)
The text was updated successfully, but these errors were encountered: