App URL: https://adrian-s-op-dashboard.streamlit.app/
Since: 2026-11-03 (UTC)
Symptoms:
- On first load the page shows only the blank loading spinner for 1+ minute.
- When the app finally renders, several widgets show
"TypeError: Failed to fetch dynamically imported module:
Streamlit"
- DevTools Network tab: every file under /~/+/static/js/ returns 200 except
resolveDefaultExport.DJbX7TqQ.js, which hangs for ~49 s and then returns HTTP 500.
Page “Finish” time is 3.3 minutes.
What I’ve ruled out:
- Same behavior from a home PC, from a phone on mobile data, and from a second,
much lighter app in the same account — so not my network or browser.
- Same behavior on streamlit 1.52.0 and 1.59.0 (Python 3.12.16 on Cloud).
- Manage app logs show a clean deploy and no Python errors; the script runs fine.
- Rebooted the app from Manage app; no change.
- The app runs normally outside Cloud (local streamlit run).
This looks like the same issue reported in October ("Apps stuck on loading spinner —
/~/+/ returns HTTP 500"). Could someone on the Cloud team take a look?
Thanks for the detailed report and screenshots. The key signal is that resolveDefaultExport.DJbX7TqQ.js returns HTTP 500 after ~49 seconds; the DataFrame bundle itself returns 200. That points to a failed Cloud-served frontend asset request, not a Python exception shown in your app logs. The /api/v2/user/details 404s are visible too, but the provided information doesn’t establish whether they’re related. The remote-deployment guide covers loading and WebSocket configuration problems, but doesn’t document this specific asset 500, so there isn’t a confirmed app-side fix to recommend. (Deployment issues, remote-loading troubleshooting)
This looks appropriate to escalate through Streamlit support; include the app URL, UTC timestamps, both affected app versions, and a Network-panel HAR or the failed request details. The Community Cloud docs point users to support and forums for deployment issues. (Streamlit Community Cloud) If you post a minimal reproducible app or relevant code, community members may also help rule out an app-specific trigger.
Sources: