Bug 38744 - RemovePage breaks Navigation Stack
Summary: RemovePage breaks Navigation Stack
Status: RESOLVED DUPLICATE of bug 37462
Alias: None
Product: Forms
Classification: Xamarin
Component: Android ()
Version: 1.5.1
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2016-02-14 12:15 UTC by khasan
Modified: 2016-02-15 00:30 UTC (History)
5 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:
Status:
RESOLVED DUPLICATE of bug 37462

Description khasan 2016-02-14 12:15:22 UTC
I have following page navigation:  Page 1 > Page 2 > Page 3 > Page4. I want jump back from Page4 to Page2. For that I remove Page3 from navigation stack and call PopAsync from within Page4 but I get blank page instead of Page2. 
This works in Xamarin.Forms version 1.4.4.63.92 but stop working in any 2.* version
Comment 1 khasan 2016-02-14 13:40:06 UTC
Also note that it happens in Android application and only if I apply New Material design. If my MainActivity derives from FormsApplicationActivity instead of FormsAppCompatActivity then everything works ok
Comment 2 Paul DiPietro [MSFT] 2016-02-15 00:30:44 UTC

*** This bug has been marked as a duplicate of bug 37462 ***