Updating to platform tools 29.0.0 results in continuous stream of adb.exe crash dialogs, at least on Windows 8.1 [134613180]

Fixed

Bug

Reviewed (L1)

Status Update

No update yet.

Description

le...@gmail.com

created issue #1

Jun 5, 2019 11:55PM

Today I updated several SDK components. I'm on the stable channel, and before today I was up to date for the stable channel. The one I believe I'm having the trouble with is the 29.0.0 platform tools. If I go back to 28.0.2, everything is fine.

When I start the Emulator (via Android Studio), I get a Windows "adb.exe has stopped working" check for solution/close program dialog. Then a couple of seconds later I get another, and another. The emulator does come up, and it's GUI is responsive, but I can't really access it from Android Studio. The stream of Windows error dialogs continues until I stop the emulator.

I can access a real test device just fine.

When I change my "platform-tools" folder back to the previous version, which I believe was 28.0.2, everything works fine. This is the workaround I'm planning on using.

I've tried this with both an AVD that I had before the update to 29.0.0 and one I created after the update. It acts the same.

I have not tried to run the emulator from the command line.

This part I can not reliably reproduce, but I've seen it several times. Sometimes, I get an error dialog after I start the emulator (via Android Studio) but before the first adb.exe crash dialog. That error dialog says something about my adb.exe being hopelessly out of date. I'm not sure who is generating that dialog, but I don't think it's Windows. Over the years I think I've seen that same error very intermittently, but ignoring it never seems to have any negative conciquences.

Since I'm not seeing too much yelling and screaming about this on the net I'm assuming I'm in a relatively small group. Windows 8.1 for one. My most non-standard thing I can think of about my system is that the android SDK folder and the android AVD folder are both on my E: drive (C: is the system drive and where my hold folder is). This is not new.

I have a very low-end Windows 10 machine that I only use in emergencies and it seems to be working fine.

Please Read:

https://developer.android.com/studio/report-bugs.html#emulator-bugs

Android Studio Version: 3.4.0-2

Emulator Version (Emulator--> Extended Controls--> Emulator Version): 29.0.11-5598178
HAXM / KVM Version: HAXM 7.5.1

Android SDK Tools: 26.1.1

Host Operating System: Windows 8.1

CPU Manufacturer: Intel CPU
Virtualization is supported
64-bit CPU

RAM: 16316 MB

GPU: GPU #1
Make: 10de
Model: NVIDIA GeForce 840M
Device ID: 1341

Build Fingerprint: google/sdk_gphone_x86/generic_x86:8.1.0/OSM1.180201.031/5455776:userdebug/dev-keys

AVD Details: Name: Nexus_5X_API_27_8.1_x86_Google_APIs_
CPU/ABI: x86
Path: E:\LeeExtra\Dev\.android\avd\Nexus_5X_API_27_8.1_x86_Google_APIs_.avd
Target: google_apis [Google APIs] (API level 27)
Skin: nexus_5x
SD Card: 512M
AvdId: Nexus_5X_API_27_8.1_x86_Google_APIs_
PlayStore.enabled: false
avd.ini.displayname: Nexus 5X API 27 (8.1 x86 Google APIs)
avd.ini.encoding: UTF-8
disk.dataPartition.size: 800M
fastboot.chosenSnapshotFile:
fastboot.forceChosenSnapshotBoot: no
fastboot.forceColdBoot: no
fastboot.forceFastBoot: yes
hw.accelerometer: yes
hw.arc: false
hw.audioInput: yes
hw.battery: yes
hw.camera.back: virtualscene
hw.camera.front: emulated
hw.cpu.ncore: 4
hw.dPad: no
hw.device.hash2: MD5:ae200ad6786ec467cb9067f7b46b0fd1
hw.device.manufacturer: Google

hw.device.name: Nexus 5X
hw.gps: yes
hw.gpu.enabled: yes
hw.gpu.mode: auto
hw.initialOrientation: Portrait
hw.keyboard: yes
hw.lcd.density: 420
hw.lcd.height: 1920
hw.lcd.width: 1080
hw.mainKeys: no
hw.ramSi

Comments

mi...@gtempaccount.com <mi...@gtempaccount.com> #2Jun 6, 2019 12:28PM

In SystemJobService, it can expect null, and able to tolerance null from WorkManagerImpl.getInstance, due to auto-backup reason.

