The workaround worked perfectly fine with streamlit 1.3.1
, I had some issues with the built-in session state that’s why I was switching to the workaround, see comment
The approach you described sounds like the proper solution, but that still does not explain the strange behavior I observed in the last 1-2 weeks. Maybe a devops/backend engineer from your side could provide more insights or maybe you have to check with them what kind of changes were done recently. There were definitly some major changes that broke tons of applications hosted in streamlit cloud.
Best regards,
Nico