Bug 36658 - [Android] TabbedPage Displays Last Tab's Content For All Child Pages
Summary: [Android] TabbedPage Displays Last Tab's Content For All Child Pages
Status: RESOLVED FIXED
Alias: None
Product: Forms
Classification: Xamarin
Component: Android ()
Version: 2.0.0
Hardware: PC Mac OS
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2015-12-06 19:36 UTC by Jimmy [MSFT]
Modified: 2016-10-25 16:08 UTC (History)
1 user (show)

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


Attachments
repro project (54.04 KB, application/zip)
2015-12-06 19:36 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 FIXED

Description Jimmy [MSFT] 2015-12-06 19:36:40 UTC
Created attachment 14136 [details]
repro project

### Overview
A TabbedPage on Android is showing the wrong child page after being navigated to. For each tab, it is always displaying the last child page instead.

However, the issue seems to only occurs with this scenario:

- An MasterDetailPage’s Detail is set to a Page
- The Detail page is replaced by a NavigationPage
- The NavigationPage pushes a TabbedPage


### Steps to Reproduce
1. Run attached Android project
2. Click “Show List” button
3. Select “First Claim”


### Expected Results
The TabbedPage is pushed and the first child page is displayed.


### Actual Results
The TabbedPaged is pushed, but the first and second tabs display the same page as the third. However, the titles in the tabs are correct so only the page content is incorrect.


### Environment Info
=== Xamarin Studio ===

Version 5.10.1 (build 3)
Installation UUID: 94ce5106-6a72-4691-b34e-cd5857b1db66
Runtime:
	Mono 4.2.1 (explicit/6dd2d0d)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 402010102

=== Xamarin.Profiler ===

Version: 0.24.0.0
Location: /Applications/Xamarin Profiler.app/Contents/MacOS/Xamarin Profiler

=== Apple Developer Tools ===

Xcode 7.1.1 (9081)
Build 7B1005

=== Xamarin.iOS ===

Version: 9.2.1.54 (Business Edition)
Hash: eb4c1ef
Branch: master
Build date: 2015-12-01 02:12:30-0500

=== Xamarin.Mac ===

Version: 2.4.0.109 (Business Edition)

=== Xamarin.Android ===

Version: 6.0.0.34 (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)
		5.1   (API level 22)
		6.0   (API level 23)

SDK Tools Version: 24.4.1
SDK Platform Tools Version: 23.0.1
SDK Build Tools Version: 22.0.1

Java SDK: /usr
java version "1.7.0_79"
Java(TM) SE Runtime Environment (build 1.7.0_79-b15)
Java HotSpot(TM) 64-Bit Server VM (build 24.79-b02, mixed mode)

=== Xamarin Android Player ===

Version: 0.6.5
Location: /Applications/Xamarin Android Player.app

=== Build Information ===

Release ID: 510010003
Git revision: f2021a209d66d49cbc0649a6d968b29040e57807
Build date: 2015-12-01 10:43:40-05
Xamarin addins: dfd4f5103e8951edbc8ac24480b53b53c55e04ff
Build lane: monodevelop-lion-cycle6-baseline

=== Operating System ===

Mac OS X 10.11.1
Darwin Jimmys-MacBook-Pro.local 15.0.0 Darwin Kernel Version 15.0.0
    Sat Sep 19 15:53:46 PDT 2015
    root:xnu-3247.10.11~1/RELEASE_X86_64 x86_64
Comment 1 Jimmy [MSFT] 2015-12-06 19:55:05 UTC
A workaround might be to use a ContentPage instead of just a Page when the Detail is first set in the attached sample project.
Comment 2 Jimmy [MSFT] 2016-10-25 16:08:39 UTC
I can no longer reproduce this issue when using Forms 2.3.2 and AppCompat.