Error message on iOS app - User unintuitive and unfriendly design

Ask the Community Password Manager
, , ,
1

Sorry I need to vent… Bitwarden been driving us nuts

Basically I introduced bitwarden to my friends and family. Especially family, however non of them are tech-savy. When they need bitwarden urgently, bitwarden on iOS basically gave them an error about request cannot be completed. No matter we have done

We thought, maybe wifi? maybe DNS? maybe restart the app? maybe reboot the phone? account hacked? checking bitwarden status? logged in via web broswer? wasted like 15-25 minutes

This cause a lot of issues especially when we were needing information and needing to save important information for things like gov services, ID card #.

After we went home, we logged out and re-logged into bitwarden, and everything went fine. My question is, how hard is it for bitwarden to give user a clear guidance on what to do instead of throwing the following into user’s screen?

BitwardenKit.ResponseValidationError(response: Networking.HTTPResponse(body: 25 bytes, headers: [“Accept-Ranges”: “bytes”, “x-content-type-options”: “nosniff”, “Content-Type”: “application/json; charset=UTF-8”, “Strict-Transport-Security”: “max-age=31557600”, “x-xss-protection”: “1; mode=block”, “x-frame-options”: “SAMEORIGIN”, “x-cache-hits”: “0”, “x-served-by”: “cache-yyc1430024-YYC”, “x-cache”: “MISS”, “Date”: “Fri, 18 Jul 2025 00:42:42 GMT”, “Pragma”: “no-cache”, “Cache-Control”: “no-store, no-cache, max-age=0”], statusCode: 400, requestID: B15CFAC7-0412-4B91-A43A-A92A38F07FD6, url: https://identity.bitwarden.com/connect/token))
The operation couldn’t be completed. (BitwardenKit.ResponseValidationError error 1.)

Stack trace:
0 BitwardenShared 0x000000010532acb4 __swift_memcpy81_8 + 80500
1 BitwardenShared 0x000000010510bca9 objectdestroy.13Tm + 11569
2 BitwardenShared 0x00000001050c2699 objectdestroyTm + 1909
3 BitwardenShared 0x000000010511ddc1 objectdestroyTm + 27185
4 BitwardenShared 0x000000010511ad71 objectdestroyTm + 14817
5 BitwardenShared 0x0000000105203ee5 __swift_memcpy96_8 + 240357
6 BitwardenShared 0x00000001050c2699 objectdestroyTm + 1909
7 BitwardenShared 0x00000001056216d5 objectdestroy.12Tm + 905
8 BitwardenShared 0x00000001050bddfd __swift_destroy_boxed_opaque_existential_0 + 15925
9 BitwardenShared 0x00000001050b98b9 __swift_memcpy1_1 + 7933
10 BitwardenShared 0x00000001051c8471 __swift_memcpy24_8 + 39457
11 BitwardenShared 0x00000001050b98b9 __swift_memcpy1_1 + 7933
12 BitwardenShared 0x00000001054aa665 block_destroy_helper + 20877
13 BitwardenShared 0x00000001050c2699 objectdestroyTm + 1909
14 libswift_Concurrency.dylib 0x00000001abb91241 DCB9E73A-92BA-3782-BC6D-3E1906622689 + 414273

Binary images:
Bitwarden: 0x0000000104cb8000
BitwardenShared: 0x00000001050b0000
BitwardenKit: 0x0000000104e7c000

User ID: 12ee45a5-[…]
Version: 2025.6.0 (2235)
:mobile_phone: iPhone14,6 :green_apple: iOS 18.5 :package: Production
:brick: commit: bitwarden/ios/release/2025.06-rc10@ff06d9c6cc8da89f78f37f376495800201d7261a
:laptop: build source: bitwarden/ios/actions/runs/15831780687/attempts/1

2

I’m getting the same error. Noticed my last sync was April 25 2025. Arrgh,.

Here’s my error:

BitwardenKit.ResponseValidationError(response: Networking.HTTPResponse(body: 25 bytes, headers: [“Accept-Ranges”: “bytes”, “x-cache-hits”: “0”, “x-content-type-options”: “nosniff”, “Content-Type”: “application/json; charset=UTF-8”, “Pragma”: “no-cache”, “x-served-by”: “cache-chi-kigq8000095-CHI”, “x-xss-protection”: “1; mode=block”, “x-frame-options”: “SAMEORIGIN”, “Date”: “Tue, 22 Jul 2025 16:07:57 GMT”, “Cache-Control”: “no-store, no-cache, max-age=0”, “Strict-Transport-Security”: “max-age=31557600”, “x-cache”: “MISS”], statusCode: 400, requestID: 9371079A-CC43-4EEF-A4FA-AB392CE74508, url: https://identity.bitwarden.com/connect/token))
The operation couldn’t be completed. (BitwardenKit.ResponseValidationError error 1.)

Stack trace:
0 BitwardenShared 0x0000000106e659d8 __swift_memcpy81_8 + 75672
1 BitwardenShared 0x0000000106c47ca9 objectdestroy.13Tm + 11569
2 BitwardenShared 0x0000000106bfe699 objectdestroyTm + 1909
3 BitwardenShared 0x000000010702f8ed block_destroy_helper.29 + 43833
4 BitwardenShared 0x0000000106d433a5 block_destroy_helper + 10229
5 BitwardenShared 0x0000000106bfe699 objectdestroyTm + 1909
6 BitwardenShared 0x000000010715d6d5 objectdestroy.12Tm + 905
7 BitwardenShared 0x0000000106bf9fa5 __swift_destroy_boxed_opaque_existential_0 + 16349
8 BitwardenShared 0x0000000106bfe699 objectdestroyTm + 1909
9 BitwardenShared 0x0000000106d04471 __swift_memcpy24_8 + 39457
10 BitwardenShared 0x0000000106bf58b9 __swift_memcpy1_1 + 7933
11 BitwardenShared 0x0000000106fe6665 block_destroy_helper + 20877
12 BitwardenShared 0x0000000106bfe699 objectdestroyTm + 1909
13 libswift_Concurrency.dylib 0x00000001982d1241 DCB9E73A-92BA-3782-BC6D-3E1906622689 + 414273

Binary images:
Bitwarden: 0x0000000104920000
BitwardenShared: 0x0000000106bec000
BitwardenKit: 0x0000000104c98000

User ID: 13d587d7-b4a2-4a13-9a1e-acd201642644
Version: 2025.6.0 (2235)
:mobile_phone: iPhone16,1 :green_apple: iOS 18.5 :package: Production
:brick: commit: bitwarden/ios/release/2025.06-rc10@ff06d9c6cc8da89f78f37f376495800201d7261a
:laptop: build source: bitwarden/ios/actions/runs/15831780687/attempts/1

3

Exactly, this is very frustrating, cuz it fails silently… only when we needed information, and we were puzzled like why isn’t it there? and then this huge error show up when it is trying to talk to server, and we literally stood in an office for like 15 minutes trying to pull information from our bitwarden… and failed…

With this, I would give bitwarden a UX of 0 stars, totally useless and wasting time

4

@JoshM @jwasilko To avoid any misunderstanding in this thread, would you please re-confirm that your accounts are hosted on Bitwarden’s cloud servers (and not self-hosted)?

5

Confirmed. I’m using Bitwarden’s cloud servers

I resolved my issue by logging out and back in. But more concerning is Bitwarden never told me it wasn’t syncing

6

There is also GitHub issue with the same kind of error message (though OP there closed it, as it was also resolved with logging in again it seems):

(PS: They also seem to use the “BW cloud”.)

PPS: I added “Error message on iOS app” to the title.

7

Yes, using cloud, provided by bitwarden, not self hosted

8

I did resolved this by logging in and out, but is that the real solution? Again for tek savvy people, they prob could try this and try that, but as general users, this was frustrating, because user cannot pull their latest info, cannot save new item and the error provides no clear solution

9

@JoshM Ah, this “pull request” seems to tackle that issue / error (message):

→ it’s already merged, so it should be in the next (or one of the next) release(s)

10

Perfect! Love it! Looking forward for the next release!

1 Like
11

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.