Hello All,
Thank you for the reports here and apologies for the inconvenience.
We are closely monitoring this issue and as others have mentioned on this thread, we’re not seeing any signs that this behavior is related to our latest Roon production update.
At this time, the issue appears to be related to TIDAL’s OAuth system, and the behavior started to occur even before the update was published, an unfortunate case of coincidental timing.
We are standing by, ready to assist TIDAL in any way needed to help resolve this issue for all our mutual customers. We’ll update everyone as we have more details on this.