Latest iOS app says "An error has occurred." - can log into web vault fine

[abc (ABC Taylor)]

Has Bitwarden just trashed the iOS app for self hosted users? Recently I noticed the entire UI changed and I get the above error (and I haven’t logged into my VM running Bitwarden for months, so nothing has willingly been changed on the backend).

Immediately, after entering an email in the app, the error appears. I’ve tried uninstalling the iOS app and adding it back again.

It seems like the error appears instantly. It doesn’t wait for any http requests. The cert is trusted in iOS’ root trust store.

What’s happened? This is pretty disappointing, and I hope it’s a simple fix.

[abc (ABC Taylor)]

Clicking OK through the error message takes you to the master password field.

• a bad master password fails (so it can speak to the server)
• a good master password works, and prompts for 2FA

2FA hangs, and eventually after 30s says “invalid verification code”.

[Nail1684]

@abc Hi!

@abc

(and I haven’t logged into my VM running Bitwarden for months, so nothing has willingly been changed on the backend).

That seems to be the problem. The new native mobile app needs an update to the latest server versions.

[abc (ABC Taylor)]

Thanks for replying. Is the usual ./bitwarden.sh update and updateself sufficient? This didn’t fix anything when I tried it a while ago.

I did see a red ERROR after the script ran (No such service: mssql) - I am using an external MSSQL server and that’s online and has been fine.

[Fifty]

Same here. Web and desktop vault access works with my master pw and 2FA, but not the iOS app. I have another thread open on my current experience.

[Nail1684]

@abc Sorry, I’m not familiar with self-hosting myself.

@Fifty Since @abc is self-hosting, the experience of the last days show, that the login problems “vanish” after the server update, so for now I presume, there are different problems for the two of you.

[grb]

@Fifty

Same here.

So you are self-hosted, after all? What server version?

[abc (ABC Taylor)]

The server version for me is 2024.9.1 (at time of writing there is only 2024.9.2 which is later, so the Docker image is indeed very recent)

I can see it clearly doing the pulls when running ./bitwarden.sh updateself and then update:

[abc (ABC Taylor)]

and then back to the MSSQL error above.

[abc (ABC Taylor)]

Not fixed yet, but found I disabled updates to docker-compose.yml to force keeping the mssql container dead (since I use external MSSQL)… maybe since 2019 this file has drifted quite a bit. I am going to take the opportunity to do a fresh install, or just move over to the Helm chart.

[grb]

@abc

Thanks for replying. Is the usual ./bitwarden.sh update and updateself sufficient?

Should be, but in the opposite order: updateself then update.

@abc

I am using an external MSSQL server

I suspect that your issue may be related to the above, although I do not have sufficient expertise to troubleshoot this further. What version is your external MSSQL server (2019 is required, 2022 recommended)?

Have you contacted Customer Support?

@abc

I am going to take the opportunity to do a fresh install

This is probably for the best.

[abc (ABC Taylor)]

Quick one… I migrated to Kubernetes (yes! was quick). When trying to login I see this in the admin pod’s logs:

Bit.Admin.Auth.Jobs.DeleteAuthRequestsJob[2]
      Error performing DeleteAuthRequestsJob.
      Microsoft.Data.SqlClient.SqlException (0x80131904): Could not find stored procedure 'dbo.AuthRequest_DeleteIfExpired'.

This smells to me like the backend has changed a lot and there are new DB stored procedures that aren’t in my (five year old) SQL database… best course of action here? I’d like to run some sort of DB migration without trashing the entire thing (trashing = export vault to json, import again on fresh DB).

[grb]

@abc

I’d like to run some sort of DB migration

I would strongly recommend contacting the Support team. They have experience with various migration scenarios, and may be able to offer advice.

In the meantime, perhaps it might be worth it to spin up a new database just to check if the iOS incompatibility issue has been resolved with the updated back end?

[Nail1684]

@abc

without trashing the entire thing (trashing = export vault to json, import again on fresh DB).

Though I have no clue here, exporting to JSON as a backup if something goes wrong, might be a good idea.

[abc (ABC Taylor)]

Solution (for people with external MSSQL - about 45 mins of work…)

1. Go ahead and nuke your bwdata
2. Get the latest install script
3. Modify the version lines in bitwarden.sh to add a variable $ver for the version numbers for CORE/WEB/KEY… (we’re gonna be changing these value loads soon)

ver="2023.1.0"

COREVERSION="$ver"
WEBVERSION="$ver"
KEYCONNECTORVERSION="$ver"

4. find out what version your last successful migration was. In SSMS it looks like this:
   
   
   
   go ahead and set your $ver above to a release around then.
5. run ./bitwarden.sh updatedb
6. keep incrementing the version number until you get to a fairly modern version, and keep trying the app, browser extension and web portal until one of them works