microg / microg/GmsCore

java.lang.NoClassDefFoundError: Failed resolution of: Lcpfr

Open
#1,877 3 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Java
Stars
14.6k
Forks
3.2k
Avg merge
12d 11h
Merged PRs (30d)
4

Description

Describe the bug
Fatal Exception: java.lang.NoClassDefFoundError: Failed resolution of: Lcpfr;
at abxk.d(abxk.java)
at zad.(zad.java:2)
at com.google.android.gms.chimera.container.DynamiteLoaderImpl.(DynamiteLoaderImpl.java:4)
at java.lang.Class.newInstance(Class.java)
at com.google.android.gms.dynamite.DynamiteModule.zzf(com.google.android.gms:play-services-basement@@18.0.1:5)
at com.google.android.gms.dynamite.DynamiteModule.zza(com.google.android.gms:play-services-basement@@18.0.1:26)
at com.google.android.gms.dynamite.zze.zzb(com.google.android.gms:play-services-basement@@18.0.1:1)
at com.google.android.gms.dynamite.zzk.selectModule(com.google.android.gms:play-services-basement@@18.0.1:2)
at com.google.android.gms.dynamite.DynamiteModule.load(com.google.android.gms:play-services-basement@@18.0.1:5)
at com.google.android.gms.internal.measurement.zzee.zzf(com.google.android.gms:play-services-measurement-sdk-api@@19.0.2:2)
at com.google.android.gms.internal.measurement.zzcx.zza(com.google.android.gms:play-services-measurement-sdk-api@@19.0.2:3)
at com.google.android.gms.internal.measurement.zzdt.run(com.google.android.gms:play-services-measurement-sdk-api@@19.0.2:2)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
at java.lang.Thread.run(Thread.java:762)

Caused by java.lang.ClassNotFoundException: Didn't find class "cpfr" on path: DexPathList[[zip file "/system/framework/com.android.location.provider.jar", zip file "/system/framework/com.android.media.remotedisplay.jar", zip file "/data/app/com.google.android.gms-2/base.apk", zip file "/data/app/com.google.android.gms-2/split_config.es.apk"],nativeLibraryDirectories=[/data/app/com.google.android.gms-2/lib/arm, /data/app/com.google.android.gms-2/base.apk!/lib/armeabi-v7a, /data/app/com.google.android.gms-2/split_config.es.apk!/lib/armeabi-v7a, /system/lib, /vendor/lib]]
at dalvik.system.BaseDexClassLoader.findClass(BaseDexClassLoader.java:56)
at java.lang.ClassLoader.loadClass(ClassLoader.java:380)
at java.lang.ClassLoader.loadClass(ClassLoader.java:312)
at abxk.d(abxk.java)
at zad.(zad.java:2)
at com.google.android.gms.chimera.container.DynamiteLoaderImpl.(DynamiteLoaderImpl.java:4)
at java.lang.Class.newInstance(Class.java)
at com.google.android.gms.dynamite.DynamiteModule.zzf(com.google.android.gms:play-services-basement@@18.0.1:5)
at com.google.android.gms.dynamite.DynamiteModule.zza(com.google.android.gms:play-services-basement@@18.0.1:26)
at com.google.android.gms.dynamite.zze.zzb(com.google.android.gms:play-services-basement@@18.0.1:1)
at com.google.android.gms.dynamite.zzk.selectModule(com.google.android.gms:play-services-basement@@18.0.1:2)
at com.google.android.gms.dynamite.DynamiteModule.load(com.google.android.gms:play-services-basement@@18.0.1:5)
at com.google.android.gms.internal.measurement.zzee.zzf(com.google.android.gms:play-services-measurement-sdk-api@@19.0.2:2)
at com.google.android.gms.internal.measurement.zzcx.zza(com.google.android.gms:play-services-measurement-sdk-api@@19.0.2:3)
at com.google.android.gms.internal.measurement.zzdt.run(com.google.android.gms:play-services-measurement-sdk-api@@19.0.2:2)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607)
at java.lang.Thread.run(Thread.java:762)

To Reproduce
Steps to reproduce the behavior:
Can not reproduce the crash ,just find many crash report in firebase

Screenshots
Most crash occur in Samsung android 7 \8 and on the background.

image

More Info
com.google.gms:google-services:4.3.13

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the posted stack trace and the reported google-services version 4.3.13, then investigate the Play Services and Dynamite loading path on Samsung devices running Android 7 or 8. Compare the Firebase crash reports with available reproduction or device logs; done means identifying the missing class's source and confirming a fix against the background crash.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, firebase, java
Domain
mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.