Fixed
Status Update
Comments
pi...@googlemail.com <pi...@googlemail.com> #2
A fix should be available in alpha05. Thanks for the bug report.
se...@google.com <se...@google.com>
ap...@google.com <ap...@google.com> #3
@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.
da...@google.com <da...@google.com>
da...@google.com <da...@google.com> #4
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?
ar...@gmail.com <ar...@gmail.com> #5
@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.
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).