-
Notifications
You must be signed in to change notification settings - Fork 48
Publish to F-Droid Repo #136
Comments
Thank you @grantwest, |
@raphBTC meanwhile, maybe you could attach the (signed) APK to releases? |
Hey @IzzySoft, |
Thanks @raphBTC! Just added it to my repo ("Staging" for F-Droid), should turn up here with the next sync in about 22h (sorry I didn't make it for the last one 2h ago, but I just returned from work). For F-Droid, it would then be nice if you could establish Fastlane file structure in your repo. My scanner says it looks good to go to f-droid.org – but "their" scanner might find something to oppose that (hopefully not, but I cannot tell for sure – I'm no dev). If you need help with the listing there, let me know; I'm one of the maintainers. |
@IzzySoft Thanks for that. What's the status of its incorporation into the main f-droid repo? Here's the QR for his f-droid repo: I get a "zapsolutions.zap_3027.apk failed to verify!" error when trying to install from within f-droid. |
@Geremia I don't know the status for each of the 4k apps at F-Droid – and whether which new app was already requested (RFP), has a merge request open, or is already in the build process 😉 But that can be checked in the corresponding repos if you wish. I don't know about that verification error either: the APK in my repo is properly signed. Maybe you had a modified version of the app installed before, that came with a different signature? In that case you'll need to uninstall that first. |
@IzzySoft Your most recent APK has a valid signature, but your most recent APK isn't in your repo. |
@Geremia say what? https://apt.izzysoft.de/fdroid/index/apk/zapsolutions.zap lists the very same file as latest APK, and clicking the link I get the very same APK (I just verified). Besides, you couldn't get a "failed to verify" error on a non-existing file. |
+1 on this, having Zap on F-Droid would be positive. |
Bump. Though I don't use bitcoin, we need more Foss, reproducible wallets in f droid proper |
Publish to F-Droid Repo
Description
In order to make it easy for non-google Android users to install and keep the app up to date, zap-android should be published to the f-droid.org repo.
The guidelines for being included into f-droid are here: https://f-droid.org/en/docs/Inclusion_Policy/
I believe zap-android meets all the requirements, but someone else should review and confirm.
The process for getting an app published to f-droid is outlined here: https://f-droid.org/en/docs/Inclusion_How-To/
The text was updated successfully, but these errors were encountered: