F-Droid version being behind
See original GitHub issueTaking this out of #462 as it’s a separate issue. Just putting it on your end first as you brought up the question – and might spot some culprit, before filing an issue with F-Droid.
To track things down, I ran fdroid checkupdates dev.patrickgold.florisboard
manually – which surprisingly stated v0.3.7 would be the up-to-date version (WTF?). So I asked for details, running the same thing again in debug mode (fdroid checkupdates --verbose dev.patrickgold.florisboard
). I don’t post the complete log, rather concentrating on v0.3.9, the current latest release:
2021-03-19 12:43:40,812 DEBUG: Check tag: 'v0.3.9'
2021-03-19 12:43:40,813 DEBUG: Directory: build/dev.patrickgold.florisboard
2021-03-19 12:43:40,813 DEBUG: > git rev-parse --show-toplevel
2021-03-19 12:43:41,038 DEBUG: Directory: build/dev.patrickgold.florisboard
2021-03-19 12:43:41,038 DEBUG: > git submodule foreach --recursive git reset --hard
2021-03-19 12:43:41,157 DEBUG: Directory: build/dev.patrickgold.florisboard
2021-03-19 12:43:41,157 DEBUG: > git submodule foreach --recursive git clean -dffx
2021-03-19 12:43:41,275 DEBUG: Directory: build/dev.patrickgold.florisboard
2021-03-19 12:43:41,275 DEBUG: > git checkout -f v0.3.9
2021-03-19 12:43:41,500 DEBUG: Directory: build/dev.patrickgold.florisboard
2021-03-19 12:43:41,500 DEBUG: > git clean -dffx
2021-03-19 12:43:41,622 DEBUG: Parsing manifest at 'build/dev.patrickgold.florisboard/build.gradle.kts'
2021-03-19 12:43:41,623 DEBUG: ..got package=None, version=None, vercode=None
2021-03-19 12:43:41,626 DEBUG: Parsing manifest at 'build/dev.patrickgold.florisboard/app/src/main/AndroidManifest.xml'
2021-03-19 12:43:41,626 DEBUG: ..got package=dev.patrickgold.florisboard, version=None, vercode=None
2021-03-19 12:43:41,627 DEBUG: Parsing manifest at 'build/dev.patrickgold.florisboard/app/build.gradle.kts'
2021-03-19 12:43:41,628 DEBUG: ..got package=dev.patrickgold.florisboard, version=None, vercode=None
2021-03-19 12:43:41,629 DEBUG: Adding possible subdir app
2021-03-19 12:43:41,629 DEBUG: Parsing manifest at 'build/dev.patrickgold.florisboard/app/src/main/AndroidManifest.xml'
2021-03-19 12:43:41,630 DEBUG: ..got package=dev.patrickgold.florisboard, version=None, vercode=None
2021-03-19 12:43:41,630 DEBUG: Parsing manifest at 'build/dev.patrickgold.florisboard/app/build.gradle.kts'
2021-03-19 12:43:41,631 DEBUG: ..got package=dev.patrickgold.florisboard, version=None, vercode=None
2021-03-19 12:43:41,632 DEBUG: Parsing manifest at 'build/dev.patrickgold.florisboard/app/src/main/AndroidManifest.xml'
2021-03-19 12:43:41,632 DEBUG: ..got package=dev.patrickgold.florisboard, version=None, vercode=None
2021-03-19 12:43:41,633 DEBUG: Adding possible subdir app/src/main
2021-03-19 12:43:41,633 DEBUG: Parsing manifest at 'build/dev.patrickgold.florisboard/app/src/main/AndroidManifest.xml'
2021-03-19 12:43:41,633 DEBUG: ..got package=dev.patrickgold.florisboard, version=None, vercode=None
Now let’s compare that to the output of v0.3.7 – which is the last version auto-update worked for:
2021-03-19 12:43:42,465 DEBUG: Check tag: 'v0.3.7'
2021-03-19 12:43:42,467 DEBUG: Directory: build/dev.patrickgold.florisboard
2021-03-19 12:43:42,467 DEBUG: > git rev-parse --show-toplevel
2021-03-19 12:43:42,688 DEBUG: Directory: build/dev.patrickgold.florisboard
2021-03-19 12:43:42,689 DEBUG: > git submodule foreach --recursive git reset --hard
2021-03-19 12:43:42,809 DEBUG: Directory: build/dev.patrickgold.florisboard
2021-03-19 12:43:42,810 DEBUG: > git submodule foreach --recursive git clean -dffx
2021-03-19 12:43:42,933 DEBUG: Directory: build/dev.patrickgold.florisboard
2021-03-19 12:43:42,933 DEBUG: > git checkout -f v0.3.7
2021-03-19 12:43:43,160 DEBUG: Directory: build/dev.patrickgold.florisboard
2021-03-19 12:43:43,160 DEBUG: > git clean -dffx
2021-03-19 12:43:43,280 DEBUG: Parsing manifest at 'build/dev.patrickgold.florisboard/build.gradle'
2021-03-19 12:43:43,281 DEBUG: ..got package=None, version=None, vercode=None
2021-03-19 12:43:43,283 DEBUG: Parsing manifest at 'build/dev.patrickgold.florisboard/app/src/main/AndroidManifest.xml'
2021-03-19 12:43:43,284 DEBUG: ..got package=dev.patrickgold.florisboard, version=None, vercode=None
2021-03-19 12:43:43,284 DEBUG: Parsing manifest at 'build/dev.patrickgold.florisboard/app/build.gradle'
2021-03-19 12:43:43,285 DEBUG: Adding possible subdir app
2021-03-19 12:43:43,286 DEBUG: Parsing manifest at 'build/dev.patrickgold.florisboard/app/src/main/AndroidManifest.xml'
2021-03-19 12:43:43,286 DEBUG: ..got package=dev.patrickgold.florisboard, version=None, vercode=None
2021-03-19 12:43:43,286 DEBUG: Parsing manifest at 'build/dev.patrickgold.florisboard/app/build.gradle'
2021-03-19 12:43:43,287 DEBUG: Manifest exists in subdir 'app'. Found version 0.3.7 (26)
2021-03-19 12:43:43,288 DEBUG: Parsing manifest at 'build/dev.patrickgold.florisboard/app/src/main/AndroidManifest.xml'
2021-03-19 12:43:43,289 DEBUG: ..got package=dev.patrickgold.florisboard, version=None, vercode=None
2021-03-19 12:43:43,289 DEBUG: Adding possible subdir app/src/main
2021-03-19 12:43:43,289 DEBUG: Parsing manifest at 'build/dev.patrickgold.florisboard/app/src/main/AndroidManifest.xml'
2021-03-19 12:43:43,290 DEBUG: ..got package=dev.patrickgold.florisboard, version=None, vercode=None
The difference I see: with v0.3.8, you switched from build.gradle
to build.gradle.kts
(Kotlin variant) – before that, checkupdates
was able to find versionName
and versionCode
, after that change no longer. Why?
defaultConfig {
applicationId = "dev.patrickgold.florisboard"
minSdkVersion(23)
targetSdkVersion(30)
versionCode(29)
versionName("0.3.10")
testInstrumentationRunner = "androidx.test.runner.AndroidJUnitRunner"
}
defaultConfig {
applicationId "dev.patrickgold.florisboard"
minSdkVersion 23
targetSdkVersion 29
versionCode 26
versionName "0.3.7"
testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
}
The Kotlin variant has a different syntax, introducing parenthesis.
F-Droid team is already investigating (I’ve just asked in our dev chat, and got an immediate response; provided the relevant lines from above, and one of our developers is already hunting it down). Still leaving this issue with you in case of other users wonder, so you can point them here 😉
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:14 (12 by maintainers)
Top GitHub Comments
Update is on its way.
Fix is on its way (reference). Take a look at the test case there 😄