Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When added to a dashboard, Mapbox map charts do not show any data until the user interacts with the map #27635

Closed
3 tasks done
rudokemper opened this issue Mar 25, 2024 · 2 comments

Comments

@rudokemper
Copy link

Bug description

Across a number of Superset instances, I have noticed that the Mapbox map chart type has an issue where when it is added to a dashboard, the data does not load, until the user interacts with the map by panning or zooming. There do not appear to be any errors in in the browser console or server logs about this. Additionally, none of the Mapbox chart settings (such as Live Render) seem to make a difference.

This issue does not occur when loading a Mapbox map chart in the edit chart view (e.g. in the /explore/... route).

How to reproduce the bug

  1. Add a MapBox map chart.
  2. Add some lat/long data
  3. Notice that the map in Chart Creating / Editing view does always show the data.
  4. Add the MapBox chart to a dashboard.
  5. Load the dashboard.
  6. The chart does not show the data (only the background map of choice is shown).
  7. Interact with the map by panning or zooming.
  8. The data now shows.

Screenshots/recordings

Before I interact with the map:
image

After I interact with the map:
image

Superset version

3.0.4

Python version

Not applicable

Node version

Not applicable

Browser

Chrome

Additional context

For the instances where I have seen this issue, they are deployed as an Azure app service using Docker (with the image apache/superset:3.0.3). There are no settings in superset_config.py that should make a difference.

Checklist

  • I have searched Superset docs and Slack and didn't find a solution to my problem.
  • I have searched the GitHub issue tracker and didn't find a similar bug report.
  • I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.
@ignasv
Copy link

ignasv commented Mar 25, 2024

Duplicate to #27562

@rudokemper
Copy link
Author

Thanks @ignasv not sure how I missed your issue (I did search for previous ones)!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants