First of all, huge kudos to @hulver : your assumption was absolutely spot on! Thanks for taking the time to share it; your input helped us quickly identify what was going on (fun fact: neither we nor TIDAL initially thought of this).
Here’s what happened:
TIDAL recently narrowed the validity window for authentication tokens. Our method for refreshing those tokens was no longer sufficient (that’s on us, our implementation wasn’t fully aligned with how it should have been done).
The good news:
We’ve fixed the issue.
The not-so-good news: it’s not something we can patch remotely via the cloud. The fix requires an update on the devices themselves. We’re currently validating the fix and will release an emergency update for all platforms in the next few days (as soon as QA is complete).
In the meantime:
- If you’re affected by the issue, when TIDAL errors out, simply disable and then re-enable TIDAL from the Sources settings page.
- Once the update is available and installed, everything will work as expected again.
We sincerely apologize for the inconvenience: this one’s on us.
Thanks for your patience and for helping us track this down