Infeasible
Status Update
Comments
la...@google.com <la...@google.com> #2
Thanks for posting.
It looks like you did not post any details in your issue. We'll be closing this as we are unable to work on your issue if there are no details provided. Please create another issue providing more details or create a support case[1] if you need more help.
[1]
Description
#IMPORTANT: If your production system or service is down file a Severity 1 support case at console.cloud.google.com/google/maps-apis/support
===========================================================================================
#REMINDER: Please do not disclose any possible PII such as: email address, IP, contact number, any part of name, project numbers and billing accounts as these information may violate security and privacy. Comments or attachments that include PII will be removed and restricted from public viewing.
Furthermore, please refrain from replying to a comment as this will make your email address visible. Instead, you may use the Issue Tracker’s comment feature for your replies.
It is OK to share your API Project ID, but not API keys or client ID credentials.
To learn more about personal data, visithttps://en.wikipedia.org/wiki/Personal_data
===========================================================================================
Please put together a simplified reproduction case, and put it up as a project on your choice of git hosting providers (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
What steps will reproduce the problem?
1. 2. 3.
Also add the following details:
Also attach screenshots, sample code and optionally an APK if possible.
If the problem exhibits itself in a released version of your app on the Play Store, optionally provide a link to the app, and explain how to reproduce the issue in the app.