[Bug]: When Last.fm says "Invalid session key - Please re-authenticate" there is no normal way to re-authenticate

[ImMALWARE]

Preflight Checklist

• I use the latest version of Pear Desktop (Application).
• I have searched the issue tracker for a bug report that matches the one I want to file, without success.
• I understand that pear-devs/pear-desktop has NO affiliation with Google or YouTube

Pear Desktop (Application) Version

3.11.0.0

Checklists

• I use the portable version of the Pear Desktop Application.
• I can reproduce this issue in the official version of (WEB) YTM.

What operating system are you using?

Windows

Operating System Version

Windows 10 21H2

What CPU architecture are you using?

x64

Last Known Working Pear Desktop (Application) version

No response

Reproduction steps

1. Enable Scrobbler plugin, enable Last.fm, enter API data.
2. Log in to Last.fm
3. Change Last.fm password or somehow else revoke that authorized session (?) I don't know exactly how my session key became invalid, but I remember that I changed Last.fm password.

Expected Behavior

Application will ask to log in to Last.fm again

Actual Behavior

Application tries to scrobble, but doesn't do anything with session key error. I didn't even know, why it didn't scrobble, before opening Charles.

Enabled plugins

1. Album Color Theme
2. Ambient Mode
3. Blur Navigation Bar
4. Discord Rich Presence
5. Downloader
6. Exponential Volume
7. In-App Menu
8. Music Together
9. Navigation
10. Notifications
11. Performance improvement
12. Precise Volume
13. Scrobbler
14. Shortcuts & MPRIS
15. Synced Lyrics
16. Taskbar Media Control

Additional Information

The only way that I found to fix this is to go to app's data folder, open config.txt and delete line plugins.scrobbler.scrobblers.lastfm.sessionKey. After restart, it will ask to reauthenticate and scrobbler will work fine.

[ArjixWasTaken]

You can directly open the config by using the menu btw

so I'd consider it a "normal" way :^)

but yeah, this definitely needs to be improved

[ArjixWasTaken]

Marked it as a bug because it definitely shouldn't silently ignore the error