Fixed
Status Update
No update yet.
Comments
ra...@google.com
Which device is issue being reported on? Can you get any logs from the device for us after you turn on verbose logging ?
ra...@google.com
A few things in addition to the questions in #2:
1. Can you verify that this problem still occurs in beta03? This is available now.
2. Can you check your merged manifest has a network permission (ACCESS_NETWORK_STATE)? It should get merged in automatically.
1. Can you verify that this problem still occurs in beta03? This is available now.
2. Can you check your merged manifest has a network permission (ACCESS_NETWORK_STATE)? It should get merged in automatically.
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!