Services Plugins FAQs

Advice for Geofence #MapLocationTriggerLive plugin

Plugins
#1

Good evening, I’m using the plugin listed above and in safari on iOS I keep seeing this message in my logs:

-“Google Maps JavaScript API has been loaded directly without loading=async. This can result in suboptimal performance.”

Immediately after my next log is “Web content process died, no memory warning”. This causes my page to crash.

I’ve done A/B testing on my page with and without the plugin and the page does work without the geofence element. I’m curious if there’s a workaround I can use so that the plugin is still able to be used?

Thanks
Jordan

#2

Hi @jordan.robertson,

Thank you for reaching out to us.

The console warning regarding loading=async for the Google Maps JavaScript API is a common notice related to performance optimization from Google, but the critical issue here is the browser crash caused by Web content process died, no memory warning in Safari on iOS.

This crash typically occurs when Safari on iOS runs out of allocated memory for the web view session. Here are a few key points and steps to help address and troubleshoot this issue:

1. Check API Key and Script Conflicts

  • Verify if Google Maps scripts are being loaded multiple times on your page. If you have standard Bubble map elements, other map/location plugins, or direct Google Maps scripts injected in the page header alongside the Geofence element, they might conflict or load redundant scripts into memory.
  • Ensure your Google Maps API key is correctly configured in your Bubble app settings under Settings → General → General appearance / API Keys if applicable.

2. Optimize Geofence Watch Frequency and Logic

  • Excessive background updates or rapid coordinate tracking events on iOS Safari can cause heavy memory usage.
  • Review your workflow logic and conditions attached to the plugin’s events to ensure you are not running continuous heavy workflows or creating infinite loops when location changes occur.
  • Reduce the frequency or number of active geofence points/polygons if you are watching a large list simultaneously.

3. Test on a Clean Page

  • Create a simple test page with only the Geofence element and test it on Safari iOS. This will help isolate whether the issue is purely specific to the Geofence element or caused by a combination of multiple elements and scripts on your main page.

For detailed setup guidelines and best practices, please refer to our official documentation: Geofence #MapLocationTriggerLive Documentation

If the issue persists on a clean test page, please share additional details regarding your setup (such as whether you are watching single points, lists of polygons, or running specific workflows on location updates) so we can assist you further.

Best regards,
Support Team
Browse all Zeroqode Plugins for bubble
Banner_Last3

#3

Thank you Constantin, I’ll check this out.

#4

Hi @jordan.robertson

Following up to check if you had a chance to test the suggestions shared in our previous message.

Please let us know if you were able to resolve the issue or if you still need assistance with the Geofence #MapLocationTriggerLive plugin.

Best regards,
Support Team
Browse all Zeroqode Plugins for bubble
Banner_Last3