Hi,
Something seems to be wrong. STF builds fine itself but doesn’t get added to the fdroid build queue anymore since the last build cycles. I wonder why that is the case, the build bot didn’t even notice the latest release at https://github.com/Catfriend1/syncthing-android/releases/tag/v1.2.0.5 during “check_updates”.
Could you please shed some light what has to be done to solve this?
Thanks.
Kind regards
Catfriend1
Not an expert on this but I just checked your build config against mine and you don’t seem to have a repo nor a repo-type in your metadata
I see the repo lines are at line 35, 36. It’s unclear to me because I didn’t change anything recently. Did F-Droid change the yml format in the meantime (last weeks)
DEBUG: Directory: build/com.github.catfriend1.syncthingandroid
DEBUG: > git -c core.askpass=/bin/true -c core.sshCommand=/bin/false -c url.https://.insteadOf=ssh:// -c url.https://u:p@bitbucket.org/.insteadOf=git@bitbucket.org: -c url.https://u:p@bitbucket.org.insteadOf=git://bitbucket.org -c url.https://u:p@bitbucket.org.insteadOf=https://bitbucket.org -c url.https://u:p@github.com/.insteadOf=git@github.com: -c url.https://u:p@github.com.insteadOf=git://github.com -c url.https://u:p@github.com.insteadOf=https://github.com -c url.https://u:p@gitlab.com/.insteadOf=git@gitlab.com: -c url.https://u:p@gitlab.com.insteadOf=git://gitlab.com -c url.https://u:p@gitlab.com.insteadOf=https://gitlab.com fetch --prune --tags origin
DEBUG: Directory: build/com.github.catfriend1.syncthingandroid
DEBUG: > git remote set-head origin --auto
DEBUG: Directory: build/com.github.catfriend1.syncthingandroid
DEBUG: > git checkout -f v1.1.4.1
DEBUG: Directory: build/com.github.catfriend1.syncthingandroid
DEBUG: > git clean -dffx
DEBUG: ...fetch auto name from build/com.github.catfriend1.syncthingandroid
DEBUG: Parsing manifest at 'build/com.github.catfriend1.syncthingandroid/build.gradle'
DEBUG: ..got package=None, version=None, vercode=None
DEBUG: Parsing manifest at 'build/com.github.catfriend1.syncthingandroid/syncthing/build.gradle'
DEBUG: ..got package=None, version=None, vercode=None
DEBUG: Parsing manifest at 'build/com.github.catfriend1.syncthingandroid/app/src/main/AndroidManifest.xml'
DEBUG: ..got package=None, version=None, vercode=None
DEBUG: Parsing manifest at 'build/com.github.catfriend1.syncthingandroid/app/build.gradle'
DEBUG: ..got package=com.github.catfriend1.syncthingandroid, version=1.1.4.1, vercode=1010401
DEBUG: Adding possible subdir app
DEBUG: fetch_real_name: Checking manifest at build/com.github.catfriend1.syncthingandroid/app/src/main/AndroidManifest.xml
ERROR: ...checkupdate failed for com.github.catfriend1.syncthingandroid : EntitiesForbidden(name='folder_ignore_delete_docs_url', system_id=None, public_id=None)
INFO: Finished
Not sure what’s going on…
Reading the log you’ve posted, I suspect the problem comes from the versions.gradle file…
Link: https://github.com/Catfriend1/syncthing-android/blob/master/app/versions.gradle
I followed advice from a StackOverflow user to ease my build script and dependency bump process by letting the static live in build.gradle and having the template to calculate the version number in versions.gradle
You know the fdroidbot can’t parse that and we will disable autoupdate, right? AFAIK at least
Huh… Okay. So is there Something I can do to solve this without having to drop the version number calculation? How does manual version update on the fdroid side work (if that exists)?
You make a new MR for a new version, we build test, then merge.
This will delay updates, I don’t recommend it since now each version will depend on volunteers free time.
Can I point my releases to a branch to build from? Then my scripts could calculate the Versioncode fill it in proper place for fdroid and push a branch+release tag for fdroid.
Can’t use branches either, in automode, IIRC 
Any chance fdroid will be able to parse the build.gradle versioncode calculation in the future :-/?! Its just an include file with pure simple mathematics. E.g. gmscore (microg) does this too.
It’s on a TODO, when checkupdate is run in a VM, it’s a wanted feature we know.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.