bitwarden / android

Bitwarden mobile app for Android.
https://bitwarden.com
GNU General Public License v3.0
6.33k stars 797 forks source link

Is FDroid Repo down? Url gives 404 #3333

Closed ppittle closed 3 months ago

ppittle commented 3 months ago

Steps To Reproduce

  1. Navigate to https://mobileapp.bitwarden.com/fdroid/repo
  2. Receive 404

image

Expected Result

200

Actual Result

404

Screenshots or Videos

No response

Additional Context

No response

Build Version

n/a

Environment Details

No response

Issue Tracking Info

SkewedZeppelin commented 3 months ago

It looks like it was done on purpose https://github.com/bitwarden/android/commit/80ff991da66d48f80d84c2618e34550a9f7bd67e

If you really want to add it still use https://raw.githubusercontent.com/bitwarden/android/gh-pages/fdroid/repo

But they're probably just migrating to another server or something.

ppittle commented 3 months ago

That looks like a breaking change :p

vvolkgang commented 3 months ago

Thank you for the report! This was an unintentional side effect of the new bitwarden/mobile repo migration, we're working to get this page back up.

vvolkgang commented 3 months ago

Should be working now!

https://mobileapp.bitwarden.com/fdroid/

cwchristerw commented 3 months ago

It works 🥳

ppittle commented 3 months ago

Should be working now!

https://mobileapp.bitwarden.com/fdroid/

Confirmed!

For your consideration, when the link was down yesterday, I checked the Bitwarden Status page for more information, but everything was green, and no mention of fdroid. Would have been nice to see a monitor for the fdroid repo url.

terminatorbs commented 3 months ago

I know this is a closed issue, but today i tried downloading the app from https://bitwarden.com/download/#downloads-mobile and got an error when scanning the QR code. the link by ppittle above (https://mobileapp.bitwarden.com/fdroid/) worked for me.

I don't know if it's my fdroid that had issues with the first code or if it actually is different, but if i'm not the only one encountering this, i'd suggest updating the QR on the first page i mentioned too, as for me that was the page i naturally ended up when looking where to get the app.