Tidal does not work at all

Core Machine (Operating system/System info/Roon build number)

Computer: Lenovo IdeaPad S145-14IWL with Windows 10 Home v1909
Roon: Version 1.7 (build 528)

Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)

100/100 Ethernet (working at said speed…)

Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)

  • Host machine - Ethernet
  • Macbook Pro - Ethernet
  • iPhone - WiFi
  • SqueezeBox - Ethrenet
  • Chromecast - WiFi

Description Of Issue

Tidal no longer works at all with Roon. (=Nothing plays)

Roon finds the music but when I press play nothing happens on any of the above devices.

NB: Tidal works fine on its own on all devices.

It has been this way for a while (a month +/-) now (thought it may be Gremlins that would go away…)

I have logged in and out of Tidal several times to no avail.

The only thing I notice is that Roons constantly says that it is syncing the Tidal library but I can’t say this is different from how it has been in the past.

Looking forward to your feedback.



restart the core and logout out and back into tidal in the services screen

Hi @Ola_Harstrom,

Welcome to the forum!

I would give this a try and if this doesn’t help, you could try clearing out the TIDAL cache:

  • Exit out of Roon
  • Find and open your Roon database
  • Navigate to Roon/Cache
  • Move the contents of the /Cache folder elsewhere, like your desktop
  • Try restarting Roon and verify if the issue still occurs

Thank you.

Clearing the cache finally appears to have solved the issue.

Is this something you suggest one should do on a regular basis?

1 Like


Tried this but it turned out I had to clear the cache to fix the issue.

A post was split to a new topic: Can’t login to TIDAL - No login entry

Hi @Ola_Harstrom,

Glad to hear that clearing out the TIDAL cache resolved this issue on your end!

This is not something that you should regularly have to do, there have been quite a few changes to the TIDAL login process and we’re working on some improvements in this area, although these improvements are still in the works.

If the behavior re-occurs, please do let us know and we can take another look, thank you!

This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.