search

fossasia / pslab-android

PSLab Android App https://play.google.com/store/apps/details?id=io.pslab
https://pslab.io
Apache License 2.0
2.04k stars 803 forks source link

Update app on Fdroid #2417

Open mariobehling opened 1 month ago

mariobehling commented 1 month ago

Update app on Fdroid https://f-droid.org/en/packages/io.pslab/

AsCress commented 1 month ago

Thank you for assigning me this issue. I just wanted to ask for a bit of clarification on this. By updating, do you mean releasing a newer version of this on FDroid. Would I be needing any sort of credentials for that ?

CloudyPadmal commented 1 month ago

@AsCress I think most of the details, I have logged here in this blog post https://blog.fossasia.org/publish-an-open-source-app-on-fdroid/

CloudyPadmal commented 1 month ago

and yea it's about making a new release. Please let me know if you encounter any issues. Thanks!

AsCress commented 1 month ago

Thank you very much @CloudyPadmal for all that info and your help!! I am getting this error when I try to run fdroid lint, fdroid rewritemeta or fdroid build: 2024-05-18 14:22:12,002 CRITICAL: '0' is not a valid Archive Policy in org.fossasia.pslab. Regex pattern: ^[0-9]+ versions$ I have been trying to resolve this since quite some time but in vain.

AsCress commented 1 month ago

@CloudyPadmal That issue is resolved. I guess it had something to do with my local installation of Ubuntu. However, when I now run fdroid checkupdates, it doesn't change anything in the io.pslab.yml file, which I guess it would show after we make a new release. fdroid lint and fdroid build are successful. So, we just need to make a new tagged release of the app here, because the latest tagged release is already on FDroid.

CloudyPadmal commented 1 month ago

@AsCress yes we will need to make a version update.

marcnause commented 1 day ago

After some discussion with @AsCress we noticed that there seems to be an issue with F-Droid not being able to process updates due to missing versionCode and versionName values in the build.gradle.kts file (they are set via environment variables at build time now) and F-Droid expects the data being present in the build.gradle(.kts) file or in the manifest.

I have read the F-Droid documentation and there may be ways around this limitation, but I am not sure if I understood everything correctly. Therefore I have requested help: https://gitlab.com/fdroid/fdroiddata/-/issues/3300