Your app is having trouble loading the streamlit_folium.st_folium component.

[thomasdkelly]

Hi great job on this library it has been invaluable for my project.

Lately I have been getting this issue Your app is having trouble loading the streamlit_folium.st_folium component. both on the locally hosted and on streamlit share version. I have been doing lots of updates so not sure which change actually kicked this off. I have seem other people have this error with other components so not sure the cause (https://github.com/PablocFonseca/streamlit-aggrid/issues/7).

If you leave it a minute or so the map will eventually load (and this issue only occurs sometimes). Does anyone have any thoughts?

[dahlalex]

Hi, I have exactly the same issue. I've tryied to use folium_static() instead. It works.

[archydeberker]

Same problem here 😪

Will do some digging and report back if I can figure it out - I wonder if loading the component at a different point in the app lifecycle will help?

[blackary]

If anyone is able to, could someone try opening their Developer Tools in their browser https://balsamiq.com/support/faqs/browserconsole/ and see there are any Javascript errors show in the console when this "your app is having trouble loading..." error is shown?

[tonkolviktor]

for me the following warnings are repeated, but no errors:

Feature Policy: Skipping unsupported feature name “accelerometer”. [5.c6c19a32.chunk.js:2:1403130](http://xxxx:9000/static/js/5.c6c19a32.chunk.js)
Feature Policy: Skipping unsupported feature name “ambient-light-sensor”. [5.c6c19a32.chunk.js:2:1403130](http://xxxx:9000/static/js/5.c6c19a32.chunk.js)
Feature Policy: Skipping unsupported feature name “autoplay”. [5.c6c19a32.chunk.js:2:1403130](http://xxxx:9000/static/js/5.c6c19a32.chunk.js)
Feature Policy: Skipping unsupported feature name “battery”. [5.c6c19a32.chunk.js:2:1403130](http://xxxx:9000/static/js/5.c6c19a32.chunk.js)
Feature Policy: Skipping unsupported feature name “document-domain”. [5.c6c19a32.chunk.js:2:1403130](http://xxxx:9000/static/js/5.c6c19a32.chunk.js)
Feature Policy: Skipping unsupported feature name “encrypted-media”. [5.c6c19a32.chunk.js:2:1403130](http://xxxx:9000/static/js/5.c6c19a32.chunk.js)
Feature Policy: Skipping unsupported feature name “gyroscope”. [5.c6c19a32.chunk.js:2:1403130](http://xxxx:9000/static/js/5.c6c19a32.chunk.js)
Feature Policy: Skipping unsupported feature name “layout-animations”. [5.c6c19a32.chunk.js:2:1403130](http://xxxx:9000/static/js/5.c6c19a32.chunk.js)
Feature Policy: Skipping unsupported feature name “legacy-image-formats”. [5.c6c19a32.chunk.js:2:1403130](http://xxxx:9000/static/js/5.c6c19a32.chunk.js)
Feature Policy: Skipping unsupported feature name “magnetometer”. [5.c6c19a32.chunk.js:2:1403130](http://xxxx:9000/static/js/5.c6c19a32.chunk.js)
Feature Policy: Skipping unsupported feature name “midi”. [5.c6c19a32.chunk.js:2:1403130](http://xxxx:9000/static/js/5.c6c19a32.chunk.js)
Feature Policy: Skipping unsupported feature name “oversized-images”. [5.c6c19a32.chunk.js:2:1403130](http://xxxx:9000/static/js/5.c6c19a32.chunk.js)
Feature Policy: Skipping unsupported feature name “payment”. [5.c6c19a32.chunk.js:2:1403130](http://xxxx:9000/static/js/5.c6c19a32.chunk.js)
Feature Policy: Skipping unsupported feature name “picture-in-picture”. [5.c6c19a32.chunk.js:2:1403130](http://xxxx:9000/static/js/5.c6c19a32.chunk.js)
Feature Policy: Skipping unsupported feature name “publickey-credentials-get”. [5.c6c19a32.chunk.js:2:1403130](http://xxxx:9000/static/js/5.c6c19a32.chunk.js)
Feature Policy: Skipping unsupported feature name “sync-xhr”. [5.c6c19a32.chunk.js:2:1403130](http://xxxx:9000/static/js/5.c6c19a32.chunk.js)
Feature Policy: Skipping unsupported feature name “usb”. [5.c6c19a32.chunk.js:2:1403130](http://xxxx:9000/static/js/5.c6c19a32.chunk.js)
Feature Policy: Skipping unsupported feature name “vr”. [5.c6c19a32.chunk.js:2:1403130](http://xxxx:9000/static/js/5.c6c19a32.chunk.js)
...
An iframe which has both allow-scripts and allow-same-origin for its sandbox attribute can remove its sandboxing. [analysis](http://xxxx:9000/analysis)
This page uses the non standard property “zoom”. Consider using calc() in the relevant property values, or using “transform” along with “transform-origin: 0 0”. [index.html](http://xxxx:9000/component/streamlit_folium.st_folium/index.html?streamlitUrl=http%3A%2F%2Fxxxx%3A9000%2Ftour_analysis)
This page uses the non standard property “zoom”. Consider using calc() in the relevant property values, or using “transform” along with “transform-origin: 0 0”. [index.html](http://xxxx:9000/component/streamlit_folium.st_folium/index.html?streamlitUrl=http%3A%2F%2Fxxxx%3A9000%2Ftour_analysis)
Layout was forced before the page was fully loaded. If stylesheets are not yet loaded this may cause a flash of unstyled content. [jquery.min.js:6:16507](https://cdnjs.cloudflare.com/ajax/libs/jquery/2.0.0/jquery.min.js)
Deprecated include of L.Mixin.Events: this property will be removed in future releases, please inherit from L.Evented instead. S.extend/<@https://cdn.jsdelivr.net/npm/[email protected]/dist/leaflet.js:5:3170
S.extend@https://cdn.jsdelivr.net/npm/[email protected]/dist/leaflet.js:5:3188
@https://teastman.github.io/Leaflet.pattern/leaflet.pattern.js:6:34
@https://teastman.github.io/Leaflet.pattern/leaflet.pattern.js:6:7077
[Class.js:121:11](https://cdn.jsdelivr.net/npm/[email protected]/src/core/Class.js)
Will-change memory consumption is too high. Budget limit is the document surface area multiplied by 3 (14080 px). Occurrences of will-change over the budget will be ignored.

[hozn]

I was also seeing this same issue repeatedly with deployed code (but not when running locally, even locally from the same docker container that I deployed to server), but then when I pulled up the developer tools and refreshed it went away ..... (and closing developer tools and refreshing it is still working), so seems to be ephemeral / something-more-complex.

[thomassajot]

I am experiencing the same issue

Streamlit v1.13.0 streamlit_folium=0.11.0

[mcarlosfr]

First I'd like to thank you @randyzwitch for you component I like it very much and love using it.

I'm having the same problem and could find the seed of the problem in my case: When loading st_folium the page tries to open a leaflet component called terminator and it seems that sometimes the server where it is located takes more than 30 secs to answer and then the download is very fast, then the map appears. I didn't have time to try and find a way to solve it but I'll try next week