This is issue is external to Roon and not related to today’s Roon update.
Roon staff have contacted Tidal and are available to support their engineers to resolve.
Same here, the callback on the roon side of the OAuth flow doesn’t seem to understand tidal return as the attached screenshot shows it.
This seems related to last update (as I just update my Server and this started to happen) or to a change on Tidal side that was silently ignored until now.
Makes sens, I had tidal playing just before the update, so I guessed it could be related.
After the update, tidal service in roon settings was as usual, I just couldn’t access any tidal track from my library.
I then decided to log out and log in again, without being able to complete the process.
I’ve come up to my vacation home for the holidays. I’ve unauthorised my Nucleus at my normal residence and logged into a Roon server on my Mac… have done this numerous times before.
When trying to login to my Tidal account I get the following error message: non-200 status code from Tidal, code: 403
I’d appreciate any help on resolving this issue as soon as possible.
From the thread I’ve linked, this doesn’t seem related to the last roon update but happen at the same time…
Please add your voices to this thread, as we’ll all have a better support if all information are collected at the same place.
I’ve tried the tidal integration from my Kef speakers and it’s broken too.
So the problem seems to be on tidal side: they have a broken OAuth flow right now.
Nothing to wait from roon, it’s tidal that must fix this authentication issue on their side.
Haven’t used my roon for three months and decided to rig it up for Christmas - lifetime subscription and also Tidal user which works on phone and other platforms have tried to access Tidal from settings and am getting this error or whatever it is, first time I’ve ever had this have updated both Rock and App on iPhone