@Override
public void onCreate() {
super.onCreate();
mWorkManagerImpl = WorkManagerImpl.getInstance(getApplicationContext());
if (mWorkManagerImpl == null) {
// This can occur if...
// 1. The app is performing an auto-backup. Prior to O, JobScheduler could erroneously
// try to send commands to JobService in this state (

b/32180780

). Since neither
// Application#onCreate nor ContentProviders have run, WorkManager won't be
// initialized. In this case, we should ignore all JobScheduler commands and tell it
// to retry.
But, current WorkManagerImpl.getInstance(Context context) implementation is that, it will never return null but throw IllegalStateException.

Isn't there's conflict among these 2 SystemJobService.onCreate logic, and WorkManagerImpl.getInstance logic?

uc...@google.com <uc...@google.com> Jun 6, 2019 09:24PM

Assigned to lf...@google.com.

lf...@google.com <lf...@google.com> #3Jun 7, 2019 02:59PM

Reassigned to jm...@google.com.

Project: platform/frameworks/support
Branch: androidx-master-dev

commit e14104eb7008f82edd50b37e16bd119b307e0554
Author: Sumir Kataria <sumir@google.com>
Date: Mon Jun 24 10:50:57 2019

Fix for JobScheduler calls when backup is in progress.

The original fix (ag/Ia1604b7c4b98f6b31869e1161a0c1efce7fe46f2) relied
on a null-check, but the new version of WorkManager.getInstance(Context)
with the Context param doesn't return null; it throws an Exception. This
CL updates the three places where we explicitly check for the return value
internally:

1. SystemJobService (the main place where this would manifest)
2. RescheduleReceiver
3. WorkManagerTestInitHelper (for consistency)

Fixes: 135858602
Test: Ran existing tests
Change-Id: Ia232869712d0c78fd80e91d0a863b8c50a080400

M work/workmanager-testing/src/main/java/androidx/work/testing/WorkManagerTestInitHelper.java
M work/workmanager/src/main/java/androidx/work/impl/background/systemalarm/RescheduleReceiver.java
M work/workmanager/src/main/java/androidx/work/impl/background/systemjob/SystemJobService.java

https://android-review.googlesource.com/988026

https://goto.google.com/android-sha1/e14104eb7008f82edd50b37e16bd119b307e0554

1c...@gmail.com <1c...@gmail.com> #4Jun 7, 2019 03:17PM

Thanks you so much for the speedy fixed!

May I know when will it be ready for production? As, currently, this IllegalStateException is impacting our users.

adb.jpg

375 KB

View

Download

be...@gmail.com <be...@gmail.com> #5Jun 7, 2019 07:04PM

Hello, please look for this later in the week. If you want to work around this bug specifically and don't need on-demand initialization, you can use the old (deprecated) WorkManager.getInstance() method for now.

jm...@google.com <jm...@google.com> #6Jun 11, 2019 07:40PM

Marked as fixed.

Hello. Thanks for respond. I surely will keep a pair of eye on the next release :)

Yes. We don't need on-demand initialization. May I know how does using old (deprecated) WorkManager.getInstance() in our app code, able to bypass this problem? Isn't the crash is origin from library internal SystemJobService?

We once thinking to bypass this problem, by switching back to Version 2.0.1 (The version just before WorkManager.getInstance(Context) is introduced). However, we notice Room version is being changed in between. Downgrading WorkManager version, might cause additional SQLite problem.

le...@gmail.com <le...@gmail.com> #7Jun 11, 2019 09:06PM

Sorry, you are correct that moving to the deprecated method will not help you here. I would advise waiting for the release later this week. And thank you very much for finding this bug and doing the research to find the underlying issue.

I am curious: do you actually have reports of this bug on Android 9? It should've been fixed in the platform layer at that point. If possible, can you share any Android 9 specific logs/bugreports/stacktraces with device models?

v....@gmail.com <v....@gmail.com> #8Jul 14, 2019 12:02PM

OK. Finger crossed users will not leave our app. I will follow the Green Dinosaur in Twitter, to wait for his announcement.

Based on your code comment, I thought this problem shouldn't occur in new Android but it happens some how. This is the log

Asus ZenFone 5 (ZE620KL) (ASUS_X00QD), Android 9 (Happen 2 times)
Asus ZenFone 5Z (ZS620KL/ZS621KL) (ASUS_Z01R_1), Android 9 (Happen 1 time)

3 incidents are having same log trace as below

java.lang.RuntimeException:
at android.app.ActivityThread.handleCreateService (ActivityThread.java:3570)
at android.app.ActivityThread.access$1300 (ActivityThread.java:200)
at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1672)
at android.os.Handler.dispatchMessage (Handler.java:106)
at android.os.Looper.loop (Looper.java:198)
at android.app.ActivityThread.main (ActivityThread.java:6732)
at java.lang.reflect.Method.invoke (Method.java)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:493)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:858)
Caused by: java.lang.IllegalStateException:
at androidx.work.impl.WorkManagerImpl.getInstance (WorkManagerImpl.java:142)
at androidx.work.impl.background.systemjob.SystemJobService.onCreate (SystemJobService.java:53)
at android.app.ActivityThread.handleCreateService (ActivityThread.java:3558)
at android.app.ActivityThread.access$1300 (ActivityThread.java:200)
at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1672)
at android.os.Handler.dispatchMessage (Handler.java:106)
at android.os.Looper.loop (Looper.java:198)
at android.app.ActivityThread.main (ActivityThread.java:6732)
at java.lang.reflect.Method.invoke (Method.java)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:493)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:858)

I attach the screenshot of Google Play Console as well. (I expect the stack trace should print programmer's message side-by-side with IllegalStateException. But it doesn't)

Feel free to let me know if you need any information from my side. Happy to help.

jm...@google.com <jm...@google.com> #9Jul 15, 2019 08:12PM

Thanks, we'll investigate this internally.

cv...@gmail.com <cv...@gmail.com> #10Jul 16, 2019 12:23AM

Hello, wondering whether the fix will be released in another one, or two days. As, users start to complain and leaving our app, due to increased crash rate :(

Thanks.

cv...@gmail.com <cv...@gmail.com> #11Jul 16, 2019 12:27AM

Hi, we're still aiming to get this out this week.

si...@gmail.com <si...@gmail.com> #12Jul 16, 2019 05:12PM

still have bug:

trace:
5 java.lang.IllegalStateException:WorkManager needs to be initialized via a ContentProvider#onCreate() or an Application#onCreate().
6 androidx.work.impl.background.systemjob.SystemJobService.onCreate(SystemJobService.java:68)
7 android.app.ActivityThread.handleCreateService(ActivityThread.java:3133)
8 android.app.ActivityThread.access$1900(ActivityThread.java:196)
9 android.app.ActivityThread$H.handleMessage(ActivityThread.java:1622)
10 com.android.tony.defenselib.hook.HookHandle$1.handleMessage(HookHandle.java:30)
11 android.os.Handler.dispatchMessage(Handler.java:107)
12 android.os.Looper.loop(Looper.java:210)
13 android.app.ActivityThread.main(ActivityThread.java:5982)
14 java.lang.reflect.Method.invoke(Native Method)
15 com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:852)
16 com.android.internal.os.ZygoteInit.main(ZygoteInit.java:742)

this code cause crash:

if (!Application.class.equals(getApplication().getClass())) {
// During auto-backup, we don't get a custom Application subclass. This code path
// indicates we are either performing auto-backup or the user never used a custom
// Application class (or both).
throw new IllegalStateException("WorkManager needs to be initialized via a "
+ "ContentProvider#onCreate() or an Application#onCreate().");
}

my analysis:

code in handleCreateService() in ActivityThread.java:
" Application app = packageInfo.makeApplication(false, mInstrumentation);
service.attach(context, this,

data.info.name, data.token, app, ActivityManager.getService())
"

handleCreateService--->. Application app = packageInfo.makeApplication(false, mInstrumentation); ---> forceDefaultAppClass is always false-->if have custom Application,will make custom Application ---> service.attach(context, this,

data.info.name, data.token, app, ActivityManager.getService()); ---> so getApplication() in service get custom application
--> if have customApplication, the code : "Application.class.equals(getApplication().getClass()" in Service will be false , even it's in backup mode

Message last modified on Jul 16, 2019 05:15PM

si...@gmail.com <si...@gmail.com> #13Jul 24, 2019 07:13PM

i'm also having the same crash, here is the relevant stacktrace:

compileSdkVersion 30
implementation 'androidx.work:work-runtime-ktx:2.4.0'

Crash
TCT (Alcatel) 5056D
Android 6.0 (SDK 23)
48.aab
2 hours ago

