Fixed
Status Update
Comments
pi...@googlemail.com <pi...@googlemail.com> #2
Hi. Thanks for reporting this. Fixed in alpha-04
se...@google.com <se...@google.com>
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
da...@google.com <da...@google.com>
da...@google.com <da...@google.com> #4
deleted
ar...@gmail.com <ar...@gmail.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
il...@google.com <il...@google.com> #6
Re #5 - if you're still running into an issue, please file a new issue with a sample project that reproduces your issue.
am...@gmail.com <am...@gmail.com> #7
Bug still exist on alpha11.
il...@google.com <il...@google.com> #8
Re #7 - if you're still running into an issue, please file a new issue with a sample project that reproduces your issue.
me...@gmail.com <me...@gmail.com> #9
this bug is still present in 2.3.0
Description
Version used: 1.0.0-alpha04
Devices/Android versions reproduced on: (does not depend on device)
Let's say, my back stack is A->B. When I click 'back' button, the last fragment is getting popped (fragment A gets displayed), but this is done by the FragmentManager's transaction handling behavior. Inside NavController back stack does not get updated. Thus, if I then try to navigate via action, I get an exception saying that the action is not found (because the top of back stack is still fragment B).