Assigned
Status Update
Comments
br...@google.com <br...@google.com> #2
Thank you for posting.
We are currently looking into this and will get back to you as soon as we have an update.
br...@google.com <br...@google.com> #3
Thank you for your patience.
In order for us to further handle the issue. May we request you to please share the following details:
- Steps to reproduce (Does this happen during initialization?)
- Reproducibility in sample/test/demo apps? (Yes/No)
- Issue frequency (e.g., 100%, 10%, For crashes x of y launches)
Thank you for your understanding.
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 Navigation SDK Sample Applications Repository and modify the sample applications:https://github.com/googlemaps-samples/android-navigation-samples
What steps will reproduce the problem?
Also add the following details:
Also attach screenshots, sample code and optionally an APK if possible.
This is on NavSDK 6.0.1
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.