Skip to content

fix: keep the check code on the Done screen; make release APKs reproducible on F-Droid - #25

Merged
TheCryptoDonkey merged 2 commits into
mainfrom
fix/check-code-on-done
Sep 26, 2026
Merged

TheCryptoDonkey merged 2 commits into
mainfrom
fix/check-code-on-done

Conversation

@TheCryptoDonkey

Copy link
Copy Markdown
Member

Two small changes for 0.7.1.

  • Check code on Done. The check code no longer disappears once enrolment finishes. It stays labelled on the Done screen with a reminder that it should match the board and Sapwood, and clears when the owner leaves the screen. Protocol, crypto and relay behaviour are unchanged.
  • F-Droid. F-Droid has been stuck on 0.4.3 because its checkupdates build of 0.5.0 failed the reproducible-build comparison. The only difference was META-INF/version-control-info.textproto: NO_VALID_GIT_FOUND in the published APK, which was built from a git worktree, against the commit in F-Droid's clone. vcsInfo.include = false on the release build type removes that file, and a local release build confirms it's gone. 0.5.0 to 0.7.0 can't be fixed after the fact. The next tagged release should pass.

JVM unit tests: 271 passing. Not installed on a phone.

The check code was cleared as soon as finishEnrolment ran, before the
owner had necessarily finished comparing it with Sapwood or the
board's own card. It now stays labelled and visible on the Done
screen, with a reminder of what it should match, until the owner
leaves.
F-Droid's reproducible-build check for 0.5.0 failed on one file: META-INF/version-control-info.textproto recorded NO_VALID_GIT_FOUND in the published APK (built from a worktree) and the commit in F-Droid's clone. Turning vcsInfo off makes both builds match whatever checkout they come from.

Also words the Done screen's check code hint as matching the board and Sapwood, since both show it.
@TheCryptoDonkey
TheCryptoDonkey merged commit fbd0907 into main Sep 26, 2026
2 checks passed
@TheCryptoDonkey
TheCryptoDonkey deleted the fix/check-code-on-done branch September 26, 2026 00:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant