-
Notifications
You must be signed in to change notification settings - Fork 172
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PopPageModel crash on iOS #307
Comments
I had the same problem. Due the urgency to solve the problem, the solution was drop it from the project. |
I'm now running into a similar problem, however this is with a CollectionView on the page. The page is a TabbedPage, navigated to using a new navigation service. Upon closing the page the following is called:
XF: 4.8.0.1269
|
I having the Same issue with collection View on XF 5 |
I'll add myself to the list of people affected by this bug. I am showing a very simple CollectionView, with an ItemsSource and a SelectedItem, and there is something going on when the bindings are removed in iOS (having a selected item). The weird thing: if I pop the page to go back to the previous page in the modal navigation service:
It works perfectly. But if I close the modal navigation using:
The page crashes (only in iOS), with a "IItemsViewSource is empty" error message. Using FreshMvvM 4.0.1 and Xamarin.Forms 5.0.0.2083 |
For what is worth, I've ended up doing this as a workaround, until this bug is fixed (either in FreshMvvm or XF, because I don't really know which one is causing it):
Not ideal (to say the least), but PopToRoot, just as PopPageModel, works without crashing, and the modal navigation disappears fast enough in iOS that the first page in the modal navigation is barely visible (and kind of makes sense in my particular case). |
here is the problem sample
I push page in Modal mode
await CoreMethods.PushPageModel<myPage>(mydata, true, true)
the same for pop page
await CoreMethods.PopPageModel(true, true);
but its crash with that error on iOS platform only
IItemsViewSource is empty
could you fix that bug on
iOS 13.4.1
the whole error for more details
The text was updated successfully, but these errors were encountered: