cwr64
April 15, 2026, 1:29am
1
Hi, Please point me exactly to the place where it tells me how to post a question about a problem I’m having. Problem happens on Samsung A35 5G Android cellphone. I am logged onto my W10PC right now. At cellphone logon to Bitwarden, I logon with master PW and BW first pops a thing asking me to update encryption by entering my master password. I then enter my master password and the process fails. The failure generates a “stacktrace” whatever that is, but I did capture the stacktrace. And then Bitwarden has me logged in as normal. I think I’m using the Brave browser, btw, but I think the browser is not up when this happens.
dwbit
April 15, 2026, 12:32pm
2
Hi there, if the issue persists after reinstalling, please contact support directly at: Help Center | Bitwarden
I am getting this issue on android I keep getting this window: "Update Your Encryption Settings" but my Master Password continually fails. Please Help
At logon I’m being prompted for master password, and I found that the only way to fix it was to reinstall the application. Seems this iOS bug has affected android as well.
Pixel 10 Pro
Android 16
dwbit
April 15, 2026, 2:45pm
4
HI @SireSalty thanks for confirming that reinstalling resolved the issue for you.
geo
(George)
April 17, 2026, 11:19pm
5
Getting this update encryption prompt when I open Bitwarden app on my Android mobile phone (screenshot) …
When I supply requested master password the update crashes. Below is the error message:
Stacktrace:
retrofit2.HttpException: HTTP 400
com.bitwarden.network.core.NetworkResultCall.toNetworkResult(r8-map-id-82b2ce132d84bf0c0f66d53f9b3d907545fe37ac79c4ec3e6cc54fd216ad5899:9)
com.bitwarden.network.core.NetworkResultCall.access$toNetworkResult(r8-map-id-82b2ce132d84bf0c0f66d53f9b3d907545fe37ac79c4ec3e6cc54fd216ad5899:1)
com.bitwarden.network.core.NetworkResultCall$enqueue$1.onResponse(r8-map-id-82b2ce132d84bf0c0f66d53f9b3d907545fe37ac79c4ec3e6cc54fd216ad5899:11)
v75.h(r8-map-id-82b2ce132d84bf0c0f66d53f9b3d907545fe37ac79c4ec3e6cc54fd216ad5899:13)
j77.run(r8-map-id-82b2ce132d84bf0c0f66d53f9b3d907545fe37ac79c4ec3e6cc54fd216ad5899:49)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1154)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:652)
java.lang.Thread.run(Thread.java:1564)
Version: 2026.3.1 (21415)
Device: motorola motorola razr plus 2024 15@35 prod
CI: commit: bitwarden/android/release/2026.3-rc49@c2ef20e1ed74a9cba60b19d5849af168629d3756
build source: bitwarden/android/actions/runs/236604596
40/attempts/1
@geo I’ve moved your post into a thread on the same topic. – See above for the solution.
PS: Here the corresponding bug report on GitHub (Android repo):
opened 05:36PM - 15 Apr 26 UTC
bug
app:password-manager
### Steps To Reproduce
On a Samsung Galaxy XCover6 Android, I bring up the Bitw… arden client.
I log in to Bitwarden using my thumbprint.
I get a popup that says "Update your encryption settings"
I enter my password in the popup and click Submit.
### Expected Result
I don't know what should happen as part of this updating of encryption parameters, but certainly not this.
### Actual Result
I get a popup with "An error has occurred"
The error details are
Stacktrace:
retrofit2.HttpException: HTTP 400
com.bitwarden.network.core.NetworkResultCall.toNetworkResult(r8-map-id-82b2ce132d84bf0c0f66d53f9b3d907545fe37ac79c4ec3e6cc54fd216ad5899:9)
com.bitwarden.network.core.NetworkResultCall.access$toNetworkResult(r8-map-id-82b2ce132d84bf0c0f66d53f9b3d907545fe37ac79c4ec3e6cc54fd216ad5899:1)
com.bitwarden.network.core.NetworkResultCall$enqueue$1.onResponse(r8-map-id-82b2ce132d84bf0c0f66d53f9b3d907545fe37ac79c4ec3e6cc54fd216ad5899:11)
v75.h(r8-map-id-82b2ce132d84bf0c0f66d53f9b3d907545fe37ac79c4ec3e6cc54fd216ad5899:13)
j77.run(r8-map-id-82b2ce132d84bf0c0f66d53f9b3d907545fe37ac79c4ec3e6cc54fd216ad5899:49)
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1154)
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:652)
java.lang.Thread.run(Thread.java:1564)
Version: 2026.3.1 (21415)
Device: 📱 samsung SM-G736U 🤖 15@35 📦 prod
CI: 🧱 commit: https://github.com/bitwarden/android/commit/c2ef20e1ed74a9cba60b19d5849af168629d3756
💻 build source: bitwarden/android/actions/runs/23660459640/attempts/1
This happened two days ago and I managed to capture a flight recorder log, but not the stack trace. Yesterday I captured the stack trace but didn't get a flight recorder log. Go figure.
I originally opened this issue in the general bitwarden GIT repository, and was advised to try logging out on of my app, logging in on another machine through the web, and restarting the app. That didn't fix it, but uninstalling the Bitwarden app, restarting my phone, and reinstalling Bitwarden got it so that I was no longer prompted to update any settings, and everything has worked fine since. So I'm filing this just in case someone thinks it's worth pursuing, not because I need help.
[bitwarden_flight_recorder4161458653137638145.zip](https://github.com/user-attachments/files/26758111/bitwarden_flight_recorder4161458653137638145.zip)
### Screenshots or Videos


### Additional Context
I've attached the flight recorder zip file.
This was repeatable.
This happened shortly after I changed which fingerprints I registered with the biometric system on my phone.
### Build Version
2026.3.1 (21415)
### What server are you connecting to?
US
### Self-host Server Version
_No response_
### Environment Details
Samsung Galaxy XCover6 Android
Android 15
### Issue Tracking Info
- [x] I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
geo
(George)
April 18, 2026, 3:06pm
7
Uninstall and re-install of Bitwarden from Google Play app store has bypassed this issue. Will advise if it re-occurs.
Note: Side effect of an uninstall is loss of some local settings, e.g. biometrics, and shortcuts. So if the actual root cause was fixed by developers instead of this workaround, would be much appreciated!
I think they’re working on it.
(See also this comment and this PR for the Android app: https://github.com/bitwarden/android/pull/6802 )