Google play services has crashed

twitheatrophonic

Bought new pixel 9. Setup everything. Getting google play services has crashed error. Like every 10 minutes. What to do?

GrapheneOS

twitheatrophonic You'll need to provide the error message as a starting point.

twitheatrophonic

Should i send the report here?
The error says - google play services has crashed

de0u

twitheatrophonic If you are getting a crash dump, it should be safe to post it.

twitheatrophonic

type: crash
osVersion: google/tokay/tokay:16/BP2A.250805.005/2025091900:user/release-keys
package: com.google.android.gms:253434035, targetSdk 36
process: com.google.android.gms
processUptime: 812 + 572 ms
installer: app.grapheneos.apps
GmsCompatConfig version: 161

java.lang.SecurityException: DCL via storage, path: /data/user_de/0/com.google.android.gms/app_chimera/m/00000005/dl-Antifingerprinting.optional_253434100000.apk
at android.ext.dcl.DynCodeLoading.checkDexFileOpen(DynCodeLoading.java:131)
at dalvik.system.DexFile.openDexFileNative(Native Method)
at dalvik.system.DexFile.openDexFile(DexFile.java:406)
at dalvik.system.DexFile.<init>(DexFile.java:128)
at dalvik.system.DexFile.<init>(DexFile.java:101)
at dalvik.system.DexPathList.loadDexFile(DexPathList.java:438)
at dalvik.system.DexPathList.makeDexElements(DexPathList.java:397)
at dalvik.system.DexPathList.<init>(DexPathList.java:166)
at dalvik.system.BaseDexClassLoader.<init>(BaseDexClassLoader.java:160)
at dalvik.system.BaseDexClassLoader.<init>(BaseDexClassLoader.java:105)
at dalvik.system.PathClassLoader.<init>(PathClassLoader.java:71)
at dalvik.system.DelegateLastClassLoader.<init>(DelegateLastClassLoader.java:114)
at wwf.f(:com.google.android.gms@253434035@25.34.34 (260400-800653487):47)
at xah.b(:com.google.android.gms@253434035@25.34.34 (260400-800653487):445)
at xbb.d(:com.google.android.gms@253434035@25.34.34 (260400-800653487):210)
at xbb.c(:com.google.android.gms@253434035@25.34.34 (260400-800653487):29)
at wvp.h(:com.google.android.gms@253434035@25.34.34 (260400-800653487):48)
at wvi.a(:com.google.android.gms@253434035@25.34.34 (260400-800653487):15)
at wvp.q(:com.google.android.gms@253434035@25.34.34 (260400-800653487):24)
at wvp.i(:com.google.android.gms@253434035@25.34.34 (260400-800653487):6)
at wzw.run(:com.google.android.gms@253434035@25.34.34 (260400-800653487):321)
at wzq.run(:com.google.android.gms@253434035@25.34.34 (260400-800653487):44)
at gdma.run(:com.google.android.gms@253434035@25.34.34 (260400-800653487):21)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1156)
at java.util.concurrent.ThreadPoolExecutor&dollar;Worker.run(ThreadPoolExecutor.java:651)
at java.lang.Thread.run(Thread.java:1119)

mortuary_jab

twitheatrophonic have you restricted DCL via storage for Play Services or other apps that use this? This is allowed by default for me and it says:

Most apps that depend on Play services require DCL via storage to be allowed

fid03

twitheatrophonic Yes, both Play services and Play Store need DCL via Storage. There is a note about that in the DCL via Storage permission menus for the two apps. In addition, apps that "depend on" Play services are by default allowed to do DCL via storage; you can find this note in the respective apps' DCL via Storage permission menus.

twitheatrophonic

Anyone?

Watermelon

fid03 Yes, both Play services and Play Store need DCL via Storage.

In my experience the Play Store doesn't need DCL via storage to be allowed, however enabling this exploit mitigation on it does cause mitigation violation notifications (and no other apparent errors so far), and it's the reason why the GrapheneOS project said in another thread here that they don't want to enable it by default for the Play Store. I enabled all exploit mitigations on the Play Store and silenced the mitigation violation notifications so I wouldn't be spammed, and it seems to work well.

twitheatrophonic

Thank you guys. I'd restricted that. Hopefully it'll not crash anymore

GrapheneOS

Watermelon Play Store needs DCL via memory for the Play Integrity API and perhaps some related things. It needs DCL via storage for several things.

Watermelon

GrapheneOS Play Store's developer options (not the same as the OS's Developer Options) reports that my device MEETS_BASIC_INTEGRITY. Maybe you're right but this was one of the first things I kept track of after enabling the mitigations on it, and so far it seems to work fine. At the very least I remember that there are mitigation violation notifications that I silenced. Hopefully no other errors would happen.