Fixed
Status Update
No update yet.
Comments
ra...@google.com
This has been fixed internally in https://android-review.googlesource.com/870975 and will be available in Navigation 1.0.0-alpha10.
Now, instead of crashing, we ignore invalid deep links, printing a log message saying as much.
Now, instead of crashing, we ignore invalid deep links, printing a log message saying as much.
ra...@google.com
Hi team.
The problem still occurs on version 2.2.0-rc04
The problem still occurs on version 2.2.0-rc04
Description
+--- com.google.guava:listenablefuture:1.0
+--- android.arch.lifecycle:extensions:1.1.0
\--- android.arch.persistence.room:runtime:1.1.1-rc1
+--- android.arch.persistence.room:common:1.1.1-rc1
| \--- com.android.support:support-annotations:26.1.0
+--- android.arch.persistence:db-framework:1.1.1-rc1
| +--- com.android.support:support-annotations:26.1.0
| \--- android.arch.persistence:db:1.1.1-rc1
| \--- com.android.support:support-annotations:26.1.0
+--- android.arch.persistence:db:1.1.1-rc1
+--- android.arch.core:runtime:1.1.1
\--- com.android.support:support-core-utils:26.1.0
Room 1.1.1 stable released on June 19
Room 2.0.0 stable released on Oct 1
It would be helpful to avoid double guessing if upgrade to stable artifacts is safe. They are both part of the same Jetpack!