Maps diagnostics
Runs a live probe of the browser key and server-side APIs so you can see why Maps failed.
Browser
Server (via connector gateway)
Map load timeline
Per-API breakdown
Which map service failed
All four map services answered normally.
Maps JavaScript API
server keyDrawing the map and markers in the app
Checking…
Geocoding API
server keyTurning vendor addresses into map pins
Checking…
Places API (New)
server keyPlace search and address autocomplete
Checking…
Routes API
server keyTravel time between activities
Checking…
Google Cloud walkthrough
Set up your own key — step by step
Eight steps in Google Cloud Console for trippbooking.com. Tick them off as you go — 0 of 8 done.
1. Open (or create) a Google Cloud project
Google Cloud projectsA project is just the workspace your map key lives in. If you already have one, pick it from the dropdown at the top of the console.
2. Turn on billing for that project
Billing settingsGoogle requires a card on file for Maps even on the free tier. Normal traffic for a site this size usually stays inside the monthly free allowance.
3. Enable the four APIs TRIPP uses
Open each one and press the blue “Enable” button.
- Enable Maps JavaScript APIDraws the trip map and activity markers.
- Enable Places API (New)Powers address search and vendor lookups.
- Enable Geocoding APITurns addresses into map pins.
- Enable Routes APICalculates driving, walking and transit times.
4. Create an API key
Credentials pageOn the Credentials page choose Create credentials → API key. Copy the key somewhere safe for a moment — you'll paste it into TRIPP at the last step.
5. Add both trippbooking.com referrer patterns to the key
Key restrictionsClick the new key, then under Application restrictions choose Websites and add these two lines. Both are required — the first covers the bare domain, the second covers
wwwand any other subdomain.https://trippbooking.com/* https://*.trippbooking.com/*
6. Limit the key to those same four APIs
Still on the key's page, under API restrictions pick Restrict key and select Maps JavaScript, Places (New), Geocoding and Routes. Then press Save. This keeps the key useless to anyone who copies it for something else.
7. Hand the key to TRIPP
Paste the key into the TRIPP chat and say you want to use your own Google Maps key. It goes straight into secure storage — never into the app's code or your browser — and your live site switches off the shared Lovable key.
8. Re-run the checks
Come back here and press Re-run checklist. The domain and pattern checks below should turn green, and maps will load on trippbooking.com.
Domain setup checklist
Domain setup checklist
Checked for this site — 0/5 done.
1. Map key connected to this site
Checking…
Not checked yet2. Maps JavaScript API works on this domain
Loading the map library from this site to see if Google accepts it…
Not checked yet3. Geocoding API enabled
Checking…
Not checked yet4. Places API (New) enabled
Checking…
Not checked yet5. Routes API enabled
Checking…
Not checked yet
Send to support
Support packet
One block with your domain, which key is in use, and Google's latest raw error messages — ready to paste into a support chat. No secret keys are included.
Places cache
Autocomplete is in-memory (cleared per session). Place details persist in localStorage for 24h per Google's caching policy.
How long cached place details stay fresh before refetching. Longer = fewer API calls; shorter = quicker to pick up address changes. Google allows up to 30 days.
When to swap the Places session token. Rotating after each selection matches Google's billing model. Rotating on idle can reduce billed sessions when users make several picks in a row.
Settings persist per browser. They take effect on the next keystroke or pick.
Common fixes
- Enable Maps JavaScript API, Places API (New), Geocoding API, and Routes API on the key.
- Enable billing on the Google Cloud project.
- For the browser key: add
https://trippbooking.com/*andhttps://*.trippbooking.com/*to HTTP referrer restrictions. - For the server key: set Application restrictions to "None" — gateway calls send no referrer.