Hey @stevev1 We have investigated this issue, and found two separate problems, both of which are now resolved.
One issue was traced back to a bug in the 3rd party HTTP implementation that Roon uses on Linux, and the other issue was traced back a server-side change made at TIDAL which required that login sessions be re-established unexpectedly. These fixes both concern outside entities and as such, they were reasonably complex, and we weren’t completely in control of the timing.
Point being, when we have simple low-risk fixes, we always try to get them out as quickly as possible, even if that means porting them back to the previous release, and putting that one change through QA before releasing it. We do everything we can to avoid leaving bugs out in the world for a minute longer than is required.
Unfortunately, in this case the fixes have been more involved and can’t easily be separated from the work we’ve been doing over the last few months for 1.3. Getting this release right has taken longer than expected, and we’ve been discussing changes that will minimize the chances of this happening again in the future. For now, these fixes need to be tested as part of 1.3, and will be released when it goes live.
This has dragged on longer than we’d like, and for now I’d encourage everyone to read over the steps posted above and pass on details to our team, so we can confirm our understanding of the issue.
We appreciate your patience everyone, and I assure you all that we’re working hard to get this resolved as soon as possible.