Bug 31266 - Navigation stack corrupted when user taps quickly
Summary: Navigation stack corrupted when user taps quickly
Status: VERIFIED FIXED
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 1.4.2
Hardware: Macintosh Mac OS
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2015-06-20 07:02 UTC by BillF
Modified: 2017-01-11 12:58 UTC (History)
7 users (show)

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


Attachments
Simple app demonstrating the problem (177.23 KB, application/zip)
2015-06-20 07:02 UTC, BillF
Details
Diagnostic from a very similar, as yet unfiled bug (185.57 KB, image/png)
2015-06-20 07:21 UTC, BillF
Details


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:
VERIFIED FIXED

Description BillF 2015-06-20 07:02:28 UTC
Created attachment 11697 [details]
Simple app demonstrating the problem

The attached sample app BugTest allows you to navigate up and down a stack of four pages. Everything goes well if you tap the buttons at a normal speed. However if you make an effort to tap buttons very quickly, one after the next, the navigation stack gets messed up.

To reproduce the problem (I used iPhone5 for this):

1. Navigate to the Groups page.
2. Tap the Group A button then as quickly as you possibly can, tap the Groups button at top left to return to the Groups page.
3. Repeat step 2 several times.

You will now find that the button on the Initial page is labelled "Group A" instead of "Page 2" and only two of the four pages are now reachable.

I discovered this when (unsuccessfully) trying to write a sample app to demonstrate another bug, not yet filed. Could be related though, will cross-link.
Comment 1 BillF 2015-06-20 07:21:04 UTC
Created attachment 11698 [details]
Diagnostic from a very similar, as yet unfiled bug

I mentioned another bug, not yet filed. It is reproduced in a very, very similar way by tapping fast, going back and forth between my Groups page and Group page. I can reproduce that one in my full app but not in a simple app. This screenshot, for interest, shows the diagnostic from this other, still-unfiled bug.

"Popped page does not appear on top of current navigation stack, please file a bug"
Comment 2 Rajneesh Kumar 2015-06-30 09:43:49 UTC
I have checked this issue and able to reproduce this as per described in bug description. But I am not sure about the issue mentioned in the comment 1. To reproduce this issue I have followed the steps and instruction provided in bug description.

Steps I followed:
1. Open attached test sample in XS.
2. Build and deploy the application in iPhone 5 device.
3. Navigate to the Groups page.
4. Tap the Group A button then as quickly as you possibly can, tap the Groups
button at top left to return to the Groups page.
5. Repeat step 2 several times.

I observed that if I make an effort to tap buttons very quickly, one after the next, the navigation stack gets messed up, however it works fine if I performed taping slowly.

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

Ide Logs: https://gist.github.com/Rajneesh360Logica/dc821eb5969c90abd992
Application Output: https://gist.github.com/Rajneesh360Logica/f722a4d5e500aeb1eabe
Device Logs: https://gist.github.com/Rajneesh360Logica/b826b62955265acc3d59

Environment Info:

=== Xamarin Studio ===

Version 5.9.4 (build 5)
Installation UUID: 011d70a5-dede-428b-ab04-ef451c2e539d
Runtime:
	Mono 4.0.2 ((detached/c99aa0c)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 400020005

=== Xamarin.Android ===

Version: 5.1.4.16 (Business Edition)
Android SDK: /Users/MM/Desktop/android-sdk-macosx
	Supported Android versions:
		2.3    (API level 10)
		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)
		4.4.87 (API level 20)
		5.0    (API level 21)
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 Android Player ===

Version: Unknown version
Location: /Applications/Xamarin Android Player.app

=== Apple Developer Tools ===

Xcode 6.2 (6776)
Build 6C131e

=== Xamarin.iOS ===

Version: 8.10.2.39 (Business Edition)
Hash: 4e8928a
Branch: master
Build date: 2015-06-29 11:03:42-0400

=== Xamarin.Mac ===

Version: 2.0.2.39 (Business Edition)

=== Build Information ===

Release ID: 509040005
Git revision: 8010a90f6e246b32364e3fb46ef2c9d1be9c9a2b
Build date: 2015-06-08 16:52:06-04
Xamarin addins: 7e93e9c3503f28770f23ce1b7eafd829919f18e8

=== Operating System ===

Mac OS X 10.9.5
Darwin MacMini.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 3 BillF 2015-07-02 21:11:57 UTC
This bug was no longer exercised when I changed my app to disable  each button until its processing was completed. So I am no longer pursuing it. But might affect other people.
Comment 4 BillF 2015-07-02 21:13:23 UTC
In Comment 3 I was referring to the 'similar' bug mentioned in Comment 1.
Comment 5 Jimmy [MSFT] 2017-01-10 18:33:21 UTC
This issue appears to be resolved.

I was able to reproduce the original issue in comment 0 with Forms 1.3.3. However after updating to Forms 2.3.3, I can navigate between the pages and the navigation stack maintains its order.