Crash on device that FBE is enabled [112665532]

Fixed

Bug

Status Update

No update yet.

Description

[Deleted User]

created issue #1

Aug 16, 2018 03:46AM

About Android FBE information is as follows：

https://source.android.com/security/encryption/file-based

https://developer.android.com/training/articles/direct-boot

My app starts by receiving "android.intent.action.LOCKED_BOOT_COMPLETED", WorkManager initial before user unlocked.

It cause crash:
java.lang.IllegalStateException: SharedPreferences in credential encrypted storage are not available until after user is unlocked

Because WorkManager use context.applicationContext accessing data/data/package/xxxx.

I tried to disable WorkManagerInitializer in AndroidManifest.xml and initial WorkManager on my first activity.But it cause another crash:
08-16 11:02:07.441 E/AndroidRuntime(19740): java.lang.RuntimeException: Unable to create service androidx.work.impl.background.systemjob.SystemJobService: java.lang.IllegalStateException: WorkManager needs to be initialized via a ContentProvider#onCreate() or an Application#onCreate().
08-16 11:02:07.441 E/AndroidRuntime(19740): at android.app.ActivityThread.handleCreateService(ActivityThread.java:3415)
08-16 11:02:07.441 E/AndroidRuntime(19740): at android.app.ActivityThread.-wrap4(Unknown Source:0)
08-16 11:02:07.441 E/AndroidRuntime(19740): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1738)
08-16 11:02:07.441 E/AndroidRuntime(19740): at android.os.Handler.dispatchMessage(Handler.java:106)
08-16 11:02:07.441 E/AndroidRuntime(19740): at android.os.Looper.loop(Looper.java:164)
08-16 11:02:07.441 E/AndroidRuntime(19740): at android.app.ActivityThread.main(ActivityThread.java:6618)
08-16 11:02:07.441 E/AndroidRuntime(19740): at java.lang.reflect.Method.invoke(Native Method)
08-16 11:02:07.441 E/AndroidRuntime(19740): at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)
08-16 11:02:07.441 E/AndroidRuntime(19740): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:810)
08-16 11:02:07.441 E/AndroidRuntime(19740): Caused by: java.lang.IllegalStateException: WorkManager needs to be initialized via a ContentProvider#onCreate() or an Application#onCreate().
08-16 11:02:07.441 E/AndroidRuntime(19740): at androidx.work.impl.background.systemjob.SystemJobService.onCreate(SystemJobService.java:67)
08-16 11:02:07.441 E/AndroidRuntime(19740): at android.app.ActivityThread.handleCreateService(ActivityThread.java:3405)
08-16 11:02:07.441 E/AndroidRuntime(19740): ... 8 more

Comments

su...@google.com <su...@google.com> #2Aug 16, 2018 03:53AM

There is no error when I use kotlin versions: 1.6.21, but issue/error starts appearing when kotlin version is 1.7.0

[Deleted User] <[Deleted User]> #3Aug 16, 2018 04:56AM

I have the same problem, i think no stable version of room 2.4.2 with kotlin 1.7.0

su...@google.com <su...@google.com> #4Aug 16, 2018 04:34PM

usage implementation 'androidx.room:room-ktx:2.5.0-alpha02'

il...@google.com <il...@google.com> #5Aug 16, 2018 06:06PM

me too

su...@google.com <su...@google.com> Aug 16, 2018 11:09PM

Assigned to su...@google.com.

ap...@google.com <ap...@google.com> #6Aug 17, 2018 10:42PM

Thanks for the report I was able to reproduce the issue and indeed it occurs when using Kotlin 1.7.0. Sadly I don't have a workaround yet, but will investigate further.

su...@google.com <su...@google.com> #7Aug 17, 2018 10:43PM

Marked as fixed.

and just to clarify, we see the issue when using Room 2.4.2, but not with Room 2.5.0-alpha02.

[Deleted User] <[Deleted User]> #8Aug 17, 2018 11:55PM

it occurs when kotlin version 1.7.0 and room 2.5.0-alpha02 as well to me. I solved the problem by downgrading kotlin version to 1.6.20

ra...@google.com <ra...@google.com> #9Aug 18, 2018 01:44AM

The same if you trying this Google-Developer Project:

https://github.com/google-developer-training/android-basics-kotlin-sql-basics-app
I updated everything - It wasn't running.
With ext.kotlin_version = "1.6.21" - it is running.

ma...@gmail.com <ma...@gmail.com> #10Aug 18, 2018 05:06PM

As a workaround, you can remove the "suspend" in the dao, but you need to explicitly specify the Dispatchers.IO when launching the coroutine.

so...@gmail.com <so...@gmail.com> #11Jan 21, 2020 12:41PM

Hey all, looks like the issue is related to a change in Kotlin's @Metadata annotation and the way Room reads it, Room 2.4.2 is using an older version of the kotlinx-metadata-jvm library which does not support reading Kotlin 1.7 information, where as in Room 2.5.0 we updated the library.

To workaround this issue please force upgrade the dependency by adding it to your annotation processor path, i.e. add kapt "org.jetbrains.kotlinx:kotlinx-metadata-jvm:0.5.0" if you are using Room 2.4.x.

Meanwhile, I'll work on releasing a Room 2.4.3 that is compatible with Kotlin 1.7 since Room 2.5.x is still in development.

so...@gmail.com <so...@gmail.com> #12Mar 3, 2020 05:56AM

Thanks a lot. Now its working good for me.