Status Update
Comments
jb...@google.com <jb...@google.com> #2
Dany, I believe this is fixed in a new release of safeargs ?
re...@gmail.com <re...@gmail.com> #3
Safeargs still needs AndroidComponentsExtension
to get the applicationID from the variants (7.2.0-alpha05
remove the extension?
re...@lunabee.com <re...@lunabee.com> #4
it moved to a different package : com.android.build.api.variant
jb...@google.com <jb...@google.com>
jb...@google.com <jb...@google.com>
ap...@google.com <ap...@google.com> #5
Safeargs still relies on AGP 4.2
. We need some of the BaseVariant
APIs to have replacements before we can upgrade to 7.0+
(
cl...@google.com <cl...@google.com> #6
The BaseVariant API are deprecated but still available in 7.x, so you should be able to release a newer version that uses the new package and still relies on the old API you require. Or am I missing something ?
na...@google.com <na...@google.com> #7
I'll try updating to the latest stable to see if we run into any issues. I can check to make sure changing the package name in 7.2.0-alpha05 works, but we would need it to be stable before we could do a release with this change.
Description
Component used: Navigation Version used: 2.7.0 Devices/Android versions reproduced on: Pixel 3XL API 31
navigate
withpopUpTo
does not work with arguments (->Ignoring popBackStack to destination -1082070894 as it was not found on the current back stack
). It seems to be due to the destination id equality test, the id is generated with the route with placeholder, and tested against the resolved route. UsingpopBackStack
+navigate
gives the expected result