mirror of
https://github.com/pachli/pachli-android.git
synced 2025-02-07 23:48:49 +01:00
30ec3982ff
This reverts commit 3870267701d8c363985b2e2e6966716c5f5f9f12. With this commit Pachli Current crash reports in Google Play showed instances of: ``` Exception java.lang.RuntimeException: at android.app.ActivityThread.handleBindApplication (ActivityThread.java:7716) 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:8919) at java.lang.reflect.Method.invoke at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:578) at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1103) Caused by java.lang.IllegalStateException: WorkManager is not initialized properly. You have explicitly disabled WorkManagerInitializer in your manifest, have not manually called WorkManager#initialize at this point, and your Application does not implement Configuration.Provider. at androidx.work.impl.WorkManagerImpl.getInstance (WorkManagerImpl.java:170) at androidx.work.WorkManager.getInstance (WorkManager.java:184) at app.pachli.PachliApplication.onCreate (PachliApplication.kt:96) at android.app.Instrumentation.callApplicationOnCreate (Instrumentation.java:1316) at android.app.ActivityThread.handleBindApplication (ActivityThread.java:7711) ``` on Samsung devices at API 34. By my understanding this is a "can't happen" issue, the `WorkManager` is supposed to be initialised by the androidx.startup content provider before `PachliApplication` starts. But it clearly does, so revert this change to be safe.