Bug 56709 - PushAsync completes before pushed page is dismissed
Summary: PushAsync completes before pushed page is dismissed
Status: RESOLVED NOT_ON_ROADMAP
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 2.3.4
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2017-05-21 19:29 UTC by Edward Brey
Modified: 2017-06-09 12:42 UTC (History)
1 user (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 NOT_ON_ROADMAP

Description Edward Brey 2017-05-21 19:29:57 UTC
The return value documentation for INavigation.PushAsync is "A task representing the asynchronous dismiss operation." Based on this, I was expecting that awaiting the returned task from VisualElement.Navigation.PushAsync would wait until the pushed page was popped or otherwise dismissed. However, instead VisualElement.Navigation.PushAsync completes immediately. The behavior should match the interface contract.
Comment 1 Jason Smith [MSFT] 2017-06-02 00:59:41 UTC
Which platform are you experiencing this on?
Comment 2 Edward Brey 2017-06-02 17:00:32 UTC
I only tried on UWP, which I test on first because debugging is so much faster. When it didn't work there, I hacked in a workaround, so I haven't tried the other platforms.
Comment 3 Edward Brey 2017-06-02 17:01:02 UTC
.
Comment 4 Jason Smith [MSFT] 2017-06-08 21:19:37 UTC
I believe this happens on UWP because we dont actually have a mechanism by which we can actually monitor the completion of the transaction. Until either we find a mechanism to track this or the underlying toolkit adds a way to do it, this will remain unfixed.
Comment 5 Edward Brey 2017-06-09 12:42:16 UTC
Please at least correct the documentation in the meantime.