> For the complete documentation index, see [llms.txt](https://docs.sharinpix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sharinpix.com/faqs/i-got-a-google-map-error-what-should-i-do.md).

# I got a Google Map error, what should I do?

![](https://751044238-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi8tH1o5AHthxksYgF6ij%2Fuploads%2FDRfPfenxRyyJrcwogj0Z%2Fimage%20\(2\).png?alt=media\&token=39661705-7267-4cd6-bcc4-806bca22215d)

If you ever encounter the above pop-up error message and/or the text '**For development purposes only**' displayed on your SharinPix Map, you should check the Google Developer Tools' console for more details about the error. Solutions to such issues are usually available from the console as well.

To access the console:

1. either use to command **Ctrl + Shift + I** to activate it or right-click and select **Inspect**
2. then, click on the **Console** tab as depicted below:

![](https://751044238-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi8tH1o5AHthxksYgF6ij%2Fuploads%2F4TkJ5rAiIf6MDF0ZETW2%2Fimage%20\(3\).png?alt=media\&token=02f45ff7-7670-452b-98d0-cc429d93c81d)

The error message shall be highlighted in red on the console tab.

Additionally, details on how to address the issue will generally appear on the console.

One common error is as follows: **“You must enable Billing on the Google Cloud Project"**

This is because Billing has not been enabled on the Google Cloud Project.

To solve this, enable Billing at [**https://console.cloud.google.com/project/\_/billing/enable**](https://console.cloud.google.com/project/_/billing/enable)

You can learn more at [**https://developers.google.com/maps/gmp-get-started**](https://developers.google.com/maps/gmp-get-started)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sharinpix.com/faqs/i-got-a-google-map-error-what-should-i-do.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.