java.lang.RuntimeException:
at android.app.ActivityThread.handleCreateService (ActivityThread.java:2887)
at android.app.ActivityThread.access$1900 (ActivityThread.java:150)
at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1427)
at android.os.Handler.dispatchMessage (Handler.java:102)
at android.os.Looper.loop (Looper.java:148)
at android.app.ActivityThread.main (ActivityThread.java:5417)
at java.lang.reflect.Method.invoke (Method.java)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:726)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:616)
Caused by: java.lang.IllegalStateException:
at androidx.work.impl.background.systemjob.SystemJobService.onCreate (SystemJobService.java:2)
at android.app.ActivityThread.handleCreateService (ActivityThread.java:2877)
at android.app.ActivityThread.access$1900 (ActivityThread.java:150)
at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1427)
at android.os.Handler.dispatchMessage (Handler.java:102)
at android.os.Looper.loop (Looper.java:148)
at android.app.ActivityThread.main (ActivityThread.java:5417)
at java.lang.reflect.Method.invoke (Method.java)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:726)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:616)

What could the walkaround this issue? Is there another way to initialize the WorkManager instance? I'm using

private fun getWorkManager(): WorkManager =
try {
WorkManager.getInstance(App.context)
} catch (e: Exception) {
e.printStackTrace()
sleep(100)
getWorkManager()
}

3l...@gmail.com <3l...@gmail.com> #14Jul 29, 2019 05:36PM

Same Error on production when call WorkManager.getInstance(context):
Library version: androidx.work:work-runtime:2.4.0

Samsung Galaxy S8 (dreamlte), 3840MB RAM, Android 9

java.lang.RuntimeException:
at android.app.ActivityThread.handleBindApplication (ActivityThread.java:6227)
at android.app.ActivityThread.access$1200 (ActivityThread.java:237)
at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1785)
at android.os.Handler.dispatchMessage (Handler.java:106)
at android.os.Looper.loop (Looper.java:214)
at android.app.ActivityThread.main (ActivityThread.java:7050)
at java.lang.reflect.Method.invoke (Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:494)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:965)

Caused by: java.lang.IllegalStateException:
at androidx.work.impl.WorkManagerImpl.getInstance (WorkManagerImpl.java:150)
at androidx.work.WorkManager.getInstance (WorkManager.java:184)
at br.com.rcgm.dicaslotofacilfull.task.WorkRequestSincronizarConcurso.enfileirar (WorkRequestSincronizarConcurso.java:20)
at br.com.rcgm.dicaslotofacilfull.BaseApplication.onCreate (BaseApplication.java:23)
at android.app.Instrumentation.callApplicationOnCreate (Instrumentation.java:1154)
at android.app.ActivityThread.handleBindApplication (ActivityThread.java:6222)

mo...@gmail.com <mo...@gmail.com> #15Aug 16, 2019 05:55AM

Hi,

I'm also facing same issue, in few devices.

Instance access : WorkManager.getInstance()
I'm not doing on-demand Initialization.
version used: 'androidx.work:work-runtime:2.3.4'

Device details
Brand: samsung
Model: Galaxy J2 Pro
Android version: 6.0.1

Fatal Exception: java.lang.RuntimeException: Unable to create service androidx.work.impl.background.systemjob.SystemJobService: java.lang.IllegalStateException: WorkManager needs to be initialized via a ContentProvider#onCreate() or an Application#onCreate().
at android.app.ActivityThread.handleCreateService(ActivityThread.java:3883)
at android.app.ActivityThread.-wrap8(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1909)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:148)
at android.app.ActivityThread.main(ActivityThread.java:7325)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1230)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1120)
Caused by java.lang.IllegalStateException: WorkManager needs to be initialized via a ContentProvider#onCreate() or an Application#onCreate().
at androidx.work.impl.background.systemjob.SystemJobService.onCreate(SystemJobService.java:73)
at android.app.ActivityThread.handleCreateService(ActivityThread.java:3873)
at android.app.ActivityThread.-wrap8(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1909)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:148)
at android.app.ActivityThread.main(ActivityThread.java:7325)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1230)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1120)

mo...@gmail.com <mo...@gmail.com> #16Aug 16, 2019 05:56AM

i have the same issue

le...@gmail.com <le...@gmail.com> #17Sep 26, 2019 11:51PM

deleted

zo...@gmail.com <zo...@gmail.com> #18Sep 29, 2019 01:05PM

Still seeing this issue in 2.5.0 using default WorkManager.getInstance() initialization. How can we prevent this situation from occurring?

if (!Application.class.equals(getApplication().getClass())) {
// During auto-backup, we don't get a custom Application subclass. This code path
// indicates we are either performing auto-backup or the user never used a custom
// Application class (or both).
throw new IllegalStateException("WorkManager needs to be initialized via a "
+ "ContentProvider#onCreate() or an Application#onCreate().");
}

za...@gmail.com <za...@gmail.com> #19Oct 13, 2019 11:32AM

this issue on workManager 2.5.0 when initialize WorkManager in background thread, bring it back to UI thread

