Andrew Fletcher published: 3 August 2022 2 minutes read
What I'm seeing in Android Studio when attempting to run the emulator?
Launching 'app' on Pixel 5 API 33.
Install successfully finished in 153 ms.
$ adb shell am start -n "{project}.app.MainActivity" -a android.intent.action.MAIN -c android.intent.category.LAUNCHER
Timed out waiting for process (com.{project}.app) to appear on Pixel_5_API_33 [emulator-5554].
As an error, this gives no intel. So go to logcat tab and change the 3rd dropdown to error
what do you see?
For me, I get multiple errors, I'll reduce the list by removing duplicates
E/android.hardware.power.stats@1.0-service-mock: Failed to getEnergyData
1359-17040/com.google.android.gms E/WakeLock: GCM_HB_ALARM release without a matched acquire!
17093-17318/? E/JavaBinder: !!! FAILED BINDER TRANSACTION !!! (parcel size = 660)
1199-1537/com.android.bluetooth E/bluetooth: packages/modules/Bluetooth/system/gd/os/linux_generic/files.cc:202 FileCreatedTime: unable to read '/data/misc/bluetooth/logs/btsnooz_hci.log' file metadata, error: No such file or directory
1359-7580/com.google.android.gms E/WakeLock: GCM_HB_ALARM release without a matched acquire!
1359-1912/com.google.android.gms E/JavaBinder: !!! FAILED BINDER TRANSACTION !!! (parcel size = 252)
1359-17352/com.google.android.gms E/WorkSourceUtil: Could not find package: com.google.android.gms.westworld
nagedChannel allocation site
at dfar.<init>(:com.google.android.gms@221821047@22.18.21 (190800-453244992):3)
at dfas.<init>(:com.google.android.gms@221821047@22.18.21 (190800-453244992):2)
at detc.a(:com.google.android.gms@221821047@22.18.21 (190800-453244992):22)
at wql.c(:com.google.android.gms@221821047@22.18.21 (190800-453244992):22)
at wql.d(:com.google.android.gms@221821047@22.18.21 (190800-453244992):1)
at ahmg.a(:com.google.android.gms@221821047@22.18.21 (190800-453244992):57)
at wpr.call(:com.google.android.gms@221821047@22.18.21 (190800-453244992):2)
at java.util.concurrent.FutureTask.run(FutureTask.java:264)
at wwq.c(:com.google.android.gms@221821047@22.18.21 (190800-453244992):6)
at wwq.run(:com.google.android.gms@221821047@22.18.21 (190800-453244992):8)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1137)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:637)
at xbv.run(:com.google.android.gms@221821047@22.18.21 (190800-453244992):0)
1359-17040/com.google.android.gms E/WakeLock: GCM_HB_ALARM release without a matched acquire!
1359-17040/com.google.android.gms E/NetworkScheduler.TED: Dropping task as app's play services SDK version does not support Android O. Either update the SDK or lower your app's target SDK version. Canceling all tasks for the service: ComponentInfo{com.google.android.gms/com.google.android.gms.ads.social.GcmSchedulerWakeupService}
359-17665/com.google.android.gms E/NetworkScheduler.ATC: Called cancelTask for already completed task com.google.android.gms/.ads.social.GcmSchedulerWakeupService{u=0 tag="ads.social.doritos" trigger=window{period=43200s,flex=1800s,earliest=-1354s,latest=805s} requirements=[NET_CONNECTED] attributes=[PERSISTED,RECURRING] scheduled=-42394s last_run=0s exec_window_multiplier=1.0000 jid=N/A status=PENDING retries=0 client_lib=GMS_TASK_SCHEDULER-221821000} :1 [CONTEXT service_id=218 ]
1359-17040/com.google.android.gms E/NetworkScheduler.TED: Dropping task as app's play services SDK version does not support Android O. Either update the SDK or lower your app's target SDK version. Canceling all tasks for the service: ComponentInfo{com.google.android.gms/com.google.android.gms.ads.social.GcmSchedulerWakeupService}
Related articles
Andrew Fletcher
•
31 Oct 2023
Android icon not changing
If the Android app icon is not changing from the default icon (in my situation this was the Capacitor icon), here are some steps to troubleshoot and resolve the issue: Check the Icon FilesEnsure that you have provided the correct icon files in the appropriate directory. In a Capacitor project,...
Andrew Fletcher
•
27 Oct 2023
Working through android.permission.REQUEST_INSTALL_PACKAGES blocking releases
I'm receiving an issue with a previous release on Google Playandroid.permission.REQUEST_INSTALL_PACKAGESI'm seeing the following message in Google PlayRequest install packages permission
error - Not started - Your app isn't compliant
A permission that allows your app to install packages. If your...
Andrew Fletcher
•
25 Oct 2023
keytool error: java.io.IOException: keystore password was incorrect
The "keystore password was incorrect" error in keytool indicates that the password you provided when trying to access or modify a keystore is incorrect. To resolve this issue, you can follow these steps: Verify the Correct PasswordDouble-check that you are entering the correct password for the...