Overview

For each new Google Maps setup, you need to register a dedicated Google Maps API key. This means that you will need to have it for your PWAs, custom domains, and your white label subdomain.

1. To get an API key (if needed), please check the Getting your own Google Maps License API key KB article.

2. To add it to the CMS platform, please check the Using a Google Maps License API key KB article.

While accessing a feature that uses Google Maps on your PWA, such as the Events Feature, you might get the following error message:

Oops! Something went wrong.
This page didn't load Google Maps correctly. See the JavaScript console for technical details.

sometimes, this message will appear especially if you are setting up locations in the food ordering feature. In this case, Google Maps would instead be blank

The embedded Google Maps component will not load correctly and appear grayed out, as in the following screenshot.

Solution

If you are receiving any errors,

• Refresh the page
• Hit F12 or open the developer tools for your browser - go to the Console tab
• Reproduce the issue

The console tab will show an error in red that should correspond to one of the following issues listed in this Google Maps documentation. This document also contains the necessary actions needed to resolve the issue.

Example console error:

The more common errors are:

• InvalidKeyMapError - Make sure you are using the correct API key. You can generate a new API key in the Cloud Console.
• ExpiredKeyMapError - Wait a few minutes and try again, or you may need to generate a new API key in the Cloud Console.
• BillingNotEnabledMapError / ClientBillingNotEnabledMapError - You have not enabled billing on your project. You must enable Billing on the Google Cloud Project associated to this client ID,
• ApiNotActivatedMapError - The Maps JavaScript API is not activated on your API project. You may need to enable the Maps JavaScript API under APIs in the Google Cloud Console.
  
  

Back to top

Testing

Once you take the steps outlined in the Solution Section, you will no longer get this error, and instead, the map will load correctly on the corresponding features.

Back to top