After the recent Roon app update on my iPad, I also received an email on update in Tidal terms. I was kicked out of Tidal in the Roon app and cannot log back in even though I have no problem logging into the Tidal app on the IPad. Have logged a support request to Tidal but I’m not sure if this is a Roon app issue or a Tidal issue.
Have tried restarting roon server with no improvements in Tidal working.
Just an update on my specs, I have a QNAP 251+ nas 4TB raid 1 running roon server build 165 that streams my music to a DAC, all flac/dsd and nas library works since the update on Nov 21 have had no issues except for the tidal login problem. No issues with Tidal’s own apps working in my network.
My controllers are 2 android associated roon remotes and a MacOSx Yosemite iMac, all 3 have roon remote tidal login issues.
I too had the same issues after agreeing to an update in Tidal terms, coincidence or something on Tidal’s end?
My system has recently developed problems connecting to Tidal and retrieving Roon account information, don’t know if the two problems are related. Can still login to both Tidal and Roon accounts from Chrome and/or IOS. Tried reentering Tidal account info within Roon but generates an error. Some days can connect to Tidal from Roon, other days no.
Roon core 1.2 build 165, 64 bit running on sonictransport
Hi @Eric_Walberg ---- Thank you for the report and my apologies for the troubles. I combined your most recent post with this thread as to keep this issue isolated in a single location. Can you confirm if you have tried:
Hi folks, the below procedure seemed to work for me.
I re-installed roon server on my Qnap 251+ in my NAS OS to Roon Server ver 1.0.1, re-installed the Roon remote build 165 on my android phone, re-mapped my music directories and that seemed to solve the tidal issues for those running it on a nap NAS.
If you are encountering this error on a linux-based core (includes Synology, Qnap, Sonic Transporter) then the following workaround may get you going.
You need to re-start RoonServer twice in succession. Don’t reboot your core, just stop the Roon package and restart it (Synology, Qnap, Sonic Transporter). Wait until your remote reconnects and then stop and start again.
If you’re running a native linux install then stop and start Roon using systemctl.
Best to count to 10 between the stop and start just to give all of the processes a chance to exit cleanly.
And if you didn’t catch it above then I’ll reiterate. You need to stop and start Roon TWICE. No need to mess with the Tidal login or your cache directory.
I am having this issue now as well. Unable to login to tidal with the ‘unexpected error’ message despite deleting the cache folder and restarting multiple times. I am able to login to my Tidal account fine from a browser or smartphone app. Core running in an Ubuntu based docker container hosted in unRAID 6. Core, app all updated to latest versions.