Bug 30377 - [WinPhone] DisplayAlert and DisplayActionSheet don't await
Summary: [WinPhone] DisplayAlert and DisplayActionSheet don't await
Status: RESOLVED DUPLICATE of bug 27119
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 1.4.2
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Eric Maupin
URL:
Depends on:
Blocks:
 
Reported: 2015-05-22 22:59 UTC by Adam
Modified: 2015-05-26 16:41 UTC (History)
3 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 27119

Description Adam 2015-05-22 22:59:24 UTC
When you change the MainPage on a Windows Phone App, the DisplayAlert and DisplayActionSheet not longer await for the response.

Many other people have this issue to -
http://forums.xamarin.com/discussion/30952/displayactionsheet-windows-phone-problem

Some more information on my issue in the forums here -
http://forums.xamarin.com/discussion/38579/await-displayalert-not-blocking
Comment 1 Adam 2015-05-25 00:08:26 UTC
Just for additional clarification. You set the MainPage initially when the app loads. If you then change the MainPage once again, while the app is running, that is when this issue occurs.
Comment 2 Eric Maupin 2015-05-26 16:41:41 UTC

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