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
1.-4. is an inappropriate way of generating a snapshot. It is better to use a lite mode map instead, because this implements exactly what is needed (non-interactive snapshot of a map).
An instance in which the current implementation is inappropriate is when onMapLoaded and onSnapshotReady have not yet been called, but the activity hosting the map is destroyed. In this case, the activity's onDestroy method must call the map's onDestroy method (which is not implemented). Lite mode maps do not expect lifecycle methods to be called, except for onCreate.
5. is in violation of the contract of the snapshot API, and by extension likely also of the terms of usage of the Google Maps API.
Note: Images of the map must not be transmitted to your servers, or otherwise used outside of the application. If you need to send a map to another application or user, send data that allows them to reconstruct the map for the new user instead of a snapshot.
The Signal app currently uses the following method of sharing a user's location, after the user has selected a location on the in-app map.
This is implemented in the following snippet:
Signal-Android/app/src/main/java/org/thoughtcrime/securesms/components/location/SignalMapView.java
Lines 77 to 99 in 6eaebd1
The two issues are:
onMapLoaded
andonSnapshotReady
have not yet been called, but the activity hosting the map is destroyed. In this case, the activity'sonDestroy
method must call the map'sonDestroy
method (which is not implemented). Lite mode maps do not expect lifecycle methods to be called, except foronCreate
.mapView
#13008.GoogleMap.OnMapLoadedCallback
correctly (ImplementGoogleMap.OnMapLoadedCallback
correctly microg/GmsCore#1960).snapshot
API, and by extension likely also of the terms of usage of the Google Maps API.Previous: #13006
The text was updated successfully, but these errors were encountered: