F-Droid fails on `DEBUG_KEYSTORE`

[gouri-panda]

trafficstars

Describe the bug The F-Droid nightly action doesn't recognize the DEBUG_KEYSTORE value. Please look at #3079 . It gives the following error although we set the DEBUG_KEYSTORE properly.

ERROR: DEBUG_KEYSTORE is not set or the value is incomplete

Expected behavior Pass the F-Droid nightly jobs.

[kelson42]

@licaon-kter Maybe you can help us to understand why our fdroid-nightly builds are not published?

[licaon-kter]

Not my area of expertise unfortunately

@eighthave ?

[eighthave]

Looks like an error in your GitHub Actions setup: https://github.com/kiwix/kiwix-android/actions/runs/3038848761/jobs/4893145316

I don't really know much about GitHub Actions.

[gouri-panda]

@eighthave Thanks for looking into it. Sorry it was #3079 .

[eighthave]

If you want to use the wardvl setup, you should ask him. This is what I got working: https://f-droid.org/docs/Publishing_Nightly_Builds/#configuring-for-github-actions

[gouri-panda]

@eighthave We have tried that also :). Our last attempt was wardvl. I think the error is in our end.

[eighthave]

If you post a log of a job with the f-droid.org setup, I can take a look. it is most likely something in your GitHub settings inkiwix/kiwix-android.

[gouri-panda]

@eighthave Thanks for your time :). Here are the logs logs_8759.zip . Let me know if you need anything.

[eighthave]

If you look at Publish nightly build/5_fdroid nightly.txt, it looks like DEBUG_KEYSTORE is unset or blank:

2022-09-19T21:01:53.7573178Z shell: /usr/bin/bash -e {0}
2022-09-19T21:01:53.7573793Z env:
2022-09-19T21:01:53.7574136Z   JAVA_HOME: /opt/hostedtoolcache/Java_Adopt_jdk/11.0.16-101/x64
2022-09-19T21:01:53.7574480Z   DEBUG_KEYSTORE: 

Try this step again:

In the Settings of the project being built, find “Actions” under “Secrets” in the “Security” section. Paste the whole DEBUG_KEYSTORE output line into a new repository secret called DEBUG_KEYSTORE, e.g. https://github.com/kiwix/kiwix-android/settings/secrets/actions.

[gouri-panda]

@eighthave We have already set the DEBUG_KEYSTORE in our actions. Previously we set this export DEBUG_KEYSTORE=${{ secrets.DEBUG_KEYSTORE }} but the output was "" and the error was this

ERROR: DEBUG_KEYSTORE is not set or the value is incomplete

I have a doubt in my mind does the DEBUG_KEYSTORE have to be from organisation? I generated the DEBUG_KEYSTORE from my local PC.