release(fdroid): v0.4.3 — fix self-hosted F-Droid publish (v2-only signing)

The self-hosted F-Droid repo (https://dzianisv.github.io/opencode-mobile/fdroid/repo)
has been stuck at v0.4.1 because publish-fdroid crashed in androguard parsing the
CI APK's v2+v3 signature block pair ('NoOverwriteDict' object has no attribute
'append'). Force v1+v2-only signing: gradle flags for local builds, plus a
deterministic apksigner re-sign step in the workflow (expo prebuild regenerates
build.gradle, so the workflow step is the real guarantee). Bump to v0.4.3 /
versionCode 5 so a fresh tag re-runs the publish with the verified bug fixes
(#10 scope fixes, send-error fix) included.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
engineer
2026-06-02 00:58:41 -07:00
parent af351d1df0
commit c66f4fb858
4 changed files with 38 additions and 5 deletions

View File

@@ -94,8 +94,8 @@ android {
applicationId 'cc.agentlabs.opencode'
minSdkVersion rootProject.ext.minSdkVersion
targetSdkVersion rootProject.ext.targetSdkVersion
versionCode 4
versionName "0.4.2"
versionCode 5
versionName "0.4.3"
buildConfigField "String", "REACT_NATIVE_RELEASE_LEVEL", "\"${findProperty('reactNativeReleaseLevel') ?: 'stable'}\""
}
@@ -112,6 +112,16 @@ android {
storePassword System.getenv("RELEASE_STORE_PASSWORD")
keyAlias System.getenv("RELEASE_KEY_ALIAS")
keyPassword System.getenv("RELEASE_KEY_PASSWORD")
// Sign with v1+v2 only. A v2+v3 block pair crashes the androguard
// version fdroidserver uses ("'NoOverwriteDict' object has no
// attribute 'append'"), which broke the self-hosted F-Droid repo
// publish from v0.4.2 on. v1+v2 installs on all supported API levels
// and matches the known-good published APK. Re-enable v3 only once
// fdroidserver/androguard ships the fix.
enableV1Signing true
enableV2Signing true
enableV3Signing false
enableV4Signing false
}
}
}