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

Validation Error when updating Fdroid Version #1823

New Issue
Closed
opened 2025-11-26 22:59:01 -06:00 by GiteaMirror · 10 comments
GiteaMirror commented 2025-11-26 22:59:01 -06:00
Owner
Copy Link

Originally created by @aaron1857 on GitHub (Mar 20, 2024).

Steps To Reproduce

  1. have the 2024.3.0 version of Bitwarden from the F-Droid repo installed
  2. Use an fdroid client to update to the 2024.3.1 version of the app.
  3. The update fails because of some key validation error.

Expected Result

The app should update successfully like other apps. I have confirmed that other apps from fdroid seem to update just fine.

Actual Result

The update fails due to us key validation error.

I use the droidify client and I get a notification with "Could not validate Bitwarden" and "Could not check integrity"

Screenshots or Videos

I can provide a screenshot if necessary but I don't think it is in this case.

Additional Context

No response

Operating System

Android

Operating System Version

Android 14

Device

Google Pixel 8

Build Version

2024.3.0

Beta

  • Using a pre-release version of the application.
Originally created by @aaron1857 on GitHub (Mar 20, 2024). ### Steps To Reproduce 1. have the 2024.3.0 version of Bitwarden from the F-Droid repo installed 2. Use an fdroid client to update to the 2024.3.1 version of the app. 3. The update fails because of some key validation error. ### Expected Result The app should update successfully like other apps. I have confirmed that other apps from fdroid seem to update just fine. ### Actual Result The update fails due to us key validation error. I use the droidify client and I get a notification with "Could not validate Bitwarden" and "Could not check integrity" ### Screenshots or Videos I can provide a screenshot if necessary but I don't think it is in this case. ### Additional Context _No response_ ### Operating System Android ### Operating System Version Android 14 ### Device Google Pixel 8 ### Build Version 2024.3.0 ### Beta - [ ] Using a pre-release version of the application.
GiteaMirror added the bug label 2025-11-26 22:59:01 -06:00
GiteaMirror commented 2025-11-26 22:59:02 -06:00
Author
Owner
Copy Link

@sammbw commented on GitHub (Mar 20, 2024):

Hi there,

I am unable to reproduce this issue, it has been escalated for further investigation. If you have more information that can help us, please add it below.

Thanks!

@sammbw commented on GitHub (Mar 20, 2024): Hi there, I am unable to reproduce this issue, it has been escalated for further investigation. If you have more information that can help us, please add it below. Thanks!
GiteaMirror commented 2025-11-26 22:59:02 -06:00
Author
Owner
Copy Link

@aaron1857 commented on GitHub (Mar 20, 2024):

I am not sure what changed overnight. It could have been an issue on my end, but the app seems to be able to update for me now. I successfully updated using the same fdroid client.

If the problem was indeed on my end, I apologize for taking your time.

@aaron1857 commented on GitHub (Mar 20, 2024): I am not sure what changed overnight. It could have been an issue on my end, but the app seems to be able to update for me now. I successfully updated using the same fdroid client. If the problem was indeed on my end, I apologize for taking your time.
GiteaMirror commented 2025-11-26 22:59:03 -06:00
Author
Owner
Copy Link

@Vishnu2jd commented on GitHub (Mar 21, 2024):

It has happened to me a few times. The app refuses to update, citing a validation error. I simply ignore it and try to update a couple of days later, and then it updates normally. I thought it was due to my college internet with its firewall. Observed that it happens just after new update is released.

@Vishnu2jd commented on GitHub (Mar 21, 2024): It has happened to me a few times. The app refuses to update, citing a validation error. I simply ignore it and try to update a couple of days later, and then it updates normally. I thought it was due to my college internet with its firewall. Observed that it happens just after new update is released.
GiteaMirror commented 2025-11-26 22:59:03 -06:00
Author
Owner
Copy Link

@DirkBaumeister commented on GitHub (Mar 31, 2024):

Hi,
today I don't see a validation error when updating from 2024.3.0 to 2024.3.1 but just a "Download failed!" notifcation. Other apps could be updated just fine.
Is there any problem you know of?

Edit:
Just debugged the fdroid app a little and saw the issue:
Your URL for downloading the apk responses with a 503 Response object too large
You can see it here: https://mobileapp.bitwarden.com/fdroid/repo/com.x8bit.bitwarden-fdroid.apk
Bildschirmfoto 2024-03-31 um 12 31 04

@DirkBaumeister commented on GitHub (Mar 31, 2024): Hi, today I don't see a validation error when updating from 2024.3.0 to 2024.3.1 but just a "Download failed!" notifcation. Other apps could be updated just fine. Is there any problem you know of? Edit: Just debugged the fdroid app a little and saw the issue: Your URL for downloading the apk responses with a 503 Response object too large You can see it here: https://mobileapp.bitwarden.com/fdroid/repo/com.x8bit.bitwarden-fdroid.apk <img width="626" alt="Bildschirmfoto 2024-03-31 um 12 31 04" src="https://github.com/bitwarden/mobile/assets/16743298/58e9b6fe-b8ea-4c3c-9849-413bc143ae4c">
GiteaMirror commented 2025-11-26 22:59:03 -06:00
Author
Owner
Copy Link

@gitterspec commented on GitHub (Mar 31, 2024):

Seeing the same re: Download failed! and in browser, Error 503

@gitterspec commented on GitHub (Mar 31, 2024): Seeing the same re: Download failed! and in browser, Error 503
GiteaMirror commented 2025-11-26 22:59:03 -06:00
Author
Owner
Copy Link

@ItsIgnacioPortal commented on GitHub (Mar 31, 2024):

Yup, same here. Error 503

@ItsIgnacioPortal commented on GitHub (Mar 31, 2024): Yup, same here. Error 503
GiteaMirror commented 2025-11-26 22:59:04 -06:00
Author
Owner
Copy Link

@Para-lyzed commented on GitHub (Apr 3, 2024):

@DirkBaumeister If you could open a new issue, I think that would be best. This issue seems to be unrelated, as the user was experiencing some form of validation error after the file was already downloaded. It might be hard to find your issue (I experience the same when I try to use the fdroid repo) since the devs would have to scroll down in an issue that appears to have resolved itself anyway with the original user. It looks like it's an issue with the way they're hosting the file, so it should hopefully be an easy fix when the devs are notified of it (with a new issue posting).

@Para-lyzed commented on GitHub (Apr 3, 2024): @DirkBaumeister If you could open a new issue, I think that would be best. This issue seems to be unrelated, as the user was experiencing some form of validation error after the file was already downloaded. It might be hard to find your issue (I experience the same when I try to use the fdroid repo) since the devs would have to scroll down in an issue that appears to have resolved itself anyway with the original user. It looks like it's an issue with the way they're hosting the file, so it should hopefully be an easy fix when the devs are notified of it (with a new issue posting).
GiteaMirror commented 2025-11-26 22:59:04 -06:00
Author
Owner
Copy Link

@DirkBaumeister commented on GitHub (Apr 3, 2024):

@DirkBaumeister If you could open a new issue, I think that would be best. This issue seems to be unrelated, as the user was experiencing some form of validation error after the file was already downloaded. It might be hard to find your issue (I experience the same when I try to use the fdroid repo) since the devs would have to scroll down in an issue that appears to have resolved itself anyway with the original user. It looks like it's an issue with the way they're hosting the file, so it should hopefully be an easy fix when the devs are notified of it (with a new issue posting).

Thanks, just created one 😊

@DirkBaumeister commented on GitHub (Apr 3, 2024): > @DirkBaumeister If you could open a new issue, I think that would be best. This issue seems to be unrelated, as the user was experiencing some form of validation error after the file was already downloaded. It might be hard to find your issue (I experience the same when I try to use the fdroid repo) since the devs would have to scroll down in an issue that appears to have resolved itself anyway with the original user. It looks like it's an issue with the way they're hosting the file, so it should hopefully be an easy fix when the devs are notified of it (with a new issue posting). Thanks, just created one 😊
GiteaMirror commented 2025-11-26 22:59:04 -06:00
Author
Owner
Copy Link

@franco27 commented on GitHub (May 4, 2024):

I had the same issue before but it has been resolved in recent versions.

On Github, I download the APK file with "fdroid" in the name, and when I wanted to update Bitwarden with the downloaded installation file, I would get an error message.

For several updates, I had to uninstall the application and reinstall it with the update. However, I noticed that in the last two or three updates, I no longer had this problem.

@franco27 commented on GitHub (May 4, 2024): I had the same issue before but it has been resolved in recent versions. On Github, I download the APK file with "fdroid" in the name, and when I wanted to update Bitwarden with the downloaded installation file, I would get an error message. For several updates, I had to uninstall the application and reinstall it with the update. However, I noticed that in the last two or three updates, I no longer had this problem.
GiteaMirror commented 2025-11-26 22:59:04 -06:00
Author
Owner
Copy Link

@vvolkgang commented on GitHub (Jun 20, 2024):

Issue migrated to https://github.com/bitwarden/mobile/issues/3097

@vvolkgang commented on GitHub (Jun 20, 2024): Issue migrated to https://github.com/bitwarden/mobile/issues/3097
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#1823
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?