github-starred/android
2
0
Fork 0
mirror of https://github.com/bitwarden/android.git synced 2026-05-08 04:16:40 -05:00
Code Issues 1.1k Packages Projects Releases 122 Wiki Activity

[GH-ISSUE #4109] connecting failure error #27914

New Issue
Closed
opened 2026-04-18 11:36:19 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-18 11:36:19 -05:00
Owner
Copy Link

Originally created by @shortcut00 on GitHub (Oct 16, 2024).
Original GitHub issue: https://github.com/bitwarden/android/issues/4109

Bitwarden Beta

  • I'm using the new native Bitwarden Beta app and I'm aware that legacy .NET app bugs should be reported in bitwarden/mobile

Steps To Reproduce

  1. Go to '...'
  2. Click on '...'
  3. Scroll down to '...'
  4. Click on '...'

Expected Result

I expectation Not "connecting failure" error message on my Android 6

Actual Result

Screenshot_20241017-023608

Screenshots or Videos

Screenshot_20241017-023608

Additional Context

No response

Build Version

lastik github realase

Environment Details

Zte blade a506 android 6

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 @shortcut00 on GitHub (Oct 16, 2024). Original GitHub issue: https://github.com/bitwarden/android/issues/4109 ### Bitwarden Beta - [X] I'm using the new native Bitwarden Beta app and I'm aware that legacy .NET app bugs should be reported in [bitwarden/mobile](https://github.com/bitwarden/mobile) ### Steps To Reproduce 1. Go to '...' 2. Click on '...' 3. Scroll down to '...' 4. Click on '...' ### Expected Result I expectation Not "connecting failure" error message on my Android 6 ### Actual Result ![Screenshot_20241017-023608](https://github.com/user-attachments/assets/d1556a8e-283b-47e2-ad56-ca3d88620db2) ### Screenshots or Videos ![Screenshot_20241017-023608](https://github.com/user-attachments/assets/d25f3cc0-92dd-417b-98c7-eae4a01e9112) ### Additional Context _No response_ ### Build Version lastik github realase ### Environment Details Zte blade a506 android 6 ### 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.
GiteaMirror added the bug label 2026-04-18 11:36:19 -05:00
GiteaMirror commented 2026-04-18 11:36:20 -05:00
Author
Owner
Copy Link

@bitwarden-bot commented on GitHub (Oct 16, 2024):

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

<!-- gh-comment-id:2418149718 --> @bitwarden-bot commented on GitHub (Oct 16, 2024): Thank you for your report! We've added this to our internal board for review. ID: PM-13777
GiteaMirror commented 2026-04-18 11:36:21 -05:00
Author
Owner
Copy Link

@BBGhub commented on GitHub (Oct 16, 2024):

Hi There,

The issue you are facing is a result of Let's Encrypt shortening it's chain of trust: https://letsencrypt.org/2023/07/10/cross-sign-expiration.html

Bitwarden uses a Let's Encrypt certificate for it's services - please note the message on this page that states:

If you use Android 7.0 or earlier, you may need to take action to ensure you can still access websites secured by Let’s Encrypt certificates. We recommend installing and using Firefox Mobile, which uses its own trust store instead of the Android OS trust store, and therefore trusts ISRG Root X1.

You could explore the option of installing the ISRG Root X1 certificate in the Android OS trust store, though this is something I am not able to assist you with myself. We recommend accessing your Bitwarden vault using the Firefox Mobile browser via https://vault.bitwarden.com or https://vault.bitwarden.eu at this time.

If you have any further questions, please don't hesitate to ask.

As a side note, the minimum Android version for the mobile app will be raised to 9.0 when the native build is released.

<!-- gh-comment-id:2418164577 --> @BBGhub commented on GitHub (Oct 16, 2024): Hi There, The issue you are facing is a result of Let's Encrypt shortening it's chain of trust: https://letsencrypt.org/2023/07/10/cross-sign-expiration.html Bitwarden uses a Let's Encrypt certificate for it's services - please note the message on this page that states: If you use Android 7.0 or earlier, you may need to take action to ensure you can still access websites secured by Let’s Encrypt certificates. We recommend installing and using Firefox Mobile, which uses its own trust store instead of the Android OS trust store, and therefore trusts ISRG Root X1. You could explore the option of installing the ISRG Root X1 certificate in the Android OS trust store, though this is something I am not able to assist you with myself. We recommend accessing your Bitwarden vault using the Firefox Mobile browser via https://vault.bitwarden.com or https://vault.bitwarden.eu at this time. If you have any further questions, please don't hesitate to ask. As a side note, the minimum Android version for the mobile app will be raised to 9.0 when the native build is released.
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 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#27914
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?