Fixed
Status Update
No update yet.
Comments
il...@google.com
je...@gmail.com
A fix should be available in alpha05. Thanks for the bug report.
il...@google.com
il...@google.com
@2 Today I got a new version for this (alpha 5), but is it safe now to use firebase too? I remember it had an issue, which I could only fix by removing this line:
implementation "android.arch.work:work-firebase:1.0.0-..."
And it's the same for Java as it is for Kotlin, right?
I've tested it with firebase, and it seems to work fine on Android 4.4 and Android P.
implementation "android.arch.work:work-firebase:1.0.0-..."
And it's the same for Java as it is for Kotlin, right?
I've tested it with firebase, and it seems to work fine on Android 4.4 and Android P.
so...@gmail.com
Did you file a bug about the firebase issue? If not, we'd need a bug and a bugreport/details to investigate. If you have filed such a bug, which one is it and has it been marked as fixed?
il...@google.com
@4 No, I wrote here, as WorkManager is on the support library, and it is supposed to support Firebase too.
Also, as I wrote, it seems to be fixed on alpha 5.
Also, as I wrote, it seems to be fixed on alpha 5.
[Deleted User] <[Deleted User]>
It was fixed in alpha03, but came back in alpha04. I'm having same issue with a graph like this:
<fragment
android:id="@+id/destination_fragmentA"
android:name="com.test.FragmentA"
android:label="FragmentA">
<action
android:id="@id/to_fragment_b"
app:destination="@id/destination_fragmentB"
/>
<action
android:id="@id/to_fragment_c"
app:destination="@id/destination_fragmentC"
/>
</fragment>
<fragment
android:id="@+id/destination_fragmentB"
android:name="com.test.FragmentB"
android:label="FragmentB">
<action
android:id="@id/to_fragment_c"
app:destination="@id/destination_fragmentC"
app:popUpTo="@id/destination_fragmentA"
/>
</fragment>
<fragment
android:id="@+id/destination_fragmentC"
android:name="com.test.FragmentC"
android:label="FragmentC">
</fragment>
1. FragmentA opens FragmentB
2. FragmentB opens FragmentC and removes itself from stack with app:popUpTo="@id/destination_fragmentA"
3. Go back to FragmentA from FragmentC with back button
4. Open FragmentC -> crash java.lang.IllegalArgumentException: navigation destination com.test:id/to_fragment_c is unknown to this NavController
Scenario is similar to one described inhttps://issuetracker.google.com/issues/110179436 , but without subgraph.
<fragment
android:id="@+id/destination_fragmentA"
android:name="com.test.FragmentA"
android:label="FragmentA">
<action
android:id="@id/to_fragment_b"
app:destination="@id/destination_fragmentB"
/>
<action
android:id="@id/to_fragment_c"
app:destination="@id/destination_fragmentC"
/>
</fragment>
<fragment
android:id="@+id/destination_fragmentB"
android:name="com.test.FragmentB"
android:label="FragmentB">
<action
android:id="@id/to_fragment_c"
app:destination="@id/destination_fragmentC"
app:popUpTo="@id/destination_fragmentA"
/>
</fragment>
<fragment
android:id="@+id/destination_fragmentC"
android:name="com.test.FragmentC"
android:label="FragmentC">
</fragment>
1. FragmentA opens FragmentB
2. FragmentB opens FragmentC and removes itself from stack with app:popUpTo="@id/destination_fragmentA"
3. Go back to FragmentA from FragmentC with back button
4. Open FragmentC -> crash java.lang.IllegalArgumentException: navigation destination com.test:id/to_fragment_c is unknown to this NavController
Scenario is similar to one described in
an...@gmail.com
I'm getting this, or a similar, issue re-occurring in android.arch.navigation:navigation-fragment-ktx:1.0.0-alpha06. I've recorded a screen capture and updated the linked application.
an...@gmail.com
In another application I have it where navigating to a fragment through a global action makes it so that the NavigationDrawer no longer pops down when clicking the toolbar icon. As noted in the screen recording I had to click the "Import" menu item twice to get it to work on the third time through (prior to the crash).
Description
E/AndroidRuntime: FATAL EXCEPTION: main
Process: com.example.jetpacknavigationtest, PID: 20199
java.util.NoSuchElementException
at java.util.ArrayDeque.removeLast(ArrayDeque.java:274)
at androidx.navigation.fragment.FragmentNavigator.popBackStack(FragmentNavigator.java:87)
at androidx.navigation.NavController.popBackStack(NavController.java:280)
at androidx.navigation.NavController.navigate(NavController.java:642)
at androidx.navigation.NavController.navigate(NavController.java:592)
at androidx.navigation.Navigation$1.onClick(Navigation.java:118)
at android.view.View.performClick(View.java:6294)
at android.view.View$PerformClick.run(View.java:24770)
at android.os.Handler.handleCallback(Handler.java:790)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:164)
at android.app.ActivityThread.main(ActivityThread.java:6494)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:807)
Component used:
android.arch.navigation:navigation-fragment-ktx
Version used:
1.0.0-alpha02
Devices/Android versions reproduced on:
Android_Accelerated_x86_Oreo.avd
If this is a bug in the library, we would appreciate if you could attach:
- Sample project to trigger the issue.
- A screenrecord or screenshots showing the issue (if UI related).