Fixed
Status Update
Comments
jb...@google.com <jb...@google.com>
ap...@google.com <ap...@google.com> #2
Hi. Thanks for reporting this. Fixed in alpha-04
ap...@google.com <ap...@google.com> #3
Project: platform/frameworks/support
Branch: androidx-main
commit e782987543a9f8ccd485e970ddc74564b24378db
Author: Vighnesh Raut <vighnesh.raut13@gmail.com>
Date: Mon Jan 02 15:27:40 2023
fix: tab row crashes when only 1 tab is added
Bug: b/264018028
Test: Added unit test
Change-Id: I6381dbac304fc1d69d3708c6655f8b595668e93f
M tv/tv-material/src/androidTest/java/androidx/tv/material/TabRowTest.kt
M tv/tv-material/src/main/java/androidx/tv/material/TabRow.kt
https://android-review.googlesource.com/2373449
Branch: androidx-main
commit e782987543a9f8ccd485e970ddc74564b24378db
Author: Vighnesh Raut <vighnesh.raut13@gmail.com>
Date: Mon Jan 02 15:27:40 2023
fix: tab row crashes when only 1 tab is added
Bug:
Test: Added unit test
Change-Id: I6381dbac304fc1d69d3708c6655f8b595668e93f
M tv/tv-material/src/androidTest/java/androidx/tv/material/TabRowTest.kt
M tv/tv-material/src/main/java/androidx/tv/material/TabRow.kt
jb...@google.com <jb...@google.com> #4
deleted
jb...@google.com <jb...@google.com> #5
The following release(s) address this bug.It is possible this bug has only been partially addressed:
androidx.tv:tv-material:1.0.0-alpha04
an...@google.com <an...@google.com> #6
The following changes were cherrypicked through Coastguard (https://android-build.googleplex.com/coastguard/ )
Release Track: (https://android-build.googleplex.com/coastguard/dashboard/6205454677704704/#/cherrypickHistory/all )
Created: 2019-11-16 01:24:35.655426+00:00
Changes: aosp/1158564, aosp/1157502
Release Track: (
Created: 2019-11-16 01:24:35.655426+00:00
Changes: aosp/1158564, aosp/1157502
st...@sieveo.com <st...@sieveo.com> #7
Hi everyone
I encountered this bug even though I am on the Navigation 2.2.0-rc03 release - however only when I do a release build of my app with minification enabled.
During normal debug I did not encounter crashes, but when I turn on minification in my debug build I get this crash.
As I work around I changed my layout to use "fragment" instead of "FragmentContainerView" in my xml.
I encountered this bug even though I am on the Navigation 2.2.0-rc03 release - however only when I do a release build of my app with minification enabled.
During normal debug I did not encounter crashes, but when I turn on minification in my debug build I get this crash.
As I work around I changed my layout to use "fragment" instead of "FragmentContainerView" in my xml.
jb...@google.com <jb...@google.com> #8
That issue is caused by a limitation of aapt2 and is being tracked by
Description
Version used: 2.2.0-r01
Devices/Android versions reproduced on: Android 9.0.0
If NavHostFragment is declared in FragmentContainerView it won't set its NavController's graph when it is recreated from configuration change. I believe the reason for this is that FragmentContainerView, unlike <fragment> tag, doesn't call fragment's onInflate() when it was recreated by FragmentManager, and NavHostFragment sets its mGraphId variable only in onInflate(). So when NavHostFragment is recreated its graph is lost.