Bug 25555 - DisplayAlert behaves differently when using back button
Summary: DisplayAlert behaves differently when using back button
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 1.3.0
Hardware: PC Windows
: Normal normal
Target Milestone: 1.3.5
Assignee: Bugzilla
Depends on:
Reported: 2014-12-21 07:52 UTC by Niels
Modified: 2015-02-18 08:17 UTC (History)
5 users (show)

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:

Description Niels 2014-12-21 07:52:08 UTC
The following code behaves differently on Android and WP when using the back button:

var proceed = await DisplayAlert("Proceed?", "Would you like to proceed?", "Yes", "No");

1) Android returns false when backbutton is pressed = OK
2) WP returns true when backbutton is pressed = Not OK
Comment 1 Ram Chandra 2015-01-08 08:22:04 UTC
I have checked this issue but I am unable to reproduce this issue.

Could you please provide a sample application and build info(Xamarin Forms + XVS)? So that we can reproduce this issue at our end.

You can get build information form here:
Visual Studio => Help => About Microsoft Visual Studio => Copy Info

Comment 2 Jason Smith [MSFT] 2015-02-13 15:34:27 UTC
Should be fixed in 1.3.5-pre1