Fixed
Status Update
Comments
an...@google.com <an...@google.com> #2
We need a simplified reproduction example in order to investigate it.
an...@google.com <an...@google.com> #4
Thanks for reporting this issue. We verified it and we'll keep tracking it. Please note that at this point we cannot give you any information on if and when this will be investigated. You can star this task to receive further updates.
vi...@google.com <vi...@google.com> #5
A fix for this issue was included in Google Maps Android API version 2.28, part of Google Play Services version 11, which should now have been rolled out to all supported Android devices.
Users of the M4B static library should download the latest version [1] and rebuild their application. Developers who have added the library source to Android SDK Manager [2] should get an automatic update prompt in Android Studio.
[1]https://developers.google.com/maps/premium/android-get-started#option_1_download_the_sdk_as_a_static_library
[2]https://developers.google.com/maps/premium/android-get-started#option_2_download_the_sdk_using_the_android_sdk_manager
Users of the M4B static library should download the latest version [1] and rebuild their application. Developers who have added the library source to Android SDK Manager [2] should get an automatic update prompt in Android Studio.
[1]
[2]
co...@googlemail.com <co...@googlemail.com> #6
Not fixed in latest version!
Issue are still available in:
Google Maps Android API: Google Play services client version: 11020000
Google Maps Android API: Google Play services package version: 11302446
Issue are still available in:
Google Maps Android API: Google Play services client version: 11020000
Google Maps Android API: Google Play services package version: 11302446
vi...@google.com <vi...@google.com>
vi...@google.com <vi...@google.com> #7
Apologies, the fix was not yet included in Google Play Services v11.
Description
03-30 15:15:28.853 E/AndroidRuntime: FATAL EXCEPTION: GLThread 1734
Process: ru.mytransporter.transporter, PID: 15834
java.lang.IllegalArgumentException: totalAngleRad must be >= 0.0f and <= 2*PI: -2.9516223E-4
at com.google.maps.api.android.lib6.common.k.b(:com.google.android.gms.DynamiteModulesB:162)
at com.google.maps.api.android.lib6.gmm6.vector.gl.a.a(:com.google.android.gms.DynamiteModulesB:409)
at com.google.maps.api.android.lib6.gmm6.vector.gl.x.a(:com.google.android.gms.DynamiteModulesB:1160)
at com.google.maps.api.android.lib6.gmm6.vector.gl.m.a(:com.google.android.gms.DynamiteModulesB:14745)
at com.google.maps.api.android.lib6.gmm6.vector.gl.m.a(:com.google.android.gms.DynamiteModulesB:1387)
at com.google.maps.api.android.lib6.gmm6.vector.t.a(:com.google.android.gms.DynamiteModulesB:691)
at com.google.maps.api.android.lib6.gmm6.vector.t.a(:com.google.android.gms.DynamiteModulesB:2411)
at com.google.maps.api.android.lib6.gmm6.api.u.a(:com.google.android.gms.DynamiteModulesB:373)
at com.google.maps.api.android.lib6.gmm6.api.r.a(:com.google.android.gms.DynamiteModulesB:237)
at com.google.maps.api.android.lib6.gmm6.vector.cc.a(:com.google.android.gms.DynamiteModulesB:1278)
at com.google.maps.api.android.lib6.gmm6.vector.cc.b(:com.google.android.gms.DynamiteModulesB:21113)
at com.google.maps.api.android.lib6.gmm6.vector.bj.f(:com.google.android.gms.DynamiteModulesB:1162)
at com.google.maps.api.android.lib6.gmm6.vector.bj.run(:com.google.android.gms.DynamiteModulesB:881)
Changing jointType was last thing I checked and I was surprised that it worked.
Android Emulator 26.0.0, SDK version 24
Google Maps 9.30.1
Google Play Services 10.2.98
My app compile SDK is 25 and I use gms libraries 10.2.0
Sorry, but I can't provide the code.