ke...@gmail.com <ke...@gmail.com> #20Oct 31, 2019 07:27PM

I begin to see this issue after using "on demand Initialization"

Stacktrace:
Caused by java.lang.IllegalStateException
WorkManager needs to be initialized via a ContentProvider#onCreate() or an Application#onCreate().
androidx.work.impl.background.systemjob.SystemJobService.onCreate (SystemJobService.java:73)
android.app.ActivityThread.handleCreateService (ActivityThread.java:3833)
android.app.ActivityThread.access$1500 (ActivityThread.java:229)
android.app.ActivityThread$H.handleMessage (ActivityThread.java:1881)
android.os.Handler.dispatchMessage (Handler.java:106)
android.os.Looper.loop (Looper.java:226)
android.app.ActivityThread.main (ActivityThread.java:7178)
java.lang.reflect.Method.invoke (Method.java)
com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:503)
com.android.internal.os.ZygoteInit.main (ZygoteInit.java:942)

For now, the device affected is
android 9 Realme.

Work Manager version: 2.6.0

ko...@gmail.com <ko...@gmail.com> #21Oct 31, 2019 08:30PM

Still happening with WorkManager 2.7.1 Samsung Galaxy S21 Ultra 5G Android 12 (SDK 31)

java.lang.RuntimeException: 
  at android.app.ActivityThread.handleCreateService (ActivityThread.java:4953)
  at android.app.ActivityThread.access$1900 (ActivityThread.java:310)
  at android.app.ActivityThread$H.handleMessage (ActivityThread.java:2300)
  at android.os.Handler.dispatchMessage (Handler.java:106)
  at android.os.Looper.loopOnce (Looper.java:226)
  at android.os.Looper.loop (Looper.java:313)
  at android.app.ActivityThread.main (ActivityThread.java:8669)
  at java.lang.reflect.Method.invoke (Native Method)
  at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:571)
  at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1135)
Caused by: java.lang.IllegalStateException: 
  at androidx.work.impl.WorkManagerImpl.getInstance (WorkManagerImpl.java:158)
  at androidx.work.impl.foreground.SystemForegroundDispatcher.<init> (SystemForegroundDispatcher.java:105)
  at androidx.work.impl.foreground.SystemForegroundService.initializeDispatcher (SystemForegroundService.java:96)
  at androidx.work.impl.foreground.SystemForegroundService.onCreate (SystemForegroundService.java:59)
  at android.app.ActivityThread.handleCreateService (ActivityThread.java:4940)
  at android.app.ActivityThread.access$1900 (ActivityThread.java:310)
  at android.app.ActivityThread$H.handleMessage (ActivityThread.java:2300)
  at android.os.Handler.dispatchMessage (Handler.java:106)
  at android.os.Looper.loopOnce (Looper.java:226)
  at android.os.Looper.loop (Looper.java:313)
  at android.app.ActivityThread.main (ActivityThread.java:8669)
  at java.lang.reflect.Method.invoke (Native Method)
  at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:571)
  at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1135)

scripts_linux_mk-sdcard-img.sh

6.2 KB

View

Download

ab...@hotmail.com <ab...@hotmail.com> Feb 8, 2020 07:14AM

scripts_linux_mk-sdcard-img.sh

6.2 KB

View

Download

fr...@gmail.com <fr...@gmail.com> #22Feb 29, 2020 04:42PM

We recently moved our WorkManager initialization to the default pattern and have started seeing this same issue.

java.lang.RuntimeException: Unable to create service androidx.work.impl.background.systemjob.SystemJobService: java.lang.IllegalStateException: WorkManager needs to be initialized via a ContentProvider#onCreate() or an Application#onCreate().
        at android.app.ActivityThread.handleCreateService(ActivityThread.java:5073)
        at android.app.ActivityThread.-$$Nest$mhandleCreateService(Unknown)
        at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2425)
        at android.os.Handler.dispatchMessage(Handler.java:106)
        at android.os.Looper.loopOnce(Looper.java:226)
        at android.os.Looper.loop(Looper.java:313)
        at android.app.ActivityThread.main(ActivityThread.java:8741)
        at java.lang.reflect.Method.invoke(Method.java:-2)
        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:571)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1067)

