F-Droid install not working
davebiffuk opened this issue · 17 comments
I installed the app v2.1 from F-Droid and it's not working, I just get "The web page at file:///android_asset/2048/index.html?lang=en could not be loaded because:
net::ERR_FILE_NOT_FOUND"
I see others have reported this and the source fix is to do with git submodule, but that can't be right for the packaged app. Can it?
I uninstalled the F-Droid 2.1 and installed 2.08 from Google Play, and that works fine.
Getting the same error for 2.1. Android 5.1.1. Downgraded to 2.08 F-Droid by completely uninstalling 2.1 and doing a fresh 2.08 install - goodbye high score 😕
Same here on official lineage 15.1 / SM-G900F
Same here. This is what i get:
The webpage at file:///android_asset/2048/index.html?lang=facould not be loaded because:
net::ERR_FILE_NOT_FOUND
I installed the app from F-Droid and my android version is 8.
Same on Pixel 2 (Pie)
Same on Oneplus 3T (Pie)
The size in F-Droid is listed as only 38KiB vs 852KiB for the last release.
I think it broke with ec194a0 it's missing the git submodule @TacoTheDank any ideas?
I'll try to have a look after work today/tomorrow otherwise.
@uberspot Yeah I think that's what the problem is. I'll go and change it back to assets, and then we should tag 2.1.1.
In the mean time, who can issue a kill order to F-Droid. The bad version is still being hosted today (12 days later).
In the mean time, who can issue a kill order to F-Droid. The bad version is still being hosted today (12 days later).
How to do so? @a-raccoon
I just merged @TacoTheDank's fix and pushed a new tag and a new apk to play store. FDroid should also pick this up soon I guess (?)
@ahangarha @a-raccoon I don't think that's possible. The most we can do is just release the new version.
There definitely needs to be a bug filed on https://gitlab.com/fdroid/fdroidclient for an "Emergency Take-down" report and removal system. If not for critical errors, then for malicious apps.
There is a system for removing apps and individual APKs, see the docs:
- Disabled: https://f-droid.org/docs/Build_Metadata_Reference/#Disabled
- disable: https://f-droid.org/docs/Build_Metadata_Reference/#Builds
- ArchivePolicy: https://f-droid.org/docs/Build_Metadata_Reference/#ArchivePolicy
There is also a manual process, but that is probably slower than using the above. Most of the time, the f-droid.org deploy cycle happens every 1-3 days, so using the above metadata fields has a pretty timely response.
I saw the new release on fdroid and it seems to work on my side so I'll close this issue for now. If it happens again, do re-open it.
Yaaassss