Runtime bugs for multi-page apps appeared in Ver. 1.36

Using Streamlit
, ,
1

“Fix some bugs. Add new ones.”

I hasten to inform the respected community and developers that starting from version 1.36, the page refreshes no longer work correctly for multi-page applications if it is not the main page of the application and some parameters are passed to it like:

image
image1383×334 30.2 KB

When a user tries to refresh the page through the browser (using the refresh button) the Streamlit freezes.

This problem appeared starting from version 1.36 (in version 1.37 the same incorrect behavior). In version 1.35 and older everything works correctly.

What have you “improved”, developers? :crazy_face:

2

Hello,
It’s already a know bug.

3

Thanks for the info.
Let’s hope it gets fixed in 1.38…

4

Can you provide a simple reproducible script which shows this bug? The bug mentioned by @Faltawer has been resolved in 1.37 Release notes - Streamlit Docs

  • :ant: Bug fix: Streamlit supports non-unix style paths for correct multipage routing in Windows (#8988, #8958).

Can you double-check that you’re actually running streamlit 1.37, and if the problem persists, can you add a comment on that issue with a simple script reproducing the issue?

5

Yes, I can.
Do you have access to my account data? Please get my email and write me.
In response to your email, I will provide you with the app’s source codes (partially) // commercial data & the auth subsystem will be removed //

6

Are you sure you’re running 1.37? Can you add a line st.write(st.__version__) to your app?

If you are indeed running 1.37, and you are still seeing this issue, the best way to debug it is to create a minimal, reproducible example How to create a Minimal, Reproducible Example - Help Center - Stack Overflow and put that in your post, or create a new issue on the streamlit repo Issues · streamlit/streamlit · GitHub and share that script

Creating a very simplified script that anyone can run that still reproduces the issue is the best way to make it likely that either:

  1. You find a bug with your code and can fix it
  2. Others on the forum find a bug with your code and can fix it
  3. Streamlit developers find a bug with Streamlit and can fix it
7

Perhaps I did not express myself very clearly. I will repeat.

  1. I have a large and complex application that works successfully in version 1.35 and does not work (in part of one of the pages of a multi-page application) in versions 1.36 and 1.37
  2. Depending on the parameters passed via the page URL, this page’s behavior must be changed.
  3. “Refresh” is emulation and is performed programmatically, using JQuerry.
  4. I’m not a student. My time as a developer is paid, so I’m not ready to write a separate example to “show it to everyone”. To write an example I need to spend time.
  5. I wrote to you about what I can do. I can quickly cut off the “sensitive parts” and send the source code privately, without publishing it anywhere if the development team needs it.

For us there is no problem with versions - we rolled back and now use the 1.35 in which everything works correctly (both on Ubuntu and Windows).

Regards.