Caused by: java.lang.IllegalStateException: WorkManager needs to be initialized via a ContentProvider#onCreate() or an Application#onCreate().
        at androidx.work.impl.background.systemjob.SystemJobService.onCreate(SystemJobService:73)
        at android.app.ActivityThread.handleCreateService(ActivityThread.java:5060)
        at android.app.ActivityThread.-$$Nest$mhandleCreateService(Unknown)
        at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2425)
        at android.os.Handler.dispatchMessage(Handler.java:106)
        at android.os.Looper.loopOnce(Looper.java:226)
        at android.os.Looper.loop(Looper.java:313)
        at android.app.ActivityThread.main(ActivityThread.java:8741)
        at java.lang.reflect.Method.invoke(Method.java:-2)
        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:571)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1067)

jd...@gmail.com <jd...@gmail.com> #23Mar 7, 2020 07:26AM

I would check to make sure that the app is not a multi-process app. If it is, you will need your Application to additionally sub-class Configuration.Provider or additionally define a second provider for the other process.

jo...@gmail.com <jo...@gmail.com> #24Apr 9, 2020 11:19PM

Hi all, I am also facing the same crash in Work Manager 2.7.1 with on-demand initialization in Samsung X-Cover Pro(31), sdk 32. There's no concrete scenario for this crash to happen, it happens randomly at any screen. Plus the auto-backup is disabled in my app which was listed as one of the factors responsible for the crash. Can someone please assist me with a way to fix/handle this crash?

ge...@gmail.com <ge...@gmail.com> #25Apr 15, 2020 11:09PM

Hi all , i use workManager 2.7.0 face some crash "IllegalStateExceptionWorkManager needs to be initialized via a ContentProvider#onCreate() or an Application#onCreate()" . i am sure app manifest allowBackUp=false and initWorkManger in every process. Can someone please assist me with a way to fix/handle this crash?

Message last modified on Apr 15, 2020 11:10PM

js...@gmail.com <js...@gmail.com> #26Apr 23, 2020 12:22AM

I'm experience the same problem. I used suspend function to init WorkManager and used Dispatchers.Default as a scope to launch. I'm going to use runBlocking instead

da...@gmail.com <da...@gmail.com> #27Apr 24, 2020 12:19AM

-hotlist Google domain
+hotlist 2367385

Message last modified on Apr 24, 2020 12:31AM

[Deleted User] <[Deleted User]> #28Apr 24, 2020 03:40PM

---------- ထပ်ဆင့်ပေးပို့သည့်မက်ဆေ့ချ် ----------
From: <buganizer-system@google.com>
Date: 24 ဧပြီ 2020 6:50 AM
Subject: Re:

Issue 134613180

: Updating to platform tools 29.0.0 results in
continuous stream of adb.exe crash dialogs, at least on Windows 8.1
To: <b-system+591006804@google.com>
မိတ္တူ: <kok129873@gmail.com>

Replying to this email means your email address will be shared with the
team that works on this product.

https://issuetracker.google.com/issues/134613180

*Changed*

*da...@gmail.com <da...@gmail.com> added

comment #27

https://issuetracker.google.com/issues/134613180#comment27>:*

-hotlist Google domain +hotlist 2367385

_______________________________

*Reference Info: 134613180 Updating to platform tools 29.0.0 results in
continuous stream of adb.exe crash dialogs, at least on Windows 8.1*
component: Android Public Tracker > App Development > Android Studio >
Emulator <

https://issuetracker.google.com/components/192727>
status: Fixed
reporter: le...@gmail.com
assignee: jm...@google.com
cc: bo...@google.com, jm...@google.com, le...@gmail.com
type: Bug
priority: P1
severity: S2
duplicate issue: 134627083
<

https://issuetracker.google.com/issues/134627083>
hotlist: Reviewed (L1) <

https://issuetracker.google.com/hotlists/712415>
retention: Component default

Generated by Google IssueTracker notification system

You're receiving this email because you are subscribed to updates on Google
IssueTracker

issue 134613180

https://issuetracker.google.com/issues/134613180> where you have the role:
starred.
Unsubscribe from this issue.
<

https://issuetracker.google.com/issues/134613180?unsubscribe=true>

[Deleted User] <[Deleted User]> #29May 10, 2020 12:12PM

29 ေဖ 2020 11:12 PM တွင် <buganizer-system@google.com> ရေးခဲ့သည်မှာ။ ။

- Show quoted text -

an...@gmail.com <an...@gmail.com> #30May 31, 2020 06:37AM

Mmmank

ou...@gmail.com <ou...@gmail.com> #31Jul 7, 2020 11:08AM

TITsovneMakara@gmail.com

Message last modified on Jul 7, 2020 11:09AM

aa...@gmail.com <aa...@gmail.com> #32Oct 5, 2020 02:09PM

Feedback

aa...@gmail.com <aa...@gmail.com> #33Oct 5, 2020 02:10PM

aaireill111@gmail.com

ab...@gmail.com <ab...@gmail.com> #34Nov 19, 2020 12:49AM

انتهاك خصوصية

ab...@gmail.com <ab...@gmail.com> #35Dec 15, 2020 07:06AM

My privacy was violated by an unidentified person, opening several web pages with all my personal data, and I have a forged and incorrect user agreement for my account. I ask you to block the unknown person and help me update my data.

Please help me to modify the privacy of my account to private privacy and not to participate categorically and the presence of security for privacy and not tampering with it.

za...@gmail.com <za...@gmail.com> #36Dec 15, 2020 07:14AM

On Wed, Nov 18, 2020, 6:50 PM <buganizer-system@google.com> wrote:

- Show quoted text -

dd...@gmail.com <dd...@gmail.com> #37Dec 16, 2020 06:01AM

What is this and why am I in this can someone please explain

On Tue, Dec 15, 2020, 2:06 AM <buganizer-system@google.com> wrote:

- Show quoted text -

06...@gmail.com <06...@gmail.com> #38Dec 28, 2020 02:05PM

https://console.aws.amazon.com/support/home?#/case/?caseId=7795210011&displayId=7795210011&language=en

ka...@gmail.com <ka...@gmail.com> #39Jan 27, 2021 04:17AM

حلم 95458 من مصر 🇪🇬 201551145918كرم محمد عبد العزيز عبد العال حلم حلم حلم حلم حلم حلم حلم 2021

ka...@gmail.com <ka...@gmail.com> #40Jan 27, 2021 04:20AM

حلم حلم حلم حلم حلم حلم حلم 95458 مصر 🇪🇬 محافظة الاسكندرية كرم محمد عبد العزيز عبد العال 201551145918 حلم حلم حلم حلم يارب شيك يارب mbc 2021

si...@gmail.com <si...@gmail.com> #41Mar 19, 2021 01:36PM

I installed 29.0.1 via the SDK Manager. This problem feels fixed to me.

to...@gmail.com <to...@gmail.com> #42Apr 23, 2021 07:45PM

https://drive.google.com/file/d/0B8TBbCbAQEhJVDJYWmtpMm1GSkU/view?usp=drive_web (225)

ab...@gmail.com <ab...@gmail.com> #43Sep 11, 2021 12:11PM

hi my name abdulrahman afghan
help me japan tool

fl...@gmail.com <fl...@gmail.com> #44Sep 11, 2021 10:53PM

On Sat, Sep 11, 2021, 8:11 AM <buganizer-system@google.com> wrote:

- Show quoted text -

m....@gmail.com <m....@gmail.com> #45Sep 12, 2021 02:10AM

good bay!

1381662341mohamadsalmanpor

در تاریخ شنبه ۱۱ سپتامبر ۲۰۲۱،‏ ۱۶:۴۱ <buganizer-system@google.com> نوشت:

- Show quoted text -

mi...@gmail.com <mi...@gmail.com> #46Oct 2, 2021 10:50AM

https://drive.google.com/file/d/1IdB9_C-qvVKHshc-xekJws6oo-FScA15/view?usp=drive_web (Backup-codes-miwavaso.txt)

m....@gmail.com <m....@gmail.com> #47Oct 2, 2021 11:03AM

1381662341:issu

1381662341mohamadsalmanpor

در تاریخ شنبه ۲ اکتبر ۲۰۲۱،‏ ۲:۲۰ بعدازظهر <buganizer-system@google.com>
نوشت:

- Show quoted text -

mo...@gmail.com <mo...@gmail.com> #48Oct 4, 2021 11:51AM

Hjh

at...@gmail.com <at...@gmail.com> #49Dec 25, 2022 11:26AM

My device esim update 13 on drive

Message last modified on Dec 25, 2022 11:34AM

ly...@gmail.com <ly...@gmail.com> #50Oct 30, 2023 10:16PM

mi...@gmail.com <mi...@gmail.com> #51Nov 29, 2023 10:35PM

El sáb., 11 de septiembre de 2021 8:11 p. m., <buganizer-system@google.com>
escribió:

- Show quoted text -

Issue 134613180

Description

Issue summary

Comments

mi...@gtempaccount.com <mi...@gtempaccount.com> #2Jun 6, 2019 12:28PM

uc...@google.com <uc...@google.com> Jun 6, 2019 09:24PM

lf...@google.com <lf...@google.com> #3Jun 7, 2019 02:59PM

