[com.google.android.apps.maps] Blank screen and crash
Affected app Name: Google maps Package id: com.google.android.apps.maps
Describe the bug Google maps doesn't display the map and crashes shortly after opening.
To Reproduce Steps to reproduce the behavior:
- Open google maps
- You will see a blank area in place of the map
- Wait a few seconds
- The app crashes
Expected behavior Google maps should display the map normally and not crash.
Screenshots If applicable, add screenshots to help explain your problem.
System Android Version: 14 Custom ROM: CrDroid 10.13 (GSI)
microG microG Core version: v0.3.9.250932 microG Self-Check results: All checked.
Additional context Logcat:
FATAL EXCEPTION: firebase-installations-executor-2
Process: com.google.android.apps.maps, PID: 809
java.lang.RuntimeException: Unable to find a default SSL provider.
at brfs.a(PG:45)
at brfs.createSocket(PG:6)
at com.android.okhttp.internal.io.RealConnection.connectTls(RealConnection.java:185)
at com.android.okhttp.internal.io.RealConnection.connectSocket(RealConnection.java:153)
at com.android.okhttp.internal.io.RealConnection.connect(RealConnection.java:116)
at com.android.okhttp.internal.http.StreamAllocation.findConnection(StreamAllocation.java:186)
at com.android.okhttp.internal.http.StreamAllocation.findHealthyConnection(StreamAllocation.java:128)
at com.android.okhttp.internal.http.StreamAllocation.newStream(StreamAllocation.java:97)
at com.android.okhttp.internal.http.HttpEngine.connect(HttpEngine.java:289)
at com.android.okhttp.internal.http.HttpEngine.sendRequest(HttpEngine.java:232)
at com.android.okhttp.internal.huc.HttpURLConnectionImpl.execute(HttpURLConnectionImpl.java:465)
at com.android.okhttp.internal.huc.HttpURLConnectionImpl.connect(HttpURLConnectionImpl.java:131)
at com.android.okhttp.internal.huc.HttpURLConnectionImpl.getOutputStream(HttpURLConnectionImpl.java:262)
at com.android.okhttp.internal.huc.DelegatingHttpsURLConnection.getOutputStream(DelegatingHttpsURLConnection.java:219)
at com.android.okhttp.internal.huc.HttpsURLConnectionImpl.getOutputStream(HttpsURLConnectionImpl.java:30)
at bwlc.g(PG:1)
at bwlc.b(PG:97)
at bwko.$r8$lambda$l9y44Uyk0Jk-iH_L8pNYEtJjJtU(PG:213)
at almk.run(PG:45)
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:1012)
Your ROM is too old.
Either update it to something more modern (e.g., crDroid 11.x) or you will need to root it and install a special Xposed module to fix its lack of proper app signature checking protocol to support microG.
Google changed that in November 2024.
Or you can install an old version of Google maps from prior to 2024-11.
This applies to all Google apps now.
Your ROM is too old.
Either update it to something more modern (e.g., crDroid 11.x) or you will need to root it and install a special Xposed module to fix its lack of proper app signature checking protocol to support microG.
Google changed that in November 2024.
Or you can install an old version of Google maps from prior to 2024-11.
This applies to all Google apps now.
All google apps work perfectly fine, and I can log into my account. MicroG self check shows everything is ticked. The issue is only with Maps. How did you come to this conclusion? Did you check the logcat? For your information, I also got the exact same issue while on the stock ROM (HiOS 14) where I had FakeGApps v6.6 Xposed module.
I have found the same error here: https://github.com/KHikami/ProjectFiCallingDeciphered/blob/master/TalkJADXDecompile/com/google/android/libraries/stitch/sslguard/SslGuardSocketFactory.java#L136
It is another app by Google, maybe the code is the same.
I found that it only happens when microG is installed as a system app. Google maps works fine when microG is installed as user app. The "permission to interact across work profiles" is not ticked (as expected), but I don't need it, so for now I will keep it installed as user app. I also tried my own microG installer which doesn't need signature spoofing support in the rom, but as it installs microG into system, the issue is still there. The problem is definitely not related to signature spoofing.