os-issue-tracker icon indicating copy to clipboard operation
os-issue-tracker copied to clipboard
verified publisher icon GrapheneOS

Google Play Services Crash

Open jesse-bonzo opened this issue 9 months ago • 17 comments 

type: crash
osVersion: google/shiba/shiba:15/BP1A.250305.019/2025032100:user/release-keys
package: com.google.android.gms:250832035, targetSdk 35
process: com.google.android.gms
processUptime: 682253 + 838 ms
installer: app.grapheneos.apps
GmsCompatConfig version: 154

java.lang.IllegalArgumentException: accountName must be provided
	at assu.q(:com.google.android.gms@[email protected] (260400-731361394):12)
	at xde.e(:com.google.android.gms@[email protected] (260400-731361394):3)
	at djcu.b(:com.google.android.gms@[email protected] (260400-731361394):126)
	at diff.f(:com.google.android.gms@[email protected] (260400-731361394):13)
	at byag.fK(:com.google.android.gms@[email protected] (260400-731361394):1)
	at byaq.run(:com.google.android.gms@[email protected] (260400-731361394):54)
	at fgkp.run(:com.google.android.gms@[email protected] (260400-731361394):21)
	at atim.c(:com.google.android.gms@[email protected] (260400-731361394):50)
	at atim.run(:com.google.android.gms@[email protected] (260400-731361394):76)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1156)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:651)
	at atnz.run(:com.google.android.gms@[email protected] (260400-731361394):8)
	at java.lang.Thread.run(Thread.java:1119)
	Suppressed: fglc: 
		at tk_trace.198-PerformValuablesOperation(Unknown Source:0)
		at tk_trace.pay-PayChimeraService-IPayService_139(Unknown Source:0)

jesse-bonzo avatar Mar 23 '25 17:03 jesse-bonzo

How was this triggered?

thestinger avatar Mar 23 '25 17:03 thestinger

I'm not sure. It's happened a few times over the past few days. Usually I wake up to the notification that Play Services crashed. I do have two Google accounts logged in, but otherwise I'm really not sure.

On Sun, Mar 23, 2025 at 10:34 AM Daniel Micay @.***> wrote:

How was this triggered?

— Reply to this email directly, view it on GitHub https://github.com/GrapheneOS/os-issue-tracker/issues/5133#issuecomment-2746330611, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHJ6ZA4Z7MAE3BBP2NPG2WD2V3WBJAVCNFSM6AAAAABZTIFTQCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONBWGMZTANRRGE . You are receiving this because you authored the thread.Message ID: @.***> [image: thestinger]thestinger left a comment (GrapheneOS/os-issue-tracker#5133) https://github.com/GrapheneOS/os-issue-tracker/issues/5133#issuecomment-2746330611

How was this triggered?

— Reply to this email directly, view it on GitHub https://github.com/GrapheneOS/os-issue-tracker/issues/5133#issuecomment-2746330611, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHJ6ZA4Z7MAE3BBP2NPG2WD2V3WBJAVCNFSM6AAAAABZTIFTQCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONBWGMZTANRRGE . You are receiving this because you authored the thread.Message ID: @.***>

jesse-bonzo avatar Mar 23 '25 17:03 jesse-bonzo

Having the same experience as @jesse-bonzo lately. I've been ignoring the crash notifications as everything seems to be working just fine.

type: crash
osVersion: google/bluejay/bluejay:15/BP1A.250305.019/2025032100:user/release-keys
package: com.google.android.gms:250832035, targetSdk 35
sharedUid: com.google.uid.shared
process: com.google.android.gms
processUptime: 200628 + 420 ms
installer: app.grapheneos.apps
GmsCompatConfig version: 154

java.lang.IllegalArgumentException: accountName must be provided
	at assu.q(:com.google.android.gms@[email protected] (260400-731361394):12)
	at xde.e(:com.google.android.gms@[email protected] (260400-731361394):3)
	at djcu.b(:com.google.android.gms@[email protected] (260400-731361394):126)
	at diff.f(:com.google.android.gms@[email protected] (260400-731361394):13)
	at byag.fK(:com.google.android.gms@[email protected] (260400-731361394):1)
	at byaq.run(:com.google.android.gms@[email protected] (260400-731361394):54)
	at fgkp.run(:com.google.android.gms@[email protected] (260400-731361394):21)
	at atim.c(:com.google.android.gms@[email protected] (260400-731361394):50)
	at atim.run(:com.google.android.gms@[email protected] (260400-731361394):76)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1156)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:651)
	at atnz.run(:com.google.android.gms@[email protected] (260400-731361394):8)
	at java.lang.Thread.run(Thread.java:1119)
	Suppressed: fglc: 
		at tk_trace.198-PerformValuablesOperation(Unknown Source:0)
		at tk_trace.pay-PayChimeraService-IPayService_139(Unknown Source:0)

qub1750ul avatar Mar 23 '25 18:03 qub1750ul

@thestinger I was able to get the same error by running a backup.

jesse-bonzo avatar Mar 24 '25 00:03 jesse-bonzo

Same error just now just looking at settings.

type: crash
osVersion: google/komodo/komodo:15/BP1A.250305.020/2025032100:user/release-keys
flags: dev options enabled
package: com.google.android.gms:250832035, targetSdk 35
process: com.google.android.gms
processUptime: 77717 + 1008 ms
installer: app.grapheneos.apps
GmsCompatConfig version: 154

java.lang.IllegalArgumentException: accountName must be provided
	at assu.q(:com.google.android.gms@[email protected] (260400-731361394):12)
	at xde.e(:com.google.android.gms@[email protected] (260400-731361394):3)
	at djcu.b(:com.google.android.gms@[email protected] (260400-731361394):126)
	at diff.f(:com.google.android.gms@[email protected] (260400-731361394):13)
	at byag.fK(:com.google.android.gms@[email protected] (260400-731361394):1)
	at byaq.run(:com.google.android.gms@[email protected] (260400-731361394):54)
	at fgkp.run(:com.google.android.gms@[email protected] (260400-731361394):21)
	at atim.c(:com.google.android.gms@[email protected] (260400-731361394):50)
	at atim.run(:com.google.android.gms@[email protected] (260400-731361394):76)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1156)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:651)
	at atnz.run(:com.google.android.gms@[email protected] (260400-731361394):8)
	at java.lang.Thread.run(Thread.java:1119)
	Suppressed: fglc: 
		at tk_trace.198-PerformValuablesOperation(Unknown Source:0)
		at tk_trace.pay-PayChimeraService-IPayService_139(Unknown Source:0)

snarfy6666 avatar Mar 24 '25 07:03 snarfy6666

Also happens on my Pixel 7 at least once a day (started happening just couple days ago):

type: crash
osVersion: google/cheetah/cheetah:15/AP4A.250105.002/2025010700:user/release-keys
package: com.google.android.gms:250832035, targetSdk 35
sharedUid: com.google.uid.shared
process: com.google.android.gms
processUptime: 26833577 + 343 ms
installer: app.grapheneos.apps
GmsCompatConfig version: 154

java.lang.NullPointerException: Attempt to invoke direct method 'boolean android.os.RecoverySystem.requestLskf(java.lang.String, android.content.IntentSender)' on a null object reference
	at android.os.RecoverySystem.prepareForUnattendedUpdate(RecoverySystem.java:715)
	at efhp.g(:com.google.android.gms@[email protected] (260400-731361394):34)
	at efhw.w(:com.google.android.gms@[email protected] (260400-731361394):48)
	at efhr.a(:com.google.android.gms@[email protected] (260400-731361394):229)
	at efhw.u(:com.google.android.gms@[email protected] (260400-731361394):120)
	at efjt.a(:com.google.android.gms@[email protected] (260400-731361394):120)
	at com.google.android.gms.update.execution.InstallationIntentOperation.onHandleIntent(:com.google.android.gms@[email protected] (260400-731361394):163)
	at com.google.android.chimera.IntentOperation.onHandleIntent(:com.google.android.gms@[email protected] (260400-731361394):2)
	at aorl.onHandleIntent(:com.google.android.gms@[email protected] (260400-731361394):8)
	at sgq.run(:com.google.android.gms@[email protected] (260400-731361394):70)
	at sgp.run(:com.google.android.gms@[email protected] (260400-731361394):152)
	at fgkp.run(:com.google.android.gms@[email protected] (260400-731361394):21)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
	at java.lang.Thread.run(Thread.java:1117)

miczyg1395 avatar Mar 25 '25 17:03 miczyg1395

@miczyg1395 You're on a release from January. Updating to a current OS release properly supporting current Google Play services will resolve that issue.

thestinger avatar Mar 25 '25 17:03 thestinger

@miczyg1395 You're on a release from January. Updating to a current OS release properly supporting current Google Play services will resolve that issue.

You are right. Thanks. However, when I tap to check for updates in the settings, nothing happens. No wonder I haven't been receiving any updates lately... I will reboot the phone and recheck.

miczyg1395 avatar Mar 25 '25 18:03 miczyg1395

@miczyg1395 Make sure you didn't turn off notifications for System Updater. That's likely what you did so you don't get either error or success notifications. You might have meant to turn off the "Already up to date" notification channel but accidentally turned it off as a whole. Check Settings > System > System update > Notification settings (or go to the same menu via the standard Settings > Apps > All apps > Show system in the menu > System Updater > Notifications or Settings > Notifications > App notifications).

thestinger avatar Mar 25 '25 18:03 thestinger

@miczyg1395 Make sure you didn't turn off notifications for System Updater. That's likely what you did so you don't get either error or success notifications. You might have meant to turn off the "Already up to date" notification channel but accidentally turned it off as a whole. Check Settings > System > System update > Notification settings (or go to the same menu via the standard Settings > Apps > All apps > Show system in the menu > System Updater > Notifications or Settings > Notifications > App notifications).

Actually, they were all enabled in the settings. I just haven't rebooted the phone after the last update installation. Usually, there was a notification, that the phone needs a reboot to apply the update. I could accidentally silence it or something and that got me confused about no updates. Now I am on the latest stable version and will observe further whether the issue occurs.

miczyg1395 avatar Mar 25 '25 20:03 miczyg1395

@thestinger I uninstalled Google Wallet and I'm not getting the error now. Hopefully that helps.

This line led me to that: at tk_trace.pay-PayChimeraService-IPayService_139(Unknown Source:0)

jesse-bonzo avatar Mar 27 '25 18:03 jesse-bonzo

This is the message i get when trying to open Google Wallet, looks consistent with the crash log. Opening the app doesn't trigger a crash. I have registered a Google account on device, but never actually used the app.

Image

qub1750ul avatar Mar 27 '25 22:03 qub1750ul

I've been getting the same crash notification on and off since I installed GrapheneOS a few months ago. Like another poster I generally ignored it since nothing seemed to be broken. If I remember correctly I usually wake up to the error. The only other odd behavior is delayed notifications for Signal. Not sure if it is at all related.

type: crash
osVersion: google/lynx/lynx:15/BP1A.250305.019/2025040700:user/release-keys
flags: dev options enabled
package: com.google.android.gms:250832035, targetSdk 35
process: com.google.android.gms.persistent
processUptime: 107625247 + 353 ms
installer: app.grapheneos.apps
GmsCompatConfig version: 156

java.lang.IllegalStateException: Too many receivers, total of 1000, registered for pid: 2975, callerPackage: com.google.android.gms
	at android.os.Parcel.createExceptionOrNull(Parcel.java:3278)
	at android.os.Parcel.createException(Parcel.java:3254)
	at android.os.Parcel.readException(Parcel.java:3230)
	at android.os.Parcel.readException(Parcel.java:3172)
	at android.app.IActivityManager$Stub$Proxy.registerReceiverWithFeature(IActivityManager.java:6188)
	at android.app.ContextImpl.registerReceiverInternal(ContextImpl.java:2004)
	at android.app.ContextImpl.registerReceiver(ContextImpl.java:1940)
	at android.content.ContextWrapper.registerReceiver(ContextWrapper.java:797)
	at android.content.ContextWrapper.registerReceiver(ContextWrapper.java:797)
	at com.google.android.chimera.ModuleContext.registerReceiver(:com.google.android.gms@[email protected] (260400-731361394):8)
	at ijl.c(:com.google.android.gms@[email protected] (260400-731361394):45)
	at ijl.b(:com.google.android.gms@[email protected] (260400-731361394):7)
	at ezre.g(:com.google.android.gms@[email protected] (260400-731361394):16)
	at ezut.accept(:com.google.android.gms@[email protected] (260400-731361394):243)
	at cbvw.run(:com.google.android.gms@[email protected] (260400-731361394):11)
	at atim.c(:com.google.android.gms@[email protected] (260400-731361394):50)
	at atim.run(:com.google.android.gms@[email protected] (260400-731361394):97)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1156)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:651)
	at atnz.run(:com.google.android.gms@[email protected] (260400-731361394):8)
	at java.lang.Thread.run(Thread.java:1119)
	Suppressed: fglc: 
		at tk_trace.location_base-GoogleLocationManagerChimeraService_onCreate(Unknown Source:0)

IAmDarthMole avatar Apr 10 '25 15:04 IAmDarthMole

The only other odd behavior is delayed notifications for Signal

Is Unrestricted battery mode granted to Play services in the same profile, and did you install Signal after Play services? It won't work properly if installed before it.

thestinger avatar Apr 10 '25 15:04 thestinger

The only other odd behavior is delayed notifications for Signal

Is Unrestricted battery mode granted to Play services in the same profile, and did you install Signal after Play services? It won't work properly if installed before it.

It was on optimized but I changed it to unrestricted.

I believe Signal was installed after. I installed it through the Google Play Store. Should I uninstall it and reinstall it just to be sure?

Thanks!

IAmDarthMole avatar Apr 10 '25 15:04 IAmDarthMole

@IAmDarthMole

It was on optimized but I changed it to unrestricted.

That was definitely the issue. That will cause delays, especially since we changed how sandboxed Google Play services works to avoid always being considered in the foreground to match the stock OS more closely by only making a connection to it from GmsCompat (which runs as a foreground service) when needed.

I believe Signal was installed after. I installed it through the Google Play Store. Should I uninstall it and reinstall it just to be sure?

No need to do anything, Optimized mode was likely the issue.

thestinger avatar Apr 10 '25 15:04 thestinger

GmsCompat message: Google Play Services has crashed. It happened all the time when I activate my phone. I ignored it since nothing seemed to be broken. But latelly my phone freezes and the only way that sometimes worked is to shutdown it completely and then activate the phone two or three times until it starts to work "normally". I have Android 13, MC02.20250704.U0 compilation.

Amadeo47 avatar Dec 09 '25 21:12 Amadeo47