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 17951 [details]
Environment (Word) and solution to reproduce the issue
I'm developing a Xamarin.Forms PCL App for Android, iOS and UWP.
I use the normal NavigationPage to manage the navigation stack.
In Xamarin.Forms 220.127.116.11 everything runs well: Pressing the Back Button on a child page
will return to the previous page (on all platforms).
After updating from Xamarin.Forms 18.104.22.168 to 22.214.171.124 there seems to be a breaking change
for UWP Apps: Now i have to press the Back Button twice to return to the previous page.
For Android and iOS everything runs well as in version 126.96.36.199.
This behaviour is not acceptable.
What changes have been made in UWP navigation ???
To reproduce the issue, i'm sending you a solution as an attachement.
I have reduced the code and pages to the essentials.
I have invested some time to analyse the issue. Now i'm able to reproduce the bug from scratch. The error occurs when navigating from a ListView-Item (via event "ItemSelected") to the next page. The same issue occurs after displaying an alert (via event "ItemSelected"). At latest from the second time, you have to press the Back-/OK-button twice to return to the previous page.
I have created a simple VS2015 solution to reproduce the issue (see second attachment). On Android and iOS everything works as expected.
What am I doing wrong???
Created attachment 17979 [details]
Solution from scratch to reproduce the bug
*** This bug has been marked as a duplicate of bug 44886 ***