[New] (Google Maps SDK is crashing) – ArrayIndexOutOfBoundsException in Android Google Maps SDK
The Google Maps SDK is currently crash with the following stack trace: Fatal Exception: java.lang.ArrayIndexOutOfBoundsException: length=1; index=12 at com.google.maps.api.android.lib6.gmm6.vector.ct.<init>(:com.google.android.gms.dynamite_mapsdynamite@201216065@20.12.16 (100400-0):9) at com.google.maps.api.android.lib6.gmm6.vector.cv.a(:com.google.android.gms.dynamite_mapsdynamite@201216065@20.12.16 (100400-0):23) at com.google.maps.api.android.lib6.gmm6.util.m.run(:com.google.android.gms.dynamite_mapsdynamite@201216065@20.12.16 (100400-0):14) at java.lang.Thread.run(Thread.java:764) What steps will reproduce the problem? 1. Appears to be related to the size of the map view. Small map views render fine, however opening a large map view freezes then crashes the app. Issue started appearing at ~11:30AM PST April 23rd, 2020.
Android Version :- Android 6, 7, 8, 9 and 10 and all are affected.
If you have any other issue then mention it in google discussion here
if you are seeing following error then you are definitely affected by google maps service down due to some technical issue here you can track progress by google: Click Here
Issue list :-
- array index out of bound
- google maps carhases
- google maps carhases
- google maps not working
- google maps not working iphone
- google maps server not available
- google maps not working on pc
- google maps not working on website
- google maps not working on chrome, safari, mozila firefox
- google maps not working on mobile application
- goole maps sdk error
- google map location stop
- map api wont working
- FATAL EXCEPTION: androidmapsapi-ZoomTableManager
Answer by google
Our engineering team continues to investigate the issue.
We will provide an update by Thursday, 2020-04-23 14:30 US/Pacific with current details.
Diagnosis: If you see a stack dump starting with the lines: java.lang.ArrayIndexOutOfBoundsException: length=1; index=12 at com.google.maps.api.android.lib6.gmm6.vector.ct.<init> … you are affected by this error.
Workaround: None at this time
For More Info Check Here :- Click Here