github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-06-12 05:27:02 -05:00
Code Issues 2.3k Packages Projects Releases 128 Wiki Activity

[GH-ISSUE #6485] [PM-31796] The latest Bitwarden Android app version (from Google Play Store) cannot connect to my self-hosted Vaultwarden server anymore #15094

New Issue
Closed
opened 2026-04-15 01:27:05 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-15 01:27:05 -05:00
Owner
Copy Link

Originally created by @herkul24 on GitHub (Feb 5, 2026).
Original GitHub issue: https://github.com/bitwarden/android/issues/6485

Steps To Reproduce

Steps to reproduce

Install latest Bitwarden Android app from Play Store

Configure it to connect to a Vaultwarden server

Try to log in or sync

Connection fails, Vaultwarden logs errors

Install older APK (2025.11)

Login and sync works instantly

Expected Result

Expected behavior

Bitwarden Android should connect to Vaultwarden normally, just like previous versions and other platforms (iOS, Desktop, Web).

Additional notes

No server, DNS, or reverse proxy changes were made on my side

The issue began only after the most recent Android update

A second account (my wife’s) has the same issue on the same phone

The same account works fine on an iPhone

This appears to be a client-side regression specific to the new Android build.

Actual Result

Description

The latest Bitwarden Android app version (from Google Play Store) cannot connect to my self-hosted Vaultwarden server anymore.
This issue started suddenly a few days ago without any server changes.

When I install an older Bitwarden APK (2025.11), the connection works immediately again.
The issue is 100% reproducible and affects only the latest Android version.

Bitwarden on iOS, Desktop, and Web Vault continues to work normally.

This strongly suggests a regression in the latest Bitwarden Android release.

Device

Phone: Xiaomi 15

OS: Android 16

Bitwarden version (broken): latest Play Store release (2025.12.x)

Bitwarden version (working): 2025.11 APK

Server: Self-hosted Vaultwarden (running in Proxmox LXC)
What happens

When trying to log in or sync with the newest Android version:

The app shows an error (“cannot connect” / “unexpected error”)

Vaultwarden receives requests without a valid access token

Some requests cause DNS resolve errors server-side

Xiaomi + Android 16 appears to be affected (iPhone works fine)

After downgrading to Bitwarden Android 2025.11, everything works immediately again.

Relevant Vaultwarden log excerpts

  1. Repeated DNS/Resolve errors when receiving requests from the new Android app
    reqwest::Error
    hyper_util::client::legacy::Error
    ConnectError
    "dns error"
    ResolveError
    ProtoError

  2. Authentication errors from the new Android app
    [auth][ERROR] Unauthorized Error: No access token provided

These errors appear only when using the latest Bitwarden Android version.
They disappear completely when downgrading to APK 2025.11.

Screenshots or Videos

No response

Additional Context

Additional notes

No server, DNS, proxy, or configuration changes were made

Another account on the same phone fails in the same way

Same account works fine on iPhone

Issue appears specific to new Android app on Xiaomi + Android 16

This appears to be a client-side regression in the latest Bitwarden Android release.

Build Version

2026.1

What server are you connecting to?

Self-host

Self-host Server Version

Vaultwarden 1.34.3 + Web-Vault 2025.7.0

Environment Details

Environment

Client (problematic):

Device: Xiaomi 15

OS: Android 16

Bitwarden version (broken): latest Play Store release (2025.12.x)

Bitwarden version (working): 2025.11 (APK)

Server:

Vaultwarden 1.34.3

Web-Vault 2025.7.0

Running inside Proxmox LXC using Docker

Reverse proxy + DNS unchanged

Issue Tracking Info

  • 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.
Originally created by @herkul24 on GitHub (Feb 5, 2026). Original GitHub issue: https://github.com/bitwarden/android/issues/6485 ### Steps To Reproduce Steps to reproduce Install latest Bitwarden Android app from Play Store Configure it to connect to a Vaultwarden server Try to log in or sync Connection fails, Vaultwarden logs errors Install older APK (2025.11) Login and sync works instantly ### Expected Result Expected behavior Bitwarden Android should connect to Vaultwarden normally, just like previous versions and other platforms (iOS, Desktop, Web). Additional notes No server, DNS, or reverse proxy changes were made on my side The issue began only after the most recent Android update A second account (my wife’s) has the same issue on the same phone The same account works fine on an iPhone This appears to be a client-side regression specific to the new Android build. ### Actual Result Description The latest Bitwarden Android app version (from Google Play Store) cannot connect to my self-hosted Vaultwarden server anymore. This issue started suddenly a few days ago without any server changes. When I install an older Bitwarden APK (2025.11), the connection works immediately again. The issue is 100% reproducible and affects only the latest Android version. Bitwarden on iOS, Desktop, and Web Vault continues to work normally. This strongly suggests a regression in the latest Bitwarden Android release. Device Phone: Xiaomi 15 OS: Android 16 Bitwarden version (broken): latest Play Store release (2025.12.x) Bitwarden version (working): 2025.11 APK Server: Self-hosted Vaultwarden (running in Proxmox LXC) What happens When trying to log in or sync with the newest Android version: The app shows an error (“cannot connect” / “unexpected error”) Vaultwarden receives requests without a valid access token Some requests cause DNS resolve errors server-side Xiaomi + Android 16 appears to be affected (iPhone works fine) After downgrading to Bitwarden Android 2025.11, everything works immediately again. Relevant Vaultwarden log excerpts 1. Repeated DNS/Resolve errors when receiving requests from the new Android app reqwest::Error hyper_util::client::legacy::Error ConnectError "dns error" ResolveError ProtoError 2. Authentication errors from the new Android app [auth][ERROR] Unauthorized Error: No access token provided These errors appear only when using the latest Bitwarden Android version. They disappear completely when downgrading to APK 2025.11. ### Screenshots or Videos _No response_ ### Additional Context Additional notes No server, DNS, proxy, or configuration changes were made Another account on the same phone fails in the same way Same account works fine on iPhone Issue appears specific to new Android app on Xiaomi + Android 16 This appears to be a client-side regression in the latest Bitwarden Android release. ### Build Version 2026.1 ### What server are you connecting to? Self-host ### Self-host Server Version Vaultwarden 1.34.3 + Web-Vault 2025.7.0 ### Environment Details Environment Client (problematic): Device: Xiaomi 15 OS: Android 16 Bitwarden version (broken): latest Play Store release (2025.12.x) Bitwarden version (working): 2025.11 (APK) Server: Vaultwarden 1.34.3 Web-Vault 2025.7.0 Running inside Proxmox LXC using Docker Reverse proxy + DNS unchanged ### 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.
GiteaMirror added the app:password-managerbug labels 2026-04-15 01:27:05 -05:00
GiteaMirror commented 2026-04-15 01:27:08 -05:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Feb 5, 2026):

Thank you for your report! We've added this to our internal board for review.
ID: PM-31796

<!-- gh-comment-id:3855710011 --> @bitwarden-bot commented on GitHub (Feb 5, 2026): Thank you for your report! We've added this to our internal board for review. ID: [PM-31796](https://bitwarden.atlassian.net/browse/PM-31796) [PM-31796]: https://bitwarden.atlassian.net/browse/PM-31796?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
GiteaMirror commented 2026-04-15 01:27:08 -05:00
Author
Owner
Copy Link

@pamperer562580892423 commented on GitHub (Feb 5, 2026):

Duplicate of https://github.com/bitwarden/android/issues/6363

<!-- gh-comment-id:3855812134 --> @pamperer562580892423 commented on GitHub (Feb 5, 2026): Duplicate of https://github.com/bitwarden/android/issues/6363
GiteaMirror commented 2026-04-15 01:27:09 -05:00
Author
Owner
Copy Link

@Neonwarden commented on GitHub (Feb 5, 2026):

Hi there!

Thank you for your report, it seems like it is a duplicate of this one https://github.com/bitwarden/android/issues/6363.

If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time in there - our engineering team will be happy to review these.

This issue will now be closed.

Thanks!

<!-- gh-comment-id:3855889132 --> @Neonwarden commented on GitHub (Feb 5, 2026): Hi there! Thank you for your report, it seems like it is a duplicate of this one https://github.com/bitwarden/android/issues/6363. If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time in there - our engineering team will be happy to review these. This issue will now be closed. Thanks!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
app:authenticator
app:password-manager
bug
bug-passkey
customer-support
duplicate
enhancement
good first issue
help wanted
needs-reply
needs-response
pull-request
Mirrored from GitHub Pull Request
 question
No Label app:password-manager bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/android#15094
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?