F-Droid - Error Installing Bitwarden #1529

@Silejonu commented on GitHub (Dec 2, 2022):

Same issue on clean GrapheneOS install with Google Pixel 6a. Did someone found a workaround?

I successfully installed it on GrapheneOS on a Pixel 6a through F-Droid.

@Silejonu commented on GitHub (Dec 2, 2022): > Same issue on clean GrapheneOS install with Google Pixel 6a. Did someone found a workaround? I successfully installed it on GrapheneOS on a Pixel 6a through F-Droid.

GiteaMirror commented

@Xstoudi commented on GitHub (Dec 3, 2022):

Seems to work today!

@Xstoudi commented on GitHub (Dec 3, 2022): Seems to work today!

GiteaMirror commented

@shrimprugbysnowowl commented on GitHub (Dec 3, 2022):

Reattempted the installation and nothing has changed on my end. I even deleted and recreated the Bitwarden repo.

@shrimprugbysnowowl commented on GitHub (Dec 3, 2022): Reattempted the installation and nothing has changed on my end. I even deleted and recreated the Bitwarden repo.

GiteaMirror commented

@jcz1 commented on GitHub (Dec 6, 2022):

"...apk failed to verify!" :(
version 2022.10.1
LineageOS 19 + microG

@jcz1 commented on GitHub (Dec 6, 2022): "...apk failed to verify!" :( version 2022.10.1 LineageOS 19 + microG

GiteaMirror commented

@catfluoride commented on GitHub (Dec 6, 2022):

Same on my end

"...apk failed to verify!" :( version 2022.10.1 LineageOS 19 + microG

Same result, with a setup identical to yours.

@catfluoride commented on GitHub (Dec 6, 2022): Same on my end > "...apk failed to verify!" :( version 2022.10.1 LineageOS 19 + microG Same result, with a setup identical to yours.

GiteaMirror commented

@shrimprugbysnowowl commented on GitHub (Dec 6, 2022):

Is this getting any visibility from the devs? Seems significant if there's an issue installing through f-droid that's affecting multiple users?

Does anyone know if an appropriate workaround would be to install the apk hosted here on github? Does it check for updates? Is it free from firebase and MS visual studio analytics like the f-droid version is (vs the one in the play store)?

@shrimprugbysnowowl commented on GitHub (Dec 6, 2022): Is this getting any visibility from the devs? Seems significant if there's an issue installing through f-droid that's affecting multiple users? Does anyone know if an appropriate workaround would be to install the apk hosted here on github? Does it check for updates? Is it free from firebase and MS visual studio analytics like the f-droid version is (vs the one in the play store)?

GiteaMirror commented

@djsmith85 commented on GitHub (Dec 6, 2022):

@jcz1, @catfluoride, @shrimprugbysnowowl Is this still occurring with 2022.11.0 which can be pulled from https://mobileapp.bitwarden.com/fdroid/ ? (Repo info)

Other commenters on this issue, seem to have gotten it working.

@djsmith85 commented on GitHub (Dec 6, 2022): @jcz1, @catfluoride, @shrimprugbysnowowl Is this still occurring with 2022.11.0 which can be pulled from https://mobileapp.bitwarden.com/fdroid/ ? ([Repo info](https://mobileapp.bitwarden.com/fdroid/repo/)) Other commenters on this issue, seem to have gotten it working.

GiteaMirror commented

https://github.com/bitwarden/mobile/releases/tag/v2022.11.0

@mpbw2 commented on GitHub (Dec 6, 2022):

I just installed our latest 2022.11.0 release through F-Droid 1.15.4 without issue.

Does anyone know if an appropriate workaround would be to install the apk hosted here on github?

The F-Droid APK (com.x8bit.bitwarden-fdroid.apk) is the same one installed through F-Droid (free from analytics, etc.):

@mpbw2 commented on GitHub (Dec 6, 2022): I just installed our latest 2022.11.0 release through F-Droid 1.15.4 without issue. > Does anyone know if an appropriate workaround would be to install the apk hosted here on github? The F-Droid APK (`com.x8bit.bitwarden-fdroid.apk`) is the same one installed through F-Droid (free from analytics, etc.): https://github.com/bitwarden/mobile/releases/tag/v2022.11.0

GiteaMirror commented

@shrimprugbysnowowl commented on GitHub (Dec 6, 2022):

@jcz1, @catfluoride, @shrimprugbysnowowl Is this still occurring with 2022.11.0 which can be pulled from https://mobileapp.bitwarden.com/fdroid/ ? (Repo info)

Other commenters on this issue, seem to have gotten it working.

No change for me, also using F-Droid 1.14.1:

Edit: Is there some way to create a log of this error?

@shrimprugbysnowowl commented on GitHub (Dec 6, 2022): > @jcz1, @catfluoride, @shrimprugbysnowowl Is this still occurring with 2022.11.0 which can be pulled from https://mobileapp.bitwarden.com/fdroid/ ? ([Repo info](https://mobileapp.bitwarden.com/fdroid/repo/)) > > Other commenters on this issue, seem to have gotten it working. No change for me, also using F-Droid 1.14.1: ![Screenshot_20221206-104729](https://user-images.githubusercontent.com/59341190/205976227-a6d824d9-ee5d-46bd-bc6d-2131145b26ed.png) Edit: Is there some way to create a log of this error?

GiteaMirror commented

@shrimprugbysnowowl commented on GitHub (Dec 6, 2022):

I just installed our latest 2022.11.0 release through F-Droid 1.15.4 without issue.

Does anyone know if an appropriate workaround would be to install the apk hosted here on github?

The F-Droid APK (com.x8bit.bitwarden-fdroid.apk) is the same one installed through F-Droid (free from analytics, etc.):

https://github.com/bitwarden/mobile/releases/tag/v2022.11.0

Thank you for the info. Confirming that the Bitwarden F-Droid APK does not check github for an updated APK and notify the user, correct?

@shrimprugbysnowowl commented on GitHub (Dec 6, 2022): > I just installed our latest 2022.11.0 release through F-Droid 1.15.4 without issue. > > > Does anyone know if an appropriate workaround would be to install the apk hosted here on github? > > The F-Droid APK (`com.x8bit.bitwarden-fdroid.apk`) is the same one installed through F-Droid (free from analytics, etc.): > > https://github.com/bitwarden/mobile/releases/tag/v2022.11.0 Thank you for the info. Confirming that the Bitwarden F-Droid APK does not check github for an updated APK and notify the user, correct?

GiteaMirror commented

@jcz1 commented on GitHub (Dec 6, 2022):

@jcz1, @catfluoride, @shrimprugbysnowowl Is this still occurring with 2022.11.0 which can be pulled from https://mobileapp.bitwarden.com/fdroid/ ? (Repo info)

It is the same. But i am able to install f-droid apk from github...

@jcz1 commented on GitHub (Dec 6, 2022): > @jcz1, @catfluoride, @shrimprugbysnowowl Is this still occurring with 2022.11.0 which can be pulled from https://mobileapp.bitwarden.com/fdroid/ ? ([Repo info](https://mobileapp.bitwarden.com/fdroid/repo/)) > It is the same. But i am able to install f-droid apk from github...

GiteaMirror commented

@mpbw2 commented on GitHub (Dec 6, 2022):

Thank you for the info. Confirming that the Bitwarden F-Droid APK does not check github for an updated APK and notify the user, correct?

@shrimprugbysnowowl That's correct, there's no version checking built-in to the app itself. However the signing key we use is unique for the F-Droid build so the F-Droid app can still take "ownership" of it and prompt for updates in the future.

@mpbw2 commented on GitHub (Dec 6, 2022): > Thank you for the info. Confirming that the Bitwarden F-Droid APK does not check github for an updated APK and notify the user, correct? @shrimprugbysnowowl That's correct, there's no version checking built-in to the app itself. However the signing key we use is unique for the F-Droid build so the F-Droid app can still take "ownership" of it and prompt for updates in the future.

GiteaMirror commented

@mpbw2 commented on GitHub (Jan 4, 2023):

This may be connected but I'll leave this issue open until the change goes live.

@mpbw2 commented on GitHub (Jan 4, 2023): This may be connected but I'll leave this issue open until the change goes live.

GiteaMirror commented

@cyanide699 commented on GitHub (Jan 11, 2023):

Not sure if related but just had an update prompt for bitwarden on fdroid.... It fails to.install "error installing, failed to verify"

I then manually downloaded the apk from github and installed ok...
Fdroid now nags "fdroid repo index.jar is older than current repo"

Pixel 7 pro (stock)

@cyanide699 commented on GitHub (Jan 11, 2023): Not sure if related but just had an update prompt for bitwarden on fdroid.... It fails to.install "error installing, failed to verify" I then manually downloaded the apk from github and installed ok... Fdroid now nags "fdroid repo index.jar is older than current repo" Pixel 7 pro (stock)

GiteaMirror commented

@mpbw2 commented on GitHub (Jan 11, 2023):

@cyanide699 Looking into this now

@mpbw2 commented on GitHub (Jan 11, 2023): @cyanide699 Looking into this now

GiteaMirror commented

@cyanide699 commented on GitHub (Jan 11, 2023):

@cyanide699 Looking into this now

Thanks .. My bw is running ok after the manual upgrade using the apk from github

But just checked fdroid again "check for updates" and still see the index.jar warning about bw.

It does have some numbers about the index.jar
1670237786←16734297
If that helps

@cyanide699 commented on GitHub (Jan 11, 2023): > @cyanide699 Looking into this now Thanks .. My bw is running ok after the manual upgrade using the apk from github But just checked fdroid again "check for updates" and still see the index.jar warning about bw. It does have some numbers about the index.jar 1670237786←16734297 If that helps

GiteaMirror commented

@mpbw2 commented on GitHub (Jan 11, 2023):

@cyanide699 Should be fixed now (cache problem on our end presented the new apk hash for the old apk resulting in a validation error by the FD client)

@mpbw2 commented on GitHub (Jan 11, 2023): @cyanide699 Should be fixed now (cache problem on our end presented the new apk hash for the old apk resulting in a validation error by the FD client)

GiteaMirror commented

@cyanide699 commented on GitHub (Jan 11, 2023):

@cyanide699 Should be fixed now (cache problem on our end presented the new apk hash for the old apk resulting in a validation error by the FD client)

Seems ok here fdroid check for updates shows no warning now (however i had already manually updated)
Thanks for the update!

@cyanide699 commented on GitHub (Jan 11, 2023): > @cyanide699 Should be fixed now (cache problem on our end presented the new apk hash for the old apk resulting in a validation error by the FD client) Seems ok here fdroid check for updates shows no warning now (however i had already manually updated) Thanks for the update!

GiteaMirror commented

@mpbw2 commented on GitHub (Jan 12, 2023):

I believe there were two separate issues reported in this thread (the first being the cache issue when a new release is pushed, and the second being the improper url). At the moment both of these have been fixed, however you may need to remove and re-add the Bitwarden repo to make sure you're using the fixed url. Can everyone confirm if that fixes the remaining install issues using the F-Droid client? (1.15.x or 1.16-alphax are both working for me now).

@mpbw2 commented on GitHub (Jan 12, 2023): I believe there were two separate issues reported in this thread (the first being the cache issue when a new release is pushed, and the second being the improper url). At the moment both of these have been fixed, however **you may need to remove and re-add the Bitwarden repo to make sure you're using the fixed url**. Can everyone confirm if that fixes the remaining install issues using the F-Droid client? (1.15.x or 1.16-alphax are both working for me now).

GiteaMirror commented

@shrimprugbysnowowl commented on GitHub (Jan 12, 2023):

I believe there were two separate issues reported in this thread (the first being the cache issue when a new release is pushed, and the second being the improper url). At the moment both of these have been fixed, however you may need to remove and re-add the Bitwarden repo to make sure you're using the fixed url. Can everyone confirm if that fixes the remaining install issues using the F-Droid client? (1.15.x or 1.16-alphax are both working for me now).

Correct, these are separate issues.

I re-added the repository in fdroid but I still receive the same error that I posted about originally - "Error installing Bitwarden[.] Failed to install due to an unknown error".

@shrimprugbysnowowl commented on GitHub (Jan 12, 2023): > I believe there were two separate issues reported in this thread (the first being the cache issue when a new release is pushed, and the second being the improper url). At the moment both of these have been fixed, however **you may need to remove and re-add the Bitwarden repo to make sure you're using the fixed url**. Can everyone confirm if that fixes the remaining install issues using the F-Droid client? (1.15.x or 1.16-alphax are both working for me now). Correct, these are separate issues. I re-added the repository in fdroid but I still receive the same error that I posted about originally - "Error installing Bitwarden[.] Failed to install due to an unknown error".

GiteaMirror commented

@mpbw2 commented on GitHub (Jan 12, 2023):

@shrimprugbysnowowl Can you confirm the new repo url ends with /repo? (full url is https://mobileapp.bitwarden.com/fdroid/repo)

@mpbw2 commented on GitHub (Jan 12, 2023): @shrimprugbysnowowl Can you confirm the new repo url ends with `/repo`? (full url is `https://mobileapp.bitwarden.com/fdroid/repo`)

GiteaMirror commented

@shrimprugbysnowowl commented on GitHub (Jan 12, 2023):

Yes, it ends in /repo. I copied the link and fingerprint from Bitwarden's website, and it's https://mobileapp.bitwarden.com/fdroid/repo.

@shrimprugbysnowowl commented on GitHub (Jan 12, 2023): Yes, it ends in ```/repo```. I copied the link and fingerprint from Bitwarden's website, and it's ```https://mobileapp.bitwarden.com/fdroid/repo```.

GiteaMirror commented

@mpbw2 commented on GitHub (Jan 12, 2023):

Okay thanks, looks like this issue will unfortunately remain open until we figure out what's going on (but hopefully remain on topic since the other issues described have been fixed)

@mpbw2 commented on GitHub (Jan 12, 2023): Okay thanks, looks like this issue will unfortunately remain open until we figure out what's going on (but hopefully remain on topic since the other issues described have been fixed)

GiteaMirror commented

@shrimprugbysnowowl commented on GitHub (Feb 14, 2023):

Attempted again but the issue remains. I currently have over 30 other apps installed from f-droid and haven't run into this issue before. Can someone please update as to the status? #2276 has not fixed this issue as the subtitle here might suggest.

@shrimprugbysnowowl commented on GitHub (Feb 14, 2023): Attempted again but the issue remains. I currently have over 30 other apps installed from f-droid and haven't run into this issue before. Can someone please update as to the status? #2276 has not fixed this issue as the subtitle here might suggest.

GiteaMirror commented

@shrimprugbysnowowl commented on GitHub (Aug 9, 2023):

This still occurs with v2023.7.0. I removed the repo, updated repositories, closed f-droid, cleared cache, restarted, re-added Bitwarden repo, updated repos, attempted to install Bitwarden, and the installation failed "due to unknown error". Can anyone provide an update on this aged issue? Is there any reason why the app isn't simply included in f-droid's repo if it doesn't have firebase?

@shrimprugbysnowowl commented on GitHub (Aug 9, 2023): This still occurs with v2023.7.0. I removed the repo, updated repositories, closed f-droid, cleared cache, restarted, re-added Bitwarden repo, updated repos, attempted to install Bitwarden, and the installation failed "due to unknown error". Can anyone provide an update on this aged issue? Is there any reason why the app isn't simply included in f-droid's repo if it doesn't have firebase?

GiteaMirror commented