Bug 30521 - Setting ParentActivity On Forms Causes Seems to Break Up Navigation
Summary: Setting ParentActivity On Forms Causes Seems to Break Up Navigation
Status: RESOLVED NOT_ON_ROADMAP
Alias: None
Product: Forms
Classification: Xamarin
Component: Android ()
Version: 1.4.3
Hardware: PC Mac OS
: Normal enhancement
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2015-05-27 17:23 UTC by Jimmy [MSFT]
Modified: 2016-04-09 00:27 UTC (History)
2 users (show)

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


Attachments
Repro Project (51.22 KB, application/zip)
2015-05-27 17:23 UTC, Jimmy [MSFT]
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:
RESOLVED NOT_ON_ROADMAP

Description Jimmy [MSFT] 2015-05-27 17:23:22 UTC
Created attachment 11361 [details]
Repro Project

*** Overview ***
If a Forms activity has a ParentActivity set, pressing the up button will navigate back to the parent activity, even if there are pages in the Form activity’s navigation stack.


*** Steps to Reproduce ***
1. Run the attached repro project
2. Press “Go to Forms Activity”
3. Press the app icon to navigate “up”
4. Press “Go to Forms Activity”
5. Press “Open Page 3”
6. Press the up button again


*** Actual Results ***
When the up button is pressed in Page3, it navigates back to the native activity, skipping Page2 in the navigation stack.


*** Expected Results ***
If there are other pages in the navigation stack, the up button should navigate back to those. This behavior can be seen by pressing the back button on Page3.


*** Environment Info ***
=== Xamarin Studio ===

Version 5.9.2 (build 2)
Installation UUID: 94ce5106-6a72-4691-b34e-cd5857b1db66
Runtime:
	Mono 4.0.1 ((detached/11b5830)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 400010043

=== Apple Developer Tools ===

Xcode 6.3.1 (7703)
Build 6D1002

=== Xamarin.iOS ===

Version: 8.10.1.59 (Business Edition)
Hash: 13d1cdc
Branch: master
Build date: 2015-05-18 22:54:57-0400

=== Xamarin.Android ===

Version: 5.1.2.0 (Business Edition)
Android SDK: /Users/jimmygarrido/Library/Developer/Xamarin/android-sdk-macosx
	Supported Android versions:
		2.3   (API level 10)
		4.0.3 (API level 15)
		4.1   (API level 16)
		4.4   (API level 19)
		5.0   (API level 21)
Java SDK: /usr
java version "1.7.0_71"
Java(TM) SE Runtime Environment (build 1.7.0_71-b14)
Java HotSpot(TM) 64-Bit Server VM (build 24.71-b01, mixed mode)

=== Xamarin Android Player ===

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

=== Xamarin.Mac ===

Version: 2.0.1.59 (Business Edition)

=== Build Information ===

Release ID: 509020002
Git revision: 43735a4b905b571f69cf9428a3ea7b52aef55476
Build date: 2015-05-18 09:38:12-04
Xamarin addins: ab18ddff45f507ed74f36c2b65df9aee22e28a56

=== Operating System ===

Mac OS X 10.10.3
Darwin Jimmys-MacBook-Pro.local 14.3.0 Darwin Kernel Version 14.3.0
    Mon Mar 23 11:59:05 PDT 2015
    root:xnu-2782.20.48~5/RELEASE_X86_64 x86_64
Comment 1 Jason Smith [MSFT] 2015-05-27 20:16:33 UTC
We don't currently support this
Comment 2 Jason Smith [MSFT] 2016-04-09 00:27:28 UTC
Thank you for your report. At this time there are no plans to implement any changes around this issue.

Warm regards,
Xamarin Forms Team