ExceptionInInitializerError

[sentry]

Sentry Issue: WORDPRESS-ANDROID-38R

NoSuchFieldException: _state
    at java.lang.Class.getDeclaredField(Class.java:929)
    at java.util.concurrent.atomic.AtomicReferenceFieldUpdater$AtomicReferenceFieldUpdaterImpl.<init>(AtomicReferenceFieldUpdater.java:183)
    at java.util.concurrent.atomic.AtomicReferenceFieldUpdater.newUpdater(AtomicReferenceFieldUpdater.java:67)
    at kotlinx.coroutines.JobSupport.<clinit>(JobSupport.kt)
    at kotlinx.coroutines.JobKt__JobKt.Job(Job.kt:361)
...
(21 additional frame(s) were not displayed)

RuntimeException: java.lang.NoSuchFieldException: _state
    at java.util.concurrent.atomic.AtomicReferenceFieldUpdater$AtomicReferenceFieldUpdaterImpl.<init>(AtomicReferenceFieldUpdater.java:202)
    at java.util.concurrent.atomic.AtomicReferenceFieldUpdater.newUpdater(AtomicReferenceFieldUpdater.java:67)
    at kotlinx.coroutines.JobSupport.<clinit>(JobSupport.kt)
    at kotlinx.coroutines.JobKt__JobKt.Job(Job.kt:361)
    at kotlinx.coroutines.JobKt.Job
...
(20 additional frame(s) were not displayed)

ExceptionInInitializerError: None
    at org.wordpress.android.ui.uploads.UploadStarter.<init>(UploadStarter.kt:64)
    at org.wordpress.android.ui.uploads.UploadStarter_Factory.get(UploadStarter_Factory.java:81)
    at org.wordpress.android.ui.uploads.UploadStarter_Factory.get(UploadStarter_Factory.java:16)
    at org.wordpress.android.modules.DaggerAppComponent.injectWordPress(DaggerAppComponent.java:4849)
    at org.wordpress.android.modules.DaggerAppComponent.inject(DaggerAppComponent.java:4124)
...
(17 additional frame(s) were not displayed)

[jd-alexander]

This seems to be happening due to an issue with Samsung's fork of Android. There is a detailed discussion taking place on the Kotlin repo here
For now, we will have to leave it until Samsung releases as a patch of some sort as we would need to write some bytecode transformation plugin as per the discussion, which might not be worth it.

[sentry]

Sentry issue: WORDPRESS-ANDROID-22P

[malinajirka]

I've spent some time investigating this issue today. I completely agree with Joel's conclusion that there isn't anything we can do about the root cause of the issue. However, I believe the thing which is causing this issue in our codebase is the usage of Mutex().
I was thinking if we could get rid of it and replace it with something else which wouldn't be causing these troubles. I'll create a PR with my proposal in a bit.

[shiki]

Fixed in #10877 and #10878.