1c...@gmail.com <1c...@gmail.com> #4Jun 7, 2019 03:17PM

be...@gmail.com <be...@gmail.com> #5Jun 7, 2019 07:04PM

jm...@google.com <jm...@google.com> #6Jun 11, 2019 07:40PM

le...@gmail.com <le...@gmail.com> #7Jun 11, 2019 09:06PM

v....@gmail.com <v....@gmail.com> #8Jul 14, 2019 12:02PM

jm...@google.com <jm...@google.com> #9Jul 15, 2019 08:12PM

cv...@gmail.com <cv...@gmail.com> #10Jul 16, 2019 12:23AM

cv...@gmail.com <cv...@gmail.com> #11Jul 16, 2019 12:27AM

si...@gmail.com <si...@gmail.com> #12Jul 16, 2019 05:12PM

si...@gmail.com <si...@gmail.com> #13Jul 24, 2019 07:13PM

3l...@gmail.com <3l...@gmail.com> #14Jul 29, 2019 05:36PM

mo...@gmail.com <mo...@gmail.com> #15Aug 16, 2019 05:55AM

mo...@gmail.com <mo...@gmail.com> #16Aug 16, 2019 05:56AM

le...@gmail.com <le...@gmail.com> #17Sep 26, 2019 11:51PM

zo...@gmail.com <zo...@gmail.com> #18Sep 29, 2019 01:05PM

za...@gmail.com <za...@gmail.com> #19Oct 13, 2019 11:32AM

ke...@gmail.com <ke...@gmail.com> #20Oct 31, 2019 07:27PM

ko...@gmail.com <ko...@gmail.com> #21Oct 31, 2019 08:30PM

ab...@hotmail.com <ab...@hotmail.com> Feb 8, 2020 07:14AM

fr...@gmail.com <fr...@gmail.com> #22Feb 29, 2020 04:42PM

jd...@gmail.com <jd...@gmail.com> #23Mar 7, 2020 07:26AM

jo...@gmail.com <jo...@gmail.com> #24Apr 9, 2020 11:19PM

ge...@gmail.com <ge...@gmail.com> #25Apr 15, 2020 11:09PM

js...@gmail.com <js...@gmail.com> #26Apr 23, 2020 12:22AM

da...@gmail.com <da...@gmail.com> #27Apr 24, 2020 12:19AM

[Deleted User] <[Deleted User]> #28Apr 24, 2020 03:40PM

[Deleted User] <[Deleted User]> #29May 10, 2020 12:12PM

an...@gmail.com <an...@gmail.com> #30May 31, 2020 06:37AM

ou...@gmail.com <ou...@gmail.com> #31Jul 7, 2020 11:08AM

aa...@gmail.com <aa...@gmail.com> #32Oct 5, 2020 02:09PM

aa...@gmail.com <aa...@gmail.com> #33Oct 5, 2020 02:10PM

ab...@gmail.com <ab...@gmail.com> #34Nov 19, 2020 12:49AM

ab...@gmail.com <ab...@gmail.com> #35Dec 15, 2020 07:06AM

za...@gmail.com <za...@gmail.com> #36Dec 15, 2020 07:14AM

dd...@gmail.com <dd...@gmail.com> #37Dec 16, 2020 06:01AM

06...@gmail.com <06...@gmail.com> #38Dec 28, 2020 02:05PM

ka...@gmail.com <ka...@gmail.com> #39Jan 27, 2021 04:17AM

ka...@gmail.com <ka...@gmail.com> #40Jan 27, 2021 04:20AM

si...@gmail.com <si...@gmail.com> #41Mar 19, 2021 01:36PM

to...@gmail.com <to...@gmail.com> #42Apr 23, 2021 07:45PM

ab...@gmail.com <ab...@gmail.com> #43Sep 11, 2021 12:11PM

fl...@gmail.com <fl...@gmail.com> #44Sep 11, 2021 10:53PM

m....@gmail.com <m....@gmail.com> #45Sep 12, 2021 02:10AM

mi...@gmail.com <mi...@gmail.com> #46Oct 2, 2021 10:50AM

m....@gmail.com <m....@gmail.com> #47Oct 2, 2021 11:03AM

mo...@gmail.com <mo...@gmail.com> #48Oct 4, 2021 11:51AM

at...@gmail.com <at...@gmail.com> #49Dec 25, 2022 11:26AM

ly...@gmail.com <ly...@gmail.com> #50Oct 30, 2023 10:16PM

mi...@gmail.com <mi...@gmail.com> #51Nov 29, 2023 10:35PM

Add comment

Issue metadata