Disabling email prompt when students first run Streamlit?

I’ve created a tutorial that walks students through cloning a simple streamlit app, modifying it and then deploying it to streamlit cloud.

When I first ran it as a workshop students balked when Streamlit asked for an email address. I did not anticipate this because it looks like Streamlit only gives this prompt the first time you run it, and I had done that so long ago.

I looked into suppressing this email prompt to make the course run smoother. I discovered that if I create a file .streamlit/config.toml and set showEmailPrompt=false it won’t prompt for an email.

But then students got an error because even though Streamlit isn’t prompting for an email, it still needs one.

I then did some research and saw that in the same file I might be able to add email=”foo@example.com”. But since my first attempt to bypass this failed, I’m reluctant to try again (especially because I seem unable to test it myself). Also, I am concerned that skipping this might break deploying from github to Streamlit Cloud, which they do later on.

Is there a way to disable this email prompt while still allowing cloud deployment from github to work?

Thanks.

It looks like there was a Github issue raised a few weeks ago here that sounds similar to what you’re explaining. It has since been resolved with an update.

Have you tried this out with the latest version of Streamlit as that should include the fixes?

1 Like

Thanks so much.

My goal with using uv for this workshop was to force everyone to use a known stable version of Python and all packages I was using. It’s kind of funny that I might have frozen everything to a version and configuration that had a bug :sweat_smile:

It looks like the version of Streamlit I was using was 1.48.0. I have upgraded it to 1.49.1 in the repo so hopefully this fixes issues for other people in the future.

I will reach out to the student who has the problem and ask them to try this fix.

My student confirmed that this solved the problem, and I have updated my repo with the latest version of Streamlit as well. Thank you so much - I would not have thought that this was a bug in streamlit itself which had been fixed!

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.