Status Update
No update yet.
Comments
de...@atommobility.com
iv...@google.com
Thanks for the post.
To look into this further, can you please provide the reason as to why your app needs to be opened for many days?
With regards to java.lang.SecurityException: GoogleCertificatesRslt error, there's an ongoing issue for that in this
"this is just a harmless, yet annoying warning message. It does not cause or show any problems on Maps SDK functionality.
We have an internal issue filed to remove the java.io.FileNotFoundException and java.lang.SecurityException warning messages from Android log. Currently we don't have a target release date for this."
So please do follow the aforementioned issue if you want to get updates regarding the SecurityException error.
de...@atommobility.com
To look into this further, can you please provide the reason as to why your app needs to be opened for many days?
I install and open the app. All is good. Then I close (kill) the app. After, lets say, 30 days, I open app again, now map wont load. In logs Stale snapshot error is shown.
If I open app regularly, lets say at least once in 7 days, all is good.
iv...@google.com
Can you please provide more information as to how you were testing your app for 30 days? And what's your use case as to why you need to leave your app open for longer times? Are you also leaving your app open on the foreground or the background? Thanks!
de...@atommobility.com
I dont leave app open for 30 days.
I install and open/launch the app. All is good. Then I close (kill) the app. After, lets say, 30 days, I open/launch app again, now map wont load.
iv...@google.com
Apologies for misunderstanding your issue.
After further checking, the security exception error is indeed a duplicate of
-
Put together a simplified reproduction case (
http://sscce.org/ ) and add it to a git hosting provider (e.g. github, bitbucket, etc)? The easiest way to do this might be to fork the Google Maps Android API Samples Repository and modify one of the existing demo activities:https://github.com/googlemaps/android-samples -
List steps to reproduce the problem
-
Add the following details:
- Device (and version of Android) you have verified this issue on:
- Google Play Services client library version:
- Google Play Services version on the device:
- Android SDK Version:
- Was this working correctly on a previous version of Google Play Services? (If yes, which client library and SDK version?)
- Attach the following:
- screenshots
- sample code
- an APK if possible.
- If the problem exhibits itself in a released version of your app on the Play Store, optionally link us to the app, and explain how to reproduce the issue in your app.
de...@atommobility.com
iv...@google.com
Thanks for the updates.
We are checking this issue internally.
de...@atommobility.com
Did you manged to reproduce the issue?
de...@atommobility.com
is...@google.com
de...@atommobility.com
Issue still persists with mapsPlayServices = "18.2.0". Map won't load on subsequent app opens after some time. On Huawei phone this issue appears almost every day.
<androidx.fragment.app.FragmentContainerView
android:id="@+id/supportMapFragmentContainer"
android:name="com.google.android.gms.maps.SupportMapFragment"
android:layout_width="match_parent"
android:layout_height="match_parent" />
Description
My app has map view in the main screen, it loads, all is fine. Problem is when app is opened after many days (~30 days). Then map tiles are blank. I can see the polygons on the map, but not the tiles. If you close the app and open again, then tiles loads.
Google Play services client version: 12451000
Google Play services package version: 231312044
Google Play services maps renderer version(maps_core): 224910104
When I had blank tiles, I put app in background, after few minutes I returned to foreground. App when trough restore state, I still could see blank tiles, but after few seconds they loaded. I got similar logs as in