Trouble logging in to TIDAL with new method

[wkasdo (Willem)]

Same here. Roon server log says this, every second:

02/22 16:09:45 Warn: [tidal/http] GET https://api.tidal.com/v1/sessions/?countryCode=NL => Unauthorized {"status":401,"subStatus":6001,"userMessage":"User does not have a valid session"}
02/22 16:09:45 Info: [broker/locations] updating location Tidal:Name=TIDAL:Id=a2bc918b-81fb-abc3-f24b-<something>          

Update: traced it back to first instance, timezone CET:
02/22 08:49:18

Update: it just started working again after I logged on from Roon to Tidal for the 10th time:

02/22 16:20:38 Debug: [easyhttp] [820] GET to https://oauthcb.roonlabs.net/1/tidal/refresh?token=<token> returned after 204 ms, status code: 200
02/22 16:20:38 Info: [broker/locations] updating location Tidal:Name=TIDAL:Id=a2bc918b-81fb-abc3-f24b-<something>
02/22 16:20:38 Debug: [easyhttp] [822] GET to https://oauthcb.roonlabs.net/1/tidal/refresh?

[dylan (Dylan Caudill)]

Thanks for the report, @wkasdo.

We’ve enabled diagnostics so we can take a closer look at what’s occurring here. In the meantime, can you describe your Core and networking setup?

[wkasdo (Willem)]

Core is running on a QNAP NAS. Networking between Core and clients is a flat subnet, wired. Internet is 50 Mbit fiber.

Status : Running
Version : 1.7 (build 521) stable
QPKG-Version : 2019-06-09

At the time of the problem, the TIDAL app itself was fine. Just the logon from Roon to Tidal was not.

[wkasdo (Willem)]

Once again trouble logging on to Tidal, with a different error this time:

04/02 18:08:44 Warn: [tidal/http] GET https://api.tidal.com/v1/featured/recommended/playlists?countryCode=NL&offset=0&limit=30 => Unauthorized {"status":401,"subStatus":11003,"userMessage":"The token has expired. (Expired on time)"}
04/02 18:08:44 Info: [tidal] got token expired. refreshing token

I cannot access any Tidal content. Local playback is fine.

Speculating: the “refresh” is not succeeding, even though there is nothing about success or failure in the log.

[Arjun_Luthra]

I have this same error, very regularly as well. Today for example, a sync started 7:35 but never completed and essentially hung everything tidal related going forward 9:35, tried to play a track around 9:49. Only way for me to get around this is to log out and re-login.

Another issue with this, when in this hung state, if I try to play a tidal track to a bluesound device, it won’t play a library track either, unless I do a transfer from another device.

Line 16432: 04/02 07:35:03 Trace: [tidal/storage] sync force=False
Line 16433: 04/02 07:35:03 Trace: [tidal/storage] scan 164: starting
Line 16434: 04/02 07:35:03 Warn: [tidal/http] GET https://api.tidal.com/v1/users/nnnnn/favorites?countryCode=US => Unauthorized {"status":401,"subStatus":11003,"userMessage":"The token has expired. (Expired on time)"}
Line 16435: 04/02 07:35:03 Info: [tidal] got token expired. refreshing token


Line 17314: 04/02 09:35:03 Trace: [tidal/storage] sync force=False
Line 17315: 04/02 09:35:03 Trace: [tidal/storage] sync requested, but another is in progress. Ignoring request
Line 17801: 04/02 09:49:17 Warn: [tidal/http] GET https://api.tidal.com/v1/tracks/nnnnn/playbackinfopostpaywall?countryCode=US&audioquality=HI_RES&assetpresentation=FULL&playbackmode=STREAM => Unauthorized {"status":401,"subStatus":11003,"userMessage":"The token has expired. (Expired on time)"}
Line 17802: 04/02 09:49:17 Info: [tidal] got token expired. refreshing token
Line 20079: 04/02 10:45:37 Warn: [tidal/http] GET https://api.tidal.com/v1/tracks/nnnnn/playbackinfopostpaywall?countryCode=US&audioquality=HI_RES&assetpresentation=FULL&playbackmode=STREAM => Unauthorized {"status":401,"subStatus":11003,"userMessage":"The token has expired. (Expired on time)"}
Line 20080: 04/02 10:45:37 Info: [tidal] got token expired. refreshing token
Line 20153: 04/02 10:45:39 Warn: [tidal/http] GET https://api.tidal.com/v1/tracks/nnnnn/playbackinfopostpaywall?countryCode=US&audioquality=HI_RES&assetpresentation=FULL&playbackmode=STREAM => Unauthorized {"status":401,"subStatus":11003,"userMessage":"The token has expired. (Expired on time)"}
Line 20154: 04/02 10:45:39 Info: [tidal] got token expired. refreshing token
Line 20166: 04/02 10:45:59 Warn: [tidal/http] GET https://api.tidal.com/v1/tracks/nnnnn/playbackinfopostpaywall?countryCode=US&audioquality=HI_RES&assetpresentation=FULL&playbackmode=STREAM => Unauthorized {"status":401,"subStatus":11003,"userMessage":"The token has expired. (Expired on time)"}
Line 20167: 04/02 10:45:59 Info: [tidal] got token expired. refreshing token
Line 20183: 04/02 10:45:59 Warn: [tidal/http] GET https://api.tidal.com/v1/tracks/nnnnn/playbackinfopostpaywall?countryCode=US&audioquality=HI_RES&assetpresentation=FULL&playbackmode=STREAM => Unauthorized {"status":401,"subStatus":11003,"userMessage":"The token has expired. (Expired on time)"}
Line 20184: 04/02 10:45:59 Info: [tidal] got token expired. refreshing token

[wkasdo (Willem)]

Happened again, stopped when transitioning to a next track:

04/04 22:00:07 Warn: [tidal/http] GET https://api.tidal.com/v1/tracks/13377171/playbackinfopostpaywall?countryCode=NL&audioquality=HI_RES&assetpresentation=FULL&playbackmode=STREAM => Unauthorized {"status":401,"subStatus":11003,"userMessage":"The token has expired. (Expired on time)"}
04/04 22:00:07 Info: [tidal] got token expired. refreshing token
04/04 22:00:07 Warn: [tidal/http] GET https://api.tidal.com/v1/tracks/13377170/playbackinfopostpaywall?countryCode=NL&audioquality=HI_RES&assetpresentation=FULL&playbackmode=STREAM => Unauthorized {"status":401,"subStatus":11003,"userMessage":"The token has expired. (Expired on time)"}
04/04 22:00:07 Info: [tidal] got token expired. refreshing token

Workaround: restart the Roon Server. @dylan could you have a look?

[dylan (Dylan Caudill)]

Hi @wkasdo,

We have some upcoming improvements to our TIDAL integration that we think will help here. It’s still in testing currently so I can’t provide any specific timelines, but we hope to have this released soon!

[wkasdo (Willem)]

Hi @dylan, glad to hear that, thanks for the update!

(edited, non-related error removed)