August 2025 update: This bug has been fixed in Gradio 5.12.0. Incidentally, it can be circumvented in earlier versions of Gradio by adding an OAuth login button and logging-in. However, personally, I recommend using Gradio 5.12.0 or later simply.