403/401 errors and no artists/playlists show after successful login – Plugin and metadata access totally broken in v5.0.0

[Kelvinmorcillo]

I've been trying to get Spotube v5.0.0 (build 42, stable) working clean on Windows, and after a massive cluster of issues, this is the result:

Login with Spotify now works sometimes after clearing everything, but after logging in, absolutely no artists, no playlists, no metadata show up at all.

Every single call to get artists/albums/playlists or any metadata provider results in a 403 or 401 error in the logs:

Example: DioException bad response ... status code 403 ... MetadataPluginUserEndpoint.savedArtists ...

Sometimes 401 and a "calling method subgetter on null object credentials" crash deep in the plugin scripts.

Settings screams: "No default metadata plugin is set. Please set a default plugin in the settings." But when I try to install or select a metadata provider, nothing works.

I've cleaned every config/cache, started fresh, reinstalled, and your DB migration bug about duplicate column name: connect_port is still spamming the logs by the way.

I’ve tried logging out/in, rebooting, everything short of animal sacrifice.
[
runCustom.txt
runCustom.txt
](url)
This is un-fixable from the user side:

The app’s plugin/metadata provider system is 100% busted – either the plugin endpoints, credentials, or API keys are blocked, expired, or the plugin server/API is f****d.

All evidence suggests this is due to either backend/OAuth issues or broken plugin endpoints, not local config.

What do you want users to do?

Is there an ETA or workaround, or am I just dead in the water until plugin server/auth is fixed upstream?

Please stop asking users to “relogin” or “try clean config” – the endpoint/plugin handshake clearly just returns 401/403 every time.

Here are actual pastebin logs if you want the gory details. Happening in v5.0.0 stable, clean Windows install.

[dieBakterie]

DioException [bad response]: This exception was thrown because the response has a status code of 401 and RequestOptions.validateStatus was configured to throw for this status code.
The status code of 401 has the following meaning: "Client error - the request contains bad syntax or cannot be fulfilled"
Read more about status codes at https://developer.mozilla.org/en-US/docs/Web/HTTP/Status
In order to resolve this exception you typically have either to verify and fix your request code or you have to fix the server code.

Here is my error log