Question about updating app

I have updated my app and am following documentation to make this update available to F-Droid users. I’ve confirmed that the updates I’ve pushed to my GitHub repo have been detected by examining the metadata for my app in F-Droid/Data as described in the Detecting section of the documentation linked above.

I notice when checking for updates via the F-Droid app that the newest version is not available. I am seeking clarification about the Adding section of the documentation linked above:

For applications built from source, it is necessary to add a new Build Version line to the metadata file. At the very least, the version name, version code and commit will be different. It is also possible that the additional build flags will change between versions.

Examining the current metadata for my app, I notice that the newest Build Version is included in the file:

Builds:
  • versionName: ‘2.1’
    versionCode: 2
    commit: f2643faaa7273aaf401bc3d424c42e241efa47c3
    subdir: app
    sudo:

    • apt-get update || apt-get update
    • apt-get install -y openjdk-11-jdk-headless
    • update-alternatives --auto java
      gradle:
    • yes
  • versionName: ‘2.2’
    versionCode: 3
    commit: 817f2c72d02a16eb664558bdb077aad1cd3d841b
    subdir: app
    sudo:

    • apt-get update || apt-get update
    • apt-get install -y openjdk-11-jdk-headless
    • update-alternatives --auto java
      gradle:
    • yes

I’ve searched the documentation describing build metadata and there is no entry for Build Version so I assume the versionName entry and nested text satisfies this? But then why is my update not appearing in the F-Droid app?

Another question on the following:

Adding updates (i.e. new versions of applications already included in the repository) happens in two ways. The simple case is applications where the APK files are binaries, retrieved from a developer’s published build. In this case, all that’s required is to place the new binary in the Repo directory, and the next run of fdroid update will pick it up.

Does this mean that if I updated APK file as a release on my GitHub repo that the update should occur automatically? Or is it necessary to include the APK file in the repository root directory? Shouldn’t all APK files be considered binaries?

Thanks in advance for your help.

Then it should just be a waiting game.

The intended way to read that is “A new entry needs to be added to the Builds list”

Most likely the build cycle it’s in just hasn’t been signed and released yet. It is also possible the build failed. What app is this about? running - F-Droid Monitor should list it if it’s part of the current build cycle.

This is about if you run your own F-Droid Server. We always build from source, so having a APK file anywhere doesn’t matter (unless you opted in for reproducible builds, then it’s required).

1 Like

Thanks for providing such an informative answer. I see my app built successfully a little more than 24 hours ago. I will wait for it to appear soon.

1 Like