Get help
If you need help with your app, you can use the following resources:
- Ask a question on Stack Overflow.
- Report a bug or feature request on the issue tracker.
Community support on Stack Overflow
You can use the programming Q&A website Stack Overflow to field technical questions about the Maps URLs. Stack Overflow is a collaboratively edited question-and-answer site for programmers. The site isn't run by Google, but you can sign in using your Google Account. It's a great place to ask technical questions about developing and maintaining your app.
Members of the Google Maps Platform team monitor several
Google Maps-related tags on Stack Overflow. You can find Google Maps
Platform API topics by adding
google-maps
to your search query. You can find Maps URLs-specific topics by adding
google-maps-urls. You can add additional tags to your question
to attract the attention of experts in related technologies.
Search before posting a question on Stack Overflow
Before posting, search Stack Overflow to see if someone has already answered your question.
Consider the following when posting a new question
- Be very clear about your question in the subject—it helps those trying to answer your question as well as those who might search for the same issue.
- Give plenty of details in your post to help others understand your problem. Consider including code snippets, logs, or links to screenshots.
- Include a code snippet that demonstrates the problem. Most people won't debug errors in your code without a sample that reproduces the problem. If you find it difficult to host your code online, use a service like JSFiddle.
- Read the Stack Overflow tour. Follow the site and community guidelines and tips to help ensure that your question is answered.
Report an issue or feature request
If you think you've found a bug, or if you have a feature request that you'd like to share with the Google Maps Platform team, file a bug or feature request in the issue tracker.
Bugs
If you think the cause of a problem is a bug in the Maps URLs, report it on the issue tracker. Include the following information in your bug description:
- A description of the problem and the behavior you expected instead.
- A list of steps or a small snippet of sample code to reproduce the problem.
- Any other information that the bug report template might require.
Before reporting a bug, search the bug list to see if someone has already reported the issue.
Search existing bugs Report a bug
Feature requests
You can use the issue tracker to request new features or suggest modifications to existing features. Describe the specific functionality that you'd like to see added and why you think it's important. If possible, include specific details about your use case and the new opportunities that the feature provides.
Before filing a new feature request, search the list to see if someone has already filed the same request.
Search existing requests Request a new feature
| Issue tracker status codes | |
|---|---|
| New | This issue/feature request has not been triaged. |
| Assigned | The issue is being reviewed. |
| In Progress (Accepted) | The issue has been reviewed and is considered valid. Note that this does not imply that it will be fixed or the feature request implemented in the foreseeable future. See the priority section below for more information. |
| Fixed | The issue is resolved and its availability is imminent. |
| Fixed (Verified) | The issue has been resolved and its availability in a release has been confirmed. |
| Won't fix (Not reproducible) | There is either not enough information to fix the issue, or the issue as reported cannot be re-created. |
| Won't fix (Intended behavior) | The issue describes the expected behavior of the product under the reported circumstances. |
| Won't fix (Obsolete) | The issue is no longer relevant due to changes in the product. |
| Won't fix (Infeasible) | The issue requires changes that cannot be implemented in the foreseeable future. |
| Duplicate | This report duplicates an existing issue. |
Issue priorities
The priority assigned to an issue is the best indicator of when it might be addressed. Higher priority issues (such as P1 and P2) are investigated and resolved more quickly, while lower priority issues (such as P3 and P4) and feature requests may take longer to address or may not be implemented in the foreseeable future. The assigned priority of an issue may change over time based on product priorities, feasibility, and available resources.