Unable to access Qobuz through Naim app (again)

I know I raised a similar issue on 26 August, but the same issue has occurred. (That time the problem seemed to resolve itself over a number of hours).

Today I have the same issue, which is that I am unable to access Qobuz through the Naim app. It says that I’m using an invalid username/password combination.

The Qobuz app opens fine. I used the Qobuz app to change my password and tried that in the Naim app, but I got the same message regarding invalid username/password combination.

In the Naim app there is no option to log out of Qobuz, only an option to log in. I assume this is because I am already logged out.

Should the password set in the Qobuz app enable Qobuz in the Naim app? In other words, should the same password apply to both the Qobuz app and Qobuz through the Naim app?

I do not use Qobuz Connect, in fact I cannot remember how! I have tried powering off the iPad, tried my iPhone instead. The same issue is present on all three of my Naim streamers.

Does anyone have any suggestions, please?

Try resetting your password again, using the Qobuz app or their website. Then write down, or save into your phone’s password app, the exact password, noting capitals, spaces, special characters etc. Then enter it exactly into the Naim app. Ensure you are entering your username correctly.

It’s strange that you get these issues; I stay logged into Qobuz month in, month out.

1 Like

i have had some success with qobuz issues on my naim streamer by deleting qobuz apps and downloading again - but is does mean you lose any imported music. their app does seem to affect naim streamers in unexpected ways (eg locking out the remote even when not using qobuz)

I’ve just tried resetting the password again and although it works in the Qobuz app, it doesn’t work in the Naim app. I have always saved the password to the passwords app in iOS and in the past I accepted the ‘strong’ password recommended by Apple. Although the typed passwords I have been trying today have been shorter, the Naim app still shows a number of asterisks equivalent to the longer Apple password. I then have to delete these to type the shorter password. I wonder if the Naim app takes time to reset and adopt the new password and somehow the password first seen overrules any subsequent typed entry. I have tried both the beta app and the old release app (v7.5.1). I shall now delete the beta app and reinstall to see if it picks up the new password.

Sadly, that didn’t work.

The beta app has been superseded by the public app, version 8.0 so if you’re still running 7.5 you should update it and try again.

I appreciate that, but I think that’s a red herring. I was grasping at straws to see if it would help. The beta app is version 8.0, so is the same as the release version. It is live until January. I was keeping 7.5.1 because there are things I’m not keen on in v8.0.

I have just tried on my wife’s iPad, which is updated to v8.0 and the same problem occurs: “Invalid username/email and password combination”.

Problem resolved! :grin:

I tried the Qobuz AI help. Among other things, it suggested turning off the streamer, the app and the router. Although the problem was replicated on all three streamers, the one I was using was an ND5XS2 in the garden room, so I switched this off while I went up in the loft to the router. Switched it all back on and… Bingo! I have no idea why it happened as normally it stays connected even with my ropey 4G broadband. Happy now. Thanks for the suggestions, @HungryHalibut , @indexical and @ChrisSU .

When new versions are released there are often small tweaks snuck in at the last minute, so it’s generally best to use the latest available version, but yes, chances are that it won’t solve your specific issue.

I think Qobuz login details can be a bit slow to filter though so I would log out of it on all your devices (Naim app and Qobuz web page) then restart the devices before attempting to log back in with a new password.

Edit: I see you are now sorted so hopefully all good.

It might have been a time issue as you say, Chris. That seemed to be the answer in August.