java.lang.NoSuchFieldError for a "blank" field access from com.google.firebase.perf.transport.TransportManager.getLogcatMsg

[WaterResistantCoder]

Crash Stack Trace:
Fatal Exception: java.lang.NoSuchFieldError: No static field of type Ljava/util/Locale; in class Ljava/util/Locale; or its superclasses (declaration of 'java.util.Locale' appears in /system/framework/core-oj.jar)
at com.google.firebase.perf.transport.TransportManager.getLogcatMsg(TransportManager.java:640)
at com.google.firebase.perf.transport.TransportManager.getLogcatMsg(TransportManager.java:610)
at com.google.firebase.perf.transport.TransportManager.syncLog(TransportManager.java:371)
at com.google.firebase.perf.transport.TransportManager.lambda$log$3(TransportManager.java:330)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
at java.lang.Thread.run(Thread.java:764)

Details:

Android: 8.1.0
firebase-bom:32.1.1

Related Issue from Google Issue Tracker:
From the above link: "Looking at the error message No static field of type Ljava/util/Locale there are two spaces between field and of indicating a field with an "invisible" name."

Please let us know if this can be handled from your side. As the number of crashes are more, even though only few users are being affected.

[google-oss-bot]

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

[lehcar09]

Hi @WaterResistantCoder, thank you for reporting the issue. I tried reproducing the issue in a similar Android API version, however, I did not encounter the issue.

Based on the description and report you shared, this seems like an edge case scenario. I highly suggest updating to the latest Firebase SDK version to ensure that you have the latest fixes that might be causing the issue. I understand that you’re waiting for that version that has the fix for JobScheduler.

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 or we have more details on what’s causing the issue.

P.S. 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!