I talked to our dev team, and their suggestion is that it’s probably a CSRF issue, and if that you use a custom deployment (e.g. with a proxy), you need to either:
- Disable CSRF protection
- Whitelist new
_streamlit_xsrfcookie name in your proxy layer