You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
We are seeing a big spike in crashes which started around December 22, 2024:
java.lang.NullPointerException
at org.microg.gms.maps.hms.GoogleMapImpl.refreshContainerLayer(GoogleMap.kt:802)
at org.microg.gms.maps.hms.GoogleMapImpl.controlLayerRun$lambda$0(GoogleMap.kt:88)
at org.microg.gms.maps.hms.GoogleMapImpl.$r8$lambda$pYOiElsK2rOoMV9WyKMIWQBHR4E(Unknown)
at org.microg.gms.maps.hms.GoogleMapImpl$$ExternalSyntheticLambda9.run(Unknown:2)
at android.os.Handler.handleCallback(Handler.java:966)
at android.os.Handler.dispatchMessage(Handler.java:110)
at android.os.Looper.loopOnce(Looper.java:205)
at android.os.Looper.loop(Looper.java:293)
at android.app.ActivityThread.loopProcess(ActivityThread.java:9998)
at android.app.ActivityThread.main(ActivityThread.java:9987)
at java.lang.reflect.Method.invoke(Method.java:-2)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:586)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1240)
Guess I'm running into this problem - some of the apps requiring location services stop working, claiming that the device does not have GMS support, for example Ampere.
The time (Dec 22) looks very close to the fact that the HarmonyOS 4.3.0.130 (which reports to be 12) was first released on Dec 17 for Mate 70 series, and it takes a few days to get a meanful number of updates. It was since that exact version my apps stopped working, and I can confirm the previous version 4.3.0.126SP3 works without problem.
Describe the bug
We are seeing a big spike in crashes which started around December 22, 2024:
@DaVinci9196 This is likely related to #2608 and it has been also mentioned in the comment to that PR: #2608 (comment).
System
Android Version: ~97% events on Android 12 and the rest on Android 10.
The text was updated successfully, but these errors were encountered: