Bug 31077 - Navigation Page Removal and Push
Summary: Navigation Page Removal and Push
Status: RESOLVED FIXED
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 1.4.2
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2015-06-12 14:02 UTC by rhicks
Modified: 2016-04-10 00:25 UTC (History)
4 users (show)

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


Attachments
Bug Project (4.44 MB, application/x-zip-compressed)
2015-06-15 11:28 UTC, rhicks
Details


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 FIXED

Description rhicks 2015-06-12 14:02:57 UTC
Manipulating the NavigationStack (by calling RemovePage and InsertPageBefore several times) and PopAsyncing the last page works as expected, it navigates back to the desired page. However, attempting to PushAsync any other pages onto the stack after that results in a blank screen. There doesn't seem to be a problem with pushing this new page onto the stack, just displaying the contents of the page once there. No exceptions are thrown, nor are there any errors in the Android Device Log.
Comment 1 rhicks 2015-06-15 11:28:23 UTC
Created attachment 11604 [details]
Bug Project

During the creation of this test project, I found two other bugs. Therefore this project will showcase three bugs in total:

1) After manipulating the NavigationStack and PopAsync the last page to land on a different page than the root, any further PushAsync calls do not cause any exceptions, but the UI of the next page is never rendered - even though the Title in the Navigation bar does change appropriately.

2) After encountering the above bug, using the "Back" button in the Navigation bar to navigate back to the root result in the root page not matching the original setting.

3) This bug is reproduced by performing the same steps required to reproduce 1 above, with the only difference being that a slightly different manipulation is completed on the NavigationStack (only one call to InsertPageBefore is completed). When this bug is encountered it appears as if the page is never Popped from the NavigationStack, and the UI is never updated appropriately.
Comment 2 alemarko 2015-07-07 05:43:19 UTC
Problem is still here in 1.4.3.6374.

This makes 'InsertPageBefore()' unusable for navigation.
Comment 3 Jason Smith [MSFT] 2016-04-10 00:25:05 UTC
Thank you for taking the time to submit this report. After reviewing the description of this bug, we believe it no longer affects the current version of Xamarin.Forms. If you are still experiencing the issue after updating your packages, please reopen this report with an attached reproduction.
 
For your convenience, we have created some reproduction best practices viewable here: https://gist.github.com/jassmith/92405c300e54a01dcc6d

Warm regards,
Xamarin Forms Team