[GH-ISSUE #396] [Bug]: May require login two times #224

New issue

Open

opened 2026-02-27 19:17:19 +03:00 by kerem · 0 comments

kerem commented

2026-02-27 19:17:19 +03:00

Owner

Originally created by @softgitron on GitHub (Jun 30, 2024).
Original GitHub issue: https://github.com/EddieTheCubeHead/Stagnum/issues/396

Originally assigned to: @EddieTheCubeHead on GitHub.

Contact details

roni.juntunen@gmail.com

Short description

There seems to be some kind of a login bug during initial login. If user has not logged to Spotify previously on the browser, login flow gets stuck on the phase, when credentials are returned to the application (token is visible in the address bar). User must manually remove token from the adress bar and login to escape this state.

Steps to reproduce

Open browser that has not been logged to the Spotify previously.
Login to Stagnum

Expected behaviour

User is succefully logged into Stagnum.

Actual behaviour

Stagnum is stuck at the middle of the login flow.

Additional information

Reproducible using Android, Chrome 126.0.6478.122.

Originally created by @softgitron on GitHub (Jun 30, 2024). Original GitHub issue: https://github.com/EddieTheCubeHead/Stagnum/issues/396 Originally assigned to: @EddieTheCubeHead on GitHub. ### Contact details roni.juntunen@gmail.com ### Short description There seems to be some kind of a login bug during initial login. If user has not logged to Spotify previously on the browser, login flow gets stuck on the phase, when credentials are returned to the application (token is visible in the address bar). User must manually remove token from the adress bar and login to escape this state. ### Steps to reproduce 1. Open browser that has not been logged to the Spotify previously. 2. Login to Stagnum ### Expected behaviour User is succefully logged into Stagnum. ### Actual behaviour Stagnum is stuck at the middle of the login flow. ### Additional information Reproducible using Android, Chrome 126.0.6478.122.