Bug 22564 - WinPhone App Bar Buttons not respecting the current page in Master/Detail set up.
Summary: WinPhone App Bar Buttons not respecting the current page in Master/Detail set...
Status: RESOLVED FIXED
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 1.2.2
Hardware: PC Windows
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2014-09-02 09:00 UTC by Kevin.Murray
Modified: 2016-03-16 12:27 UTC (History)
6 users (show)

Tags: windows masterdetailpage
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 FIXED

Description Kevin.Murray 2014-09-02 09:00:40 UTC
If you use the Xamarin Mobile CRM example:

1. Click the Master button.
2. Click Leads.
3. Click List tab.
4. Click entry.
5. On detail entry screen, click Master button.
6. Pick anything other than Leads...screen stays the same.  Back button doesn't work.
7. Click Master then Leads again.
8. Click Back button.
9. Everything back to normal again.

This only occurs on Windows Phone.
Comment 1 Rui Marinho 2015-05-27 10:44:21 UTC
We'd be happy to help you resolve this issue. Please help us by attaching a reduced reproduction to the bug by starting with a clean Xamarin.Forms project and adding just the code necessary to demonstrate the issue. If you'd do this for us we would very much appreciate it. If you are able to reproduce the issue without modifying the platform specific projects that would eliminate a number of possibilities and likely expedite a resolution. 

Warm regards,
Xamarin Forms Team
Comment 2 Jason Smith [MSFT] 2016-03-16 12:27:42 UTC
Thank you for taking the time to submit this report. After reviewing the description of this bug, we no longer believe it affects the current version of Xamarin.Forms. If you are still experiencing the issue after updating your packages, please reopen this report with an attached reproduction.
 
For your convenience, we have created some reproduction best practices viewable here: https://gist.github.com/jassmith/92405c300e54a01dcc6d

Warm regards,
Xamarin Forms Team