Status Update
Comments
jb...@google.com <jb...@google.com> #2
Hi. Thanks for reporting this. Fixed in alpha-04
[Deleted User] <[Deleted User]> #3
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
[Deleted User] <[Deleted User]> #4
an...@gmail.com <an...@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
[Deleted User] <[Deleted User]> #6
jb...@google.com <jb...@google.com> #7
The way Dynamic Navigation has to handle activities is inherently different from other destinations so not returning there could possibly be intentional.
Is this something new that was caused by upgrading to 2.5.0? Or was it pre-existing?
[Deleted User] <[Deleted User]> #8
When we saw this issue we did a rollback to 2.3.5.
2.3.5 - the last version where this issue doesn't exist
[Deleted User] <[Deleted User]> #9
jb...@google.com <jb...@google.com> #10
You're right, looks like we didn't add it back when we made
an...@gmail.com <an...@gmail.com> #11
[Deleted User] <[Deleted User]> #12
be...@google.com <be...@google.com> #13
The statement was removed during the migration to V2, when we did not expect this problem to occur.
[Deleted User] <[Deleted User]> #14
[Deleted User] <[Deleted User]> #15
fo...@gmail.com <fo...@gmail.com> #16
pa...@outlook.com <pa...@outlook.com> #17
Same issue in my project. Any update here?
ap...@google.com <ap...@google.com> #18
Branch: androidx-main
commit 0c4ad1856d1b956d8a0da8074557a5a69fb130d9
Author: Jeremy Woods <jbwoods@google.com>
Date: Tue Aug 30 16:16:49 2022
Fix navigating to Activities from unloaded modules
Currently, if you are using dynamic Navigation and you attempt to
navigate to a Activity in a module that has not yet be loaded, a
ClassNotFoundException is thrown. This is because the
DynamicActivityNavigator currently attempts to install the module (which
is an async operation) and then immediately navigates to the new class.
Instead, we should return after the install attempt and then allow the
systme to retry the navigation at the appropriate time.
RelNote: "Dynamic Navigation now properly attempts to install Activity
destinations from other modules before navigating to them."
Test: tested on a device using bundletool
Bug: 240292838
Change-Id: Ia2c1645426d2f6a5958a10379a99f2aade3dd03a
M navigation/navigation-dynamic-features-runtime/src/main/java/androidx/navigation/dynamicfeatures/DynamicActivityNavigator.kt
jb...@google.com <jb...@google.com> #19
This has been fixed internally and will be released in Navigation 2.5.2
and 2.6.0-alpha01
.
na...@google.com <na...@google.com> #20
This bug was linked in a change in the following release(s):
androidx.navigation:navigation-dynamic-features-runtime:2.6.0-alpha01
androidx.navigation:navigation-dynamic-features-runtime:2.5.2
Description
Version used: 2.5.0
Devices/Android versions reproduced on: all
package androidx.navigation.dynamicfeatures
public class DynamicActivityNavigator
return statement is missing here after install manager call.
It causes application to crash because you're navigating to not existing class yet.
Fatal Exception: java.lang.RuntimeException
Unable to instantiate activity ComponentInfo{...}: java.lang.ClassNotFoundException: Didn't find class "com....Activity" on path: DexPathList[.....]