Cookie problems now show up in the UI
Until now, when cookie authentication did not work, the provider fell back to anonymous mode and said so only in the server log. Search and playback kept working, so nothing looked wrong while library sync had quietly stopped (#92).
On MA 2.10 and newer the provider now flags itself in Settings → Music sources and explains the problem on its settings page:
- Authentication required when the cookie is rejected at startup, when Browser cookie is selected with an empty cookie field, or when a cookie that worked stops working while the provider runs. The text says what still works and how to capture a fresh cookie.
- Setup failed with a Reload button when the cookie could not be checked at all (no network at startup, YouTube Music down). The cookie may be fine; reload once YouTube Music is reachable.
The provider keeps running in anonymous mode underneath, so search and playback are unaffected. Saving a working cookie reloads the provider and clears the notice. On MA 2.9 the log warning is still the only sign.
Also in this release:
- A cookie pasted with a leading or trailing space now works. Before, it failed authentication.
- Error text shown in the notice and the log has cookie values redacted.
- An HTTP proxy's "407 Proxy Authentication Required" is no longer mistaken for an expired cookie.
Updating: run the installer script again or let the watcher add-on pick it up, then restart Music Assistant.
What's Changed
- feat: show a UI notice while cookie auth is not working (#92) by @sproft-bot in #93
Full Changelog: v1.1.5...v1.2.0