Bug 23429 - Issue with PopModalAsync
Summary: Issue with PopModalAsync
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 1.2.3
Hardware: PC Mac OS
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
URL: https://github.com/xamarin/Duplo/issu...
Depends on:
Reported: 2014-09-27 00:21 UTC by Cody Beyer (MSFT)
Modified: 2015-08-18 02:41 UTC (History)
7 users (show)

Tags: android crash navigation
Is this bug a regression?: ---
Last known good build:

TestCase (5.76 MB, application/zip)
2014-09-27 00:21 UTC, Cody Beyer (MSFT)

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 Cody Beyer (MSFT) 2014-09-27 00:21:42 UTC
Created attachment 8214 [details]

Clicking one option on a modal page does not disable the other option while the animation completes, and can cause a fatal exception if the other option is hit.

For example, using the attached app

1: Build App
2: Click Push Modal Async button franticly 
3: Continue to click things with much haste
4: Observe app fail with following error: [MonoDroid] System.InvalidOperationException: The underlying Task is already in one of the three final states: RanToCompletion, Faulted, or Canceled.
Comment 1 Sadik Ali 2014-09-29 04:55:56 UTC
I have checked this issue with the steps mentioned in bugs description and I am able to reproduce this issue.

I observed that when I click on "PushModalAsync" button continuously, I am getting following exception:

"UNHANDLED EXCEPTION:System.InvalidOperationException: The underlying Task is already in one of the three final states: RanToCompletion, Faulted, or Canceled."

Screencast: http://www.screencast.com/t/Ysw5Q837

Application output:https://gist.github.com/saurabh360/1e3d66171e29d58096e6
Adb logs:  https://gist.github.com/saurabh360/417953f0bcce7275fe05

Environment Info:


=== Xamarin Studio ===

Version 5.5 (build 222)
Installation UUID: 6ea47b0d-1852-4aaf-808d-373ff0a5002b
	Mono 3.10.0 ((detached/ac51002)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 310000016

=== Apple Developer Tools ===

Xcode 6.0.1 (6528)
Build 6A317

=== Xamarin.iOS ===

Version: (Business Edition)
Hash: a1f0a7a
Build date: 2014-09-27 22:06:24-0400

=== Xamarin.Android ===

Version: 4.18.0 (Business Edition)
Android SDK: /Users/jatin66/Desktop/Backup/android-sdk-macosx
	Supported Android versions:
		1.6   (API level 4)
		2.1   (API level 7)
		2.2   (API level 8)
		2.3   (API level 10)
		3.0   (API level 11)
		3.1   (API level 12)
		3.2   (API level 13)
		4.0   (API level 14)
		4.0.3 (API level 15)
		4.1   (API level 16)
		4.2   (API level 17)
		4.3   (API level 18)
		4.4   (API level 19)
Java SDK: /usr
java version "1.7.0_65"
Java(TM) SE Runtime Environment (build 1.7.0_65-b17)
Java HotSpot(TM) 64-Bit Server VM (build 24.65-b04, mixed mode)

=== Xamarin.Mac ===

Version: (Business Edition)

=== Build Information ===

Release ID: 505000222
Git revision: dae37674f8a41572a91bf0e14c098d15e03d0a53
Build date: 2014-09-26 14:15:04-04
Xamarin addins: bab982129fe7697d3c639fa713751ab29305a257

=== Operating System ===

Mac OS X 10.9.5
Darwin Jatin66s-iMac.local 13.4.0 Darwin Kernel Version 13.4.0
    Sun Aug 17 19:50:11 PDT 2014
    root:xnu-2422.115.4~1/RELEASE_X86_64 x86_64
Comment 2 Rui Marinho 2015-05-28 15:02:38 UTC
Hi this doesn't seem to be a bug in Forms, in theory its possible for the button to get 2 click events before we ever get the interrupt for the first one.