Hi,
I’m building an app on Streamlit 1.45 that uses the builtin authentication via OIDC with Auth0 as provider.
Overall login experience works fine but sometimes I get the yellow warning messages saying:
Please replace st.experimental_user with st.user. st.experimental_user will be removed after 2025-11-06.
I’ve checked that my application code does not use the deprecated field but I suspect some of the modules in the requirements that are used under the hood still use the old experimental implementation. My requirements are the following:
st-annotated-text==4.0.2
streamlit==1.45.0
streamlit-card==1.0.2
streamlit-embedcode==0.1.2
streamlit-extras==0.6.0
streamlit-faker==0.0.3
streamlit-highcharts==0.2.0
streamlit-image-coordinates==0.1.9
streamlit-keyup==0.3.0
streamlit-toggle-switch==1.0.2
streamlit-vertical-slider==2.5.5
Is there a way to find out where the warning is generated?
Test each package separately. The older packages are the main suspects.
You may find a better way if you narrow down “sometimes I get the yellow warning messages” to a specific user action performed in specific circunstances, a.k.a a reproducible issue.
Unfortunately, providing a reproducible issue is not easy. The issue often seems to occur when I’m using a breakpoint to stop the execution of the application in debugging sessions. I’ll try to build a minimal example, but as I can not identify any piece of my code responsible for the issue, I don’t have a way to isolate it.
I’ve tried a bit of digging, but don’t see anything obvious in any of those libraries that seems to be using st.experimental_user. One approach you might take is unpinning the specific versions and trying to upgrade all the packages to the latest versions, and see if that resolves the warning.
Thanks for stopping by! We use cookies to help us understand how you interact with our website.
By clicking “Accept all”, you consent to our use of cookies. For more information, please see our privacy policy.
Cookie settings
Strictly necessary cookies
These cookies are necessary for the website to function and cannot be switched off. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms.
Performance cookies
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us understand how visitors move around the site and which pages are most frequently visited.
Functional cookies
These cookies are used to record your choices and settings, maintain your preferences over time and recognize you when you return to our website. These cookies help us to personalize our content for you and remember your preferences.
Targeting cookies
These cookies may be deployed to our site by our advertising partners to build a profile of your interest and provide you with content that is relevant to you, including showing you relevant ads on other websites.