App stuck after "Processed dependencies!" — never starts (no error, no Uvicorn log)

Community Cloud
,
1

My app stulio-finance-pro.streamlit.app (repo tulicesar/stulio-finance-pro, branch main, app.py) gets stuck indefinitely right after the “:package: Processed dependencies!” log line. It never logs “Uvicorn server started” and never executes any line of app.py (no traceback, no error of any kind).

What I’ve tried (all unsuccessful):

  • Multiple reboots of the original app (URL: stulio-finance-pro-7xa6pgb2ttmkdper9lwqqo.streamlit.app)

  • Pinned streamlit==1.41.0, pandas==2.2.3 in requirements.txt (was previously unpinned, installing 1.58.0/3.0.3)

  • Changed Python version from 3.14 → 3.11 in Advanced Settings

  • Deleted the app entirely and recreated it from scratch with a new custom subdomain (stulio-finance-pro.streamlit.app), Python 3.11, fresh Secrets — same result

  • Tested in incognito/different browsers — frontend loads (CSS/theme renders, “Hosted with Streamlit” badge shows), but <div id="root"> stays empty

  • Confirmed: GitHub status OK, Supabase project active, streamlitstatus.com shows “All Systems Operational”

Logs consistently end at:

[XX:XX:XX] 🐍 Python dependencies were installed from /mount/src/stulio-finance-pro/requirements.txt using uv.
Check if streamlit is installed
Streamlit is already installed
[XX:XX:XX] 📦 Processed dependencies!

…and nothing further, ever (waited 30+ min multiple times).

This started suddenly during normal operation (no major code changes that should affect startup — same code ran fine minutes before via local testing/previous deploy).

Could someone from the Streamlit team take a look at the deployment/orchestration for this app? Account email: arqtulicesar@gmail.com

2

Hey there, thanks for the super detailed report and for sharing all your troubleshooting steps! :rocket: This “stuck after Processed dependencies!” issue—where the app never logs “Uvicorn server started” or executes any code—is a known symptom on Streamlit Community Cloud, especially when there are no errors or tracebacks and the frontend just shows a blank page. This can be caused by (1) a platform-level issue, (2) a problem with your requirements.txt (such as incompatible, missing, or built-in packages), (3) a Python version mismatch, or (4) a resource or orchestration bug on the backend. Multiple users have reported similar symptoms, and sometimes the root cause is on Streamlit’s side, not in your code or config. See examples and official troubleshooting in the docs and forum: App stuck at spinning up manager process, App deployment stuck after processed dependencies, and App not loading when running remotely.

You’ve already tried all the recommended steps: rebooting, deleting/redeploying, pinning package versions, and changing Python versions. At this point, the best next steps are: (a) double-check your requirements.txt for typos, unnecessary packages (don’t include built-in modules), and version conflicts, (b) ensure your entrypoint is correct (app.py in the repo root), and (c) try a minimal app.py (just st.write(“hello”)) to rule out code issues. If it still hangs, this is likely a platform issue—especially since you see no logs or errors and the same code works locally. The Streamlit team has acknowledged similar issues and sometimes resolves them on the backend. Keep an eye on Streamlit status and the deployment troubleshooting docs. If you haven’t already, please share your requirements.txt and a minimal reproducible example in the forum so the community can help debug further. Community members, feel free to jump in with your insights!

Sources: