Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Google Maps crashes when Play service apps are installed in another profile but not in current one #685

Closed
justinhsa opened this issue Oct 10, 2021 · 7 comments
Labels
bug Something isn't working

Comments

@justinhsa
Copy link

justinhsa commented Oct 10, 2021

Device: Pixel 5 (redfin)
OS version: RQ3A.211001.001.2021100606

Hello, just noticed this. I have one secondary profile with play service apps installed. If I install google maps in another secondary profile without play service apps, it will crash on start. Haven't tested on owner profile yet. Below is part of the logs that I think related:

FATAL EXCEPTION: DefaultPool5
Process: com.google.android.apps.maps, PID: 15591
java.lang.SecurityException: Failed to find provider com.google.android.gsf.gservices for user 12; expected to find a valid ContentProvider for this authority
at android.os.Parcel.createExceptionOrNull(Parcel.java:2373)
at android.os.Parcel.createException(Parcel.java:2357)
at android.os.Parcel.readException(Parcel.java:2340)
at android.os.Parcel.readException(Parcel.java:2282)
at android.content.IContentService$Stub$Proxy.registerContentObserver(IContentService.java:1229)
at android.content.ContentResolver.registerContentObserver(ContentResolver.java:2627)
at android.content.ContentResolver.registerContentObserver(ContentResolver.java:2615)
at cytj.<init>(PG:2)
at cytj.a(PG:2)
at cyue.j(PG:2)
at cyue.d(PG:10)
at czdw.d(PG:1)
at com.google.android.libraries.social.peoplekit.avatars.viewcontrollers.glide.FifeGlideModule.c(PG:2)
at ddn.g(PG:42)
at ddn.b(PG:3)
at ddn.d(PG:2)
at ddn.c(PG:1)
at crqt.a(PG:2)
at ddbw.a(PG:1)
at crqp.run(PG:6)
at bwkl.run(PG:2)
at bwlv.run(PG:2)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at bwlm.run(PG:4)
at java.lang.Thread.run(Thread.java:923)
Caused by: android.os.RemoteException: Remote stack trace:
at com.android.server.content.ContentService.registerContentObserver(ContentService.java:355)
at android.content.IContentService$Stub.onTransact(IContentService.java:482)
at android.os.Binder.execTransactInternal(Binder.java:1154)
at android.os.Binder.execTransact(Binder.java:1123)

@thestinger
Copy link
Member

Are you talking about a secondary user or a work profile?

@thestinger thestinger added the bug Something isn't working label Oct 10, 2021
@justinhsa
Copy link
Author

Secondary user, not work profile.

@thestinger
Copy link
Member

Should be resolved in Android 12. You may have to remove and reinstall Play services in secondary profiles due to the upstream profile fixes though.

@justinhsa
Copy link
Author

justinhsa commented Oct 23, 2021

Tested this again in SP1A.210812.015.2021102203. I removed play services apps in all secondary profiles, restarted the phone, installed play services apps in one secondary profile, ended this profile, went to another secondary profile and installed gmaps, and gmaps still crashed upon starting. Relevant error logs are here. From what I can see, the error logs are similar as before, so I don't think the issue has been resolved yet.

@thestinger thestinger reopened this Oct 23, 2021
@codethief
Copy link

codethief commented Jan 24, 2022

Similar (but slightly different) observation: When I install Signal in my personal profile (while having Play Services installed only in my work profile), Signal will still think Play Services are available and attempt to use them for notifications instead of resorting to web socket notifications – which will obviously fail. Interestingly, I could fix that by running

adb shell pm disable-user --user 0 com.google.android.gms

Details and discussion: signalapp/Signal-Android#9279 (comment)

@ghost
Copy link

ghost commented Feb 2, 2022

I can't reproduce this on the latest release. Can you please try the latest version (2022013120) and see if it still happens?

@thestinger thestinger reopened this Feb 2, 2022
@thestinger
Copy link
Member

This shouldn't be an issue anymore across user profiles. The issue should be fixed upstream now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants