java.lang.ClassCircularityError: Class qsy.osf.ykv extends itself

[hanpingchinese]

[REQUIRED] Step 2: Describe your environment

• Android Studio version: 2023.2.1 Patch 2
• Firebase Component: AppCheck
• Component version: 32.8.1

google-android-play-services-auth = "21.1.0"
google-services = "4.4.1"

[REQUIRED] Step 3: Describe the problem

Crash seen in Crashlytics for single users (99.9% users no problem)

Steps to reproduce:

Unable to reproduce. Only seen in Crashlytics

Similar to #5664 #5664 ?

Relevant Code:

Galaxy A33 5G (Android 14)

java.lang.ClassCircularityError: Class qsy.osf.ykv extends itself (declaration of 'qsy.osf.ykv' appears in /data/app/~~B_cE45p2ZuWvdMTJARbwvg==/com.myapp-DZHAcyvy15OkzWngDA6bag==/base.apk)
       at com.google.android.gms.tasks.zzw.<init>(com.google.android.gms:play-services-tasks@@18.1.0:10)
       at com.google.android.gms.tasks.TaskCompletionSource.<init>(com.google.android.gms:play-services-tasks@@18.1.0:5)
       at com.google.firebase.appcheck.internal.DefaultFirebaseAppCheck.retrieveStoredAppCheckTokenInBackground(DefaultFirebaseAppCheck.java:95)
       at com.google.firebase.appcheck.internal.DefaultFirebaseAppCheck.<init>(DefaultFirebaseAppCheck.java:90)
       at com.google.firebase.appcheck.FirebaseAppCheckRegistrar.lambda$getComponents$0(FirebaseAppCheckRegistrar.java:72)
       at com.google.firebase.tracing.ComponentMonitor.lambda$processRegistrar$0(ComponentMonitor.java:38)
       at com.google.firebase.components.ComponentRuntime.lambda$discoverComponents$0(ComponentRuntime.java:160)
       at com.google.firebase.components.Lazy.get(Lazy.java:53)
       at com.google.firebase.components.ComponentRuntime.doInitializeEagerComponents(ComponentRuntime.java:322)
       at com.google.firebase.components.ComponentRuntime.initializeEagerComponents(ComponentRuntime.java:312)
       at com.google.firebase.FirebaseApp.initializeAllApis(FirebaseApp.java:607)
       at com.google.firebase.FirebaseApp.initializeApp(FirebaseApp.java:300)
       at com.google.firebase.FirebaseApp.initializeApp(FirebaseApp.java:264)
       at com.google.firebase.FirebaseApp.initializeApp(FirebaseApp.java:249)
       at com.google.firebase.provider.FirebaseInitProvider.onCreate(FirebaseInitProvider.java:69)
       at android.content.ContentProvider.attachInfo(ContentProvider.java:2690)
       at android.content.ContentProvider.attachInfo(ContentProvider.java:2660)
       at com.google.firebase.provider.FirebaseInitProvider.attachInfo(FirebaseInitProvider.java:61)
       at android.app.ActivityThread.installProvider(ActivityThread.java:8458)
       at android.app.ActivityThread.installContentProviders(ActivityThread.java:7963)
       at android.app.ActivityThread.handleBindApplication(ActivityThread.java:7649)
       at android.app.ActivityThread.-$$Nest$mhandleBindApplication()
       at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2478)
       at android.os.Handler.dispatchMessage(Handler.java:106)
       at android.os.Looper.loopOnce(Looper.java:230)
       at android.os.Looper.loop(Looper.java:319)
       at android.app.ActivityThread.main(ActivityThread.java:8893)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:608)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1103)

[google-oss-bot]

I found a few problems with this issue:

• I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.
• This issue does not seem to follow the issue template. Make sure you provide all the required information.

[lehcar09]

Hi @hanpingchinese, thank you for reaching out. I tried to investigate the issue, however, I wasn't able to replicate as well. The issue #5664, as this is might be caused by the Firebase Crashlytics dependency that is Firebase session.

Based on this Stack Overflow link:

This error will not normally happen unless the version of some library used in run-time does not match the version of the library used for compilation.

Is it possible that some problems occurred during app build? Does the issue occur on certain devices and/or android versions?

[hanpingchinese]

I don't think the issue could have occurred in the build otherwise how would the build complete? All I have is a single crashlytics report from a single device (non-rooted). I suppose it could be someone trying to hack the app?

[lehcar09]

Thanks for the extra details. I can’t say anything for sure for now; – This seems to be an edge case scenario. That said, given that this is difficult to reproduce, what we can do is leave this issue open for now, in case our engineers might have an idea what's causing the issue. We can prioritize a deeper investigation on this if this begins to affect more developers.
If anyone encounters the same issue, kindly leave a thumbs up on the author's original post. This'll help us prioritize issues based on severity and demand. Thanks!