I had to uninstall Tidal HiFi to log back into Strawberry Tidal

I don't understand what's this issue with the tidal-hifi app at all. I can use both at the same time. Assuming you mean this app.

again reinstalling and now I can no longer update any playlists, authors, tracks, or albums. The tab closes instantly after starting a search, being impossible to give any results. Only the search for a particular row or author works.

Which version. Say the full build filename.

Have you deleted/renamed these user config folders whenever you have reinstalled Strawberry, even once as a test? It is not normally needed but something in the database might be messed up considering all the weird issues you're having.

~/.local/share/strawberry
~/.config/strawberry

Rename them to something. Launch Strawberry, login to Tidal and see if the problems still persist. If they do then undo the renaming and you'll lose no settings.

I give up my collection in Strawberry.

??
Don't worry about losing it since it is always synced back your Tidal account.

I had to uninstall Tidal HiFi to log back into Strawberry Tidal

I don't understand what's this issue with the tidal-hifi app at all. I can use both at the same time. Assuming you mean this app.

again reinstalling and now I can no longer update any playlists, authors, tracks, or albums. The tab closes instantly after starting a search, being impossible to give any results. Only the search for a particular row or author works.

Which version. Say the full build filename.

Have you deleted/renamed these user config folders whenever you have reinstalled Strawberry, even once as a test? It is not normally needed but something in the database might be messed up considering all the weird issues you're having.

~/.local/share/strawberry
~/.config/strawberry

Rename them to something. Launch Strawberry, login to Tidal and see if the problems still persist. If they do then undo the renaming and you'll lose no settings.

I give up my collection in Strawberry.

??
Don't worry about losing it since it is always synced back your Tidal account.

It's common for Tidal to return 404 for some albums listed in the favorites. It might be albums that Tidal have removed from their catalog, but still are listed in the favorites, or they are not accessible through the API, not entirely sure.

In my (Tidal official app) favourite collection the albums were greyed out and no longer showed up search results. So likely removed or georestricted.

Now using 1.0.10-9-gf48d133b, no issues but since I removed the error-making albums I can't anymore do a repro.

A workaround that worked for me:

It appears that the "not found albums" are albums that have been removed from or made regionally unavailable in Tidal.

So I went through my albums collection in Tidal Android app and removed them (the unavailable ones are greyed out) and now the refresh completes with all the newly added albums and without errors.

I only had remove to a few albums. Didn't count them but it probably corresponded to the amount of errors.

Created a bug report: https://github.com/strawberrymusicplayer/strawberry/issues/1061

Fixed. Looks like it was a quick fix so probably something changed on Tidal's end.

Might have to wait for a new version release some weeks because the last release was 6 days ago.

How do you know if the albums you want to appear in your collection are favorites or not?

I'm not sure after all. Since the last successful refresh couple of days ago I had added 7 albums via official Tidal app and I got 7 errors. So I made an assumption. Now as a test added one more but the amount of errors was still 7. Regardless, the recently added ones don't appear in Strawberry collection but that might be because the refresh never finishes properly.

On the other hand, I observe that the search for the complete list of albums is done in a very short time, while the one for covers takes a long time.

That has always been the case. The covers take a long time since it actually downloads them as image files.

On the other hand, you cannot start a search from Strawberry, nor from artists, albums or songs with the Tidal HiFi application open and playing on the same PC because Tidal immediately blocks Strawberry with the warning "The token has expired on time (401) ( 1103)".

Can't replicate this issue and it sounds like a separate issue.

So I delete Tidal Hi Fi, scan with Strawberry, playing a song from my collection. The previous warning no longer appears but the search does not give any results.
I don't understand why this warning appears when I have used a token extracted from my android mobile. The same thing happens to me with the other token.

Search works for me normally. My token is from an old Android version too (this) and I fetched it months ago.

But I still doubt your issue is the token since login works and that means it is a valid token.

Created a bug report: https://github.com/strawberrymusicplayer/strawberry/issues/1061

This is happening for me too.

I don't think the token or Strawberry package version is the problem since you are able to log in and this issue didn't exist about 2 days ago on my installation and I haven't made any changes.

• I can still browse and play anything I had added since the previous successful refresh and also searching and favouriting/unfavouriting in Strawberry works.

• If I favourite/unfavourite an album in Strawberry, that does get updated to Tidal database almost right away (without a catalogue refresh) and it shows up in official Tidal apps. But neither new adds or removals made in official Tidal app get updated back to Strawberry.

• I logged out and back in. Didn't help.

I wonder if it is just some temporary i ssue on Tidal's end.

I have 1.0.10 from the official PPA (ppa:jonaski/strawberry).

@hogthow said in Tidal account:

@kamilos_x I ran into the same problem with the latest version of the Tidal Android app. I had to uninstall the Tidal android app and load an older version (I used 2.3.7) and it worked fine.

Yes, it looks like something has changed.

In 2.3.7 (from APKMirror) the format is like this:

[REDACTED].0:X-Tidal-Token: [REDACTED/this is the part you need]

While in later versions it is:

[REDACTED].0:vary: x-tidal-sessionid,x-tidal-token,authorization

Anyway, finally got it to work.