TIDAL Issues on Android/iOS/Windows

I have this issue…on ios, Android and windows…

Hello @Phil_Knowles,

So we can better assist you, please provide a brief description of your current setup using this link as a guide.

Make sure to describe your network configuration/topology, including any networking hardware currently in use, so we can have a clear understanding of how your devices are communicating.

Is there any change in behavior if you log out and back into TIDAL via the Roon Services tab?

Hi… essentially, I notice that in the Services section of Roon the Tidal service has a continual spinning icon next to it. I log out and back in and it resolves but often reappears the following day. So the resolution is logging out and back in. Not ideal of course.

I think this is connected to another thread where the Tidal cache is not working. I just replied there after following instructions to shut the server down and rename the cache file. This has fixed the problem now, but am hoping this will not reoccur.
Is there a way the cache can be cleared from within the software please?

Hi @Phil_Knowles,

Can I please ask that you submit a log package by using these instructions and a screenshot of your TIDAL sync status in Roon Settings -> Services -> TIDAL next time Roon is in this state for you? The best way to get the logs and screenshot over would be via a shared Dropbox / Google Drive link but if you don’t have either service just let me know and we can use an alternate method. Thanks!

Mine is doing it now…

This looks to be a problem where Roon is trying to sync the library with Tidal. It never stops. There is another thread I found here which suggested stopping the server and clearing the tidal cache. I did this and renamed the folder and restarted the server. All is running fine now without having to log out and in again.
It would be good to understand why this happens though as the fix is a bit cumbersome.

1 Like

Hi @Phil_Knowles,

I’ve moved your posts into your existing thread so we can better keep track of what troubleshooting you have performed.

I agree, and for us to do this, please provide the info I requested if this behavior re-occurs:

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