[Repo] : Metadata - Create process to update/upgrade an app

Hi all,

I’m new on this project.

My goal is having repo to update/upgrade element application.

I have follow this guide within step 10. : https://f-droid.org/en/docs/Setup_an_F-Droid_App_Repo/

My webserver nginx give access to fdroidserver/repo.

On debian bullseye, my building/deploying process is the following :

1 - git clone the project
2 - build with android-studio
3 - send apk to fdroidserver/repo/
4 - fdroid update

With one APK on the folder, it’s easy.

  • If i build APK from the next branch project, i will have this same name,

output-metadata.json
vector-gplay-arm64-v8a-release.apk
vector-gplay-armeabi-v7a-release.apk
vector-gplay-universal-release.apk
vector-gplay-x86_64-release.apk
vector-gplay-x86-release.apk

So, How can i note the next build for APKs ? With prefix or suffix ?

  • Now, i’m asking what is the good syntaxe of metadata for fdroidserver ?

I only have output-metadata.json

When i have done “fdroid update”, it was mentioned “no metadata available …”

So i have done fdroid update -c and this skeleton was gived to me.

What can i write in this fields ?

Thanks a lot.

metadata example: https://gitlab.com/fdroid/fdroiddata/-/blob/master/metadata/im.vector.app.yml

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.