Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
Created attachment 25484 [details]
Small app to show bug
I get always blank page when i try to resume my app(after minimizing). This behaviour occurs only after an update of forms to 2.4.
Steps to reproduce:
- Update app to latest 2.4
- Run app
- Minimize app
- Run app again(resume)
- Admire blank page
Attached app with 2.3.X.
The project doesn't appear to reproduce the issue on an API 21 emulator or an S8 device. Can you provide more info about the device or emulator you're using or if there's some other step missing?
Attached project works fine. I let it on FF2.3.X to show how it should work. You have to upgrade this project to FF2.4.280(for example) and then it should not more work
Okay, for some reason before it wasn't doing it; maybe caching issues.
I cannot reproduce this with version 188.8.131.52863. Please update and let us know if it is still a problem. Thanks!
No. The problem is not solved. Try following steps to reproduce:
- Download my app atached
- Compile and deploy(this version will work)
- uninstall app on test device
- uninstall forms in solution via nuget manager
- install newest 2.4.X
- Compile and deploy
When will it be fixed? I need an estimation for my chief.
I suspect that this was working before by virtue of a memory leak that kept the page fragments alive even though the pages were disposed by Android on minimize.
I recommend that you use something more like this:
nav = new NavigationService();
SimpleIoc.Default.Register<GalaSoft.MvvmLight.Views.INavigationService>(() => nav);
nav = (NavigationService)SimpleIoc.Default.GetInstance<GalaSoft.MvvmLight.Views.INavigationService>();
var navPage = new NavigationPage(new Views.LoginPage());
MainPage = navPage;
This will ensure that you are providing your MainPage and NavService with a live set of fragments.
Let me know if you have any further issues! Thanks!
In my example app there is only one view to simplify my issue. In my prod app there are a lot of views. The line:
"av = (NavigationService)SimpleIoc.Default.GetInstance<GalaSoft.MvvmLight.Views.INavigationService>();" makes possible that i navigate back to last used view. In your solution this else-part makes no sense. Your proposal/solution is also always to navigate to login-view? Sorry but that is a bad joke.
My proposal was simplified to reflect the reproduction.
You can keep track of what view you want to navigate back to, but you must recreate the view. You can't reuse the same dead renderer.