DataStore crashed after upgrade from 1.0.0-alpha02 to alpha03 [173036843]

Fixed

Bug

Status Update

No update yet.

Description

[Deleted User]

created issue #1

Nov 12, 2020 03:02AM

After I upgraded from DataStore 1.0.0-alpha02 to alpha03. DataStore crashed.

implementation "androidx.datastore:datastore-preferences:1.0.0-alpha03"

 java.lang.NoClassDefFoundError: Failed resolution of: Landroidx/datastore/preferences/PreferencesMapCompat;
        at androidx.datastore.preferences.core.PreferencesSerializer.readFrom(PreferencesSerializer.kt:46)
        at androidx.datastore.preferences.core.PreferencesSerializer.readFrom(PreferencesSerializer.kt:36)
        at androidx.datastore.core.SingleProcessDataStore.readData(SingleProcessDataStore.kt:249)
        at androidx.datastore.core.SingleProcessDataStore.readDataOrHandleCorruption(SingleProcessDataStore.kt:227)
        at androidx.datastore.core.SingleProcessDataStore.readAndInitOnce(SingleProcessDataStore.kt:190)
        at androidx.datastore.core.SingleProcessDataStore$actor$1.invokeSuspend(SingleProcessDataStore.kt:154)
        at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
        at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
        at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:571)
        at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:738)
        at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:678)
        at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:665)
     Caused by: java.lang.ClassNotFoundException: Didn't find class "androidx.datastore.preferences.PreferencesMapCompat" on path: DexPathList[[zip file "/data/app/~~AQdf2bhW1X-xyBtRDL-Rqw==/com.myapp-BNefhcdckB1woaukj1e6eA==/base.apk", zip file "/data/app/~~AQdf2bhW1X-xyBtRDL-Rqw==/com.myapp-BNefhcdckB1woaukj1e6eA==/split_config.xxhdpi.apk"],nativeLibraryDirectories=[/data/app/~~AQdf2bhW1X-xyBtRDL-Rqw==/com.myapp-BNefhcdckB1woaukj1e6eA==/lib/x86_64, /system/lib64, /system_ext/lib64]]
        at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:207)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:379)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:312)
        at androidx.datastore.preferences.core.PreferencesSerializer.readFrom(PreferencesSerializer.kt:46) 
        at androidx.datastore.preferences.core.PreferencesSerializer.readFrom(PreferencesSerializer.kt:36) 
        at androidx.datastore.core.SingleProcessDataStore.readData(SingleProcessDataStore.kt:249) 
        at androidx.datastore.core.SingleProcessDataStore.readDataOrHandleCorruption(SingleProcessDataStore.kt:227) 
        at androidx.datastore.core.SingleProcessDataStore.readAndInitOnce(SingleProcessDataStore.kt:190) 
        at androidx.datastore.core.SingleProcessDataStore$actor$1.invokeSuspend(SingleProcessDataStore.kt:154) 
        at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33) 
        at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106) 
        at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:571) 
        at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:738) 
        at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:678) 
        at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:665) 
    	Suppressed: java.io.IOException: No original dex files found for dex location (x86_64) /data/app/~~AQdf2bhW1X-xyBtRDL-Rqw==/com.myapp-BNefhcdckB1woaukj1e6eA==/split_config.xxhdpi.apk
        at dalvik.system.DexFile.openDexFileNative(Native Method)
        at dalvik.system.DexFile.openDexFile(DexFile.java:367)
        at dalvik.system.DexFile.<init>(DexFile.java:109)
        at dalvik.system.DexFile.<init>(DexFile.java:82)
        at dalvik.system.DexPathList.loadDexFile(DexPathList.java:439)
        at dalvik.system.DexPathList.makeDexElements(DexPathList.java:398)
        at dalvik.system.DexPathList.<init>(DexPathList.java:166)
        at dalvik.system.BaseDexClassLoader.<init>(BaseDexClassLoader.java:129)
        at dalvik.system.BaseDexClassLoader.<init>(BaseDexClassLoader.java:104)
        at dalvik.system.PathClassLoader.<init>(PathClassLoader.java:74)
        at com.android.internal.os.ClassLoaderFactory.createClassLoader(ClassLoaderFactory.java:87)
        at com.android.internal.os.ClassLoaderFactory.createClassLoader(ClassLoaderFactory.java:116)
        at android.app.ApplicationLoaders.getClassLoader(ApplicationLoaders.java:114)
        at android.app.ApplicationLoaders.getClassLoaderWithSharedLibraries(ApplicationLoaders.java:60)
        at android.app.LoadedApk.createOrUpdateClassLoaderLocked(LoadedApk.java:901)
        at android.app.LoadedApk.getClassLoader(LoadedApk.java:958)
        at android.app.LoadedApk.getResources(LoadedApk.java:1190)
        at android.app.ContextImpl.createAppContext(ContextImpl.java:2663)
        at android.app.ContextImpl.createAppContext(ContextImpl.java:2655)
        at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6595)
        at android.app.ActivityThread.access$1300(ActivityThread.java:237)
        at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1913)
        at android.os.Handler.dispatchMessage(Handler.java:106)
        at android.os.Looper.loop(Looper.java:223)
        at android.app.ActivityThread.main(ActivityThread.java:7656)
2020-11-12 09:50:28.461 25656-25656/com.myapp E/AndroidRuntime:     at java.lang.reflect.Method.invoke(Native Method)
        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)

Comments

[Deleted User] <[Deleted User]> #2Nov 12, 2020 07:50AM

Also, we ever checked this with our SoC vendor Qualcomm. Repost their reply as below:
"Dear Customer,
With respect to linker issue and this could be issue with google as the keystore bin is maintained by google,, qcom don't own this.. Please check with google..
Basically what i understand from error, it indicate that the linker is unable to create the executable keystore it can not find a specific symbol (_ZTSN6icu_7024DateTimePatternGeneratorE). This symbol is referenced by the library libicui18n.so."

vi...@gmail.com <vi...@gmail.com> #3Nov 12, 2020 02:37PM

The related log is:

01-04 13:17:32.786   501   501 F linker  : CANNOT LINK EXECUTABLE "/system/bin/keystore2": cannot locate symbol "_ZTIN6icu_7024DateTimePatternGeneratorE" referenced by "/apex/com.android.i18n/lib64/libicui18n.so"...

Where do you get /apex/com.android.i18n? The symbol should be defined in libicui18n.so itself.

ro...@google.com <ro...@google.com> Nov 12, 2020 08:18PM

Accepted by ro...@google.com.

[Deleted User] <[Deleted User]> #4Nov 13, 2020 03:41AM

hi,
It should be built from the GSI source code of AOSP. And the last git log of /system/apex is:
commit a6c05564be6ac04bc1be117f86564552cc200952 (HEAD, origin/android13_ext, m/android13_ext, android13_ext)
Merge: 8eab4a2e d2c816eb
Author: Android Build Coastguard Worker <android-build-coastguard-worker@google.com>
Date: Thu Nov 10 00:29:51 2022 +0000

Snap for 9274385 from d2c816eb179071a39247c6fdcf3e4de278f9231b to tm-qpr2-release

Change-Id: I3cfc162bd4a8897cffc75417702a58de4f142967

commit d2c816eb179071a39247c6fdcf3e4de278f9231b
Author: Jooyung Han <jooyung@google.com>
Date: Tue Nov 8 16:30:02 2022 +0900

Use block apex path as key for rootdigest overrides

When scanning block apexes in VM mode, apexd keeps rootdigest overrides
in a map for later verification. But using apex name as a key doesn't
work for "sharelibs" apexes because there might be two apexes for a
single sharelib apex name.

Instead, we can use block apex path as a key to a map.

Bug: 257377686
Test: ApexTestCases
Merged-In: Idd4e90f52e56b47d046c4eda88f34bf7b7aee4d5
Change-Id: Idd4e90f52e56b47d046c4eda88f34bf7b7aee4d5
(cherry picked from commit f571befaba0b3609d9574a2b31006e0c871c5fe8)

ap...@google.com <ap...@google.com> #5Nov 13, 2020 06:32AM

Please check the symbol in your object file /apex/com.android.i18n/lib64/libicui18n.so. The symbol should be defined in the library. I suspect that the file is corrupted.

You may also download the Android13 GSI image for comparison.

up...@gmail.com <up...@gmail.com> #6Nov 15, 2020 02:01PM

Hi,
That device can boot into android normally if we forced to restart it. Do you still think that file is corrupt in this case?

fp...@gmail.com <fp...@gmail.com> #7Nov 16, 2020 04:59PM

By "device can boot into android normally", you mean keystore2 can be executed without that linker error?

ni...@google.com <ni...@google.com> #8Nov 17, 2020 09:42PM

Marked as fixed.

Hi,
Yeah, we didn't see the same error by doing so.

se...@gmail.com <se...@gmail.com> #9Nov 18, 2020 01:01AM

If it's not always reproducible, then I suspect it's a device issue. Let me close the issue as not reproducible. Feel free to reopen it if you find a reliable way to reproduce the problem.

se...@gmail.com <se...@gmail.com> #10Nov 18, 2020 01:09AM

For me, it should be always reproducible during an overnight test. Until now, we found 5 of 100 devices have such problem. Could you please help to check if there is any way to do further analysis on this issue?