Thanks for that, I see what’s going on now. Just to give you an understanding as to what’s happening…
So one thing we can’t change here, is Bubble’s behaviour or to be more precise, when it decides to try and load the maps API. As soon as you click that button, Bubble attempts to loads the Maps API (it doesn’t do it on page load for performance reasons), it then runs the calculation to return the coordinates at the address through the action. But… because my plugin has essentially already loaded the maps API, that’s why the error then appears at the time you click the button - and this applies to any Google Maps plugin you’ll find in the plugin store.
I’ve added some substantial amount of checking code into this plugin for which the first part you already see through the console logs, where it states:
google maps api script is being loaded by the plugin with additional places, drawing and geometry libraries included
Now, if you were to put an address box onto your page and set the choices to geographical places, then when the page loads, Bubble see’s this and it will load the maps API before anything else. When that happens, the plugin will do it’s detection thing and you’ll see the console log message change to:
google maps api script already loaded by bubble, drawing and geometry libraries will be added with the correct language
When you click the button now, it will use the maps API script which Bubble loaded and the error goes away. Anything else related to using current user’s location or other geographical data types will all work in the normal way and hopefully now the plugin will now detect all this and function as normal.
I’ve just added the search box onto your page and at the moment there are no conditions being applied anywhere. I would set the map to be not visible and only make it visible when that search box is visible. That will ensure the 2 load in the right sequence. In your case, you don’t want the map to load before that search box. Set the search box to be width/height of 1px and send it to the back to its sitting behind all elements, you can mark it disabled also which won’t affect Bubble loading the maps API.