Deauthing the app from the website makes it go into offline mode with no option to reauth

[lauranolte]

Setup:

• Windows 10
• Scrobbler v3.1.27.1

Steps:

• Be logged into the app
• Go to the application website settings (this is in the current website RC and not publicly available yet)
• Remove the app from there

Actual behaviour:

• The app still shows the user as signed in and then shows as (Offline)
• There is no option to sign in again
• After exiting and opening the app again, the log in screen is shown and the user can reauth

Expected:

• The app recognises that the user has deauthed and shows the log in screen (same as logging out from within the app), or another way to log in again

[VorTechS]

The app now recognises the user has de-authed, and will force the user to re-authenticate.

The same is also now true of API Key suspension, and Invalid API Key - although the latter is unlikely to occur whilst the application is running, more at startup which was already covered.

[ben-xo]

Now that I'm back from jury service, finally got round to testing this.

• Deauthing the app does what you'd expect if you quit the app and start it again: next start presents a login box
• Deauthing the app only partially does what you'd expect if you deauth mid session: sending a "scrobble" event DOES trigger the app to realise it's logged out. However, sending a "now playing" or "loved" events doesn't trigger the app to realise it's logged out
• If the settings window is open when it realises it's logged out, the settings window remains open when the login window is open. These should never be visible at the same time

It is, however, broadly usable like this.

[lauranolte]

v3.1.28.1 fixes the issue for me where it recognises that my user is no longer authenticated and prompts to re-login without me having to re-open the app.