But these arw the http headers defined by Tidal for the Tidal service including authentication parameters. This is a standard way of using and invoking web services.
I cleared the issue by clearing web caches, clearing cookies and removing a VPN I had on one of my devices… whether a coincidence or not, the issue went away and has not happened since. I suspect it was cookie related.
This is weird, I tried this URL from Mobile (various browsers) but also from computer and various browser and same.
I believe I could try to review my router settings on this connected device but still not quite sure why Tidal refuses it.
Interesting, I installed the Naim app on my wife’s Samsung mobile and could login and get Tidal app working directly from Naim app.
There must be something wrong then with my own most recent Android (Google Pixel 8a).
We both are on Android 14. Pretty weird.
I also have fully uninstalled the app and reinstalled it.
Am quite puzzled.
Hi,
This may seem like an odd suggestion, but could you try the following please:
Go to Settings (Android settings), search for “Temperature” (it’s usually somewhere inside Languages or Location settings within System).
Then go to Regional Preferences > Temperature, and make sure it’s set to “Use default”.
Now force quit the Naim app, and retry the TIDAL authentication again.
We’ve seen some strange behaviour with this particular setting which showed up in this same way, when the temperature was set to anything other than Use Default.
(We’re working on a fix our end too to try and get around this)
Wow, great finding Paul!
This did resolve the issue.
My setting for Temperature was Celcius.
I am however very curious on why changing the Android Temperature in Celcius is damaging the Tidal Login process in Naim App!
Nice to see you are working on the resolution, thank you for your help, this has been puzzling me for months!
What we discovered is that the URL that the TIDAL sign in prompt generates (to redirect to the web browser) contains location data. It’s only usually the country, so that the correct website is loaded in the correct language. (eg, the URL will contain “gb” or “de” etc)
However, when setting this temperature setting, Android also includes the temperature setting in this location data.
Therefore the URL for the TIDAL sign in page was broken, as it contained something like “gb-celcius”, and was no longer valid.
I think we should be able to suppress this information before heading out to the web browser.
Thanks for the explanation.
This is right, I really was suspecting an issue with the URL call that was made from the app to Tidal, since the Mobile Tidal application was working fine.
This is a great finding, even I am surprised not more users had reported this issue!
Glad that you found the cause. Great Job!