Hi @siticum,
Thank you for the detailed explanation and for adding us as a collaborator - that was very helpful.
From what we can see so far, the tracking itself appears to be working correctly in your setup. The browser requests and accepts the location permission, the map centers correctly when tracking starts, and Bubble is able to pull the current location. This indicates that the Start Track Location action is functioning as expected and the geolocation watch is active.
The part that seems unusual is that no visual tracking marker appears on the map, even though tracking is active. After reviewing the setup screenshots, the most likely cause appears to be related to the custom marker configuration and additional CSS customization applied to the map.
Specifically, we noticed that “Use custom markers” is enabled and the marker icon source is set to the image_marker field. Your database markers use this field correctly, but the tracking marker is not created from the same data structure as regular markers, so it may not have access to that field. Because of this, the plugin may be trying to render the tracking marker using the same custom marker logic and ending up with no visible icon.
In addition, there is a custom HTML/CSS block on the page that modifies Google Maps UI elements. While the CSS appears to target camera controls and the compass rather than markers directly, it still affects the Google Maps DOM structure, which can sometimes interfere with map overlays or plugin-rendered elements.
To help narrow this down, could you please try the following quick tests?
-
Disable custom markers temporarily
In the map element, uncheck “Use custom markers” and test the tracking again. This will help confirm whether the custom marker configuration is preventing the tracking marker from rendering.
-
Temporarily remove the HTML CSS block
Disable the HTML element that injects the custom CSS and test the tracking again to see if the marker becomes visible.
-
Test with minimal map configuration
If possible, try a quick test page with the same plugin element and API key but without:
- custom markers
- custom CSS
- additional conditional stylingThen run Start Track Location again and see whether the marker appears.
These tests will help determine whether the issue is related to custom rendering rules rather than the tracking action itself.
Could you please let us know the results after trying the steps above? That should help us identify exactly where the marker rendering is being affected.
Thanks again for the detailed report and for giving us access to the app - we really appreciate it.
Best regards,
Support Team
Browse all Zeroqode Plugins for bubble
