Skip to content

v0.7.1

Choose a tag to compare

@github-actions github-actions released this 15 Aug 03:06
· 95 commits to main since this release
63f7fa1

A privacy-focused point release: one thing the app was doing that its own settings screen denied, and one thing it could not do at all.

Turning on crash reports no longer turns on analytics

The consent toggle is described everywhere — in the setting itself, in the README, in the security policy — as stack traces only. It also switched on Firebase Analytics collection, quietly adding automatic events to what an opted-in install sent. The app has never logged an analytics event of its own, so that collection bought nothing and contradicted the toggle's own description.

Consent now enables Crashlytics and only Crashlytics, and the Analytics SDK is not shipped at all. The measured effect: the full build declares 13 permissions instead of 17AD_ID, both ACCESS_ADSERVICES_* and BIND_GET_INSTALL_REFERRER_SERVICE are gone. What a crash report can contain is unchanged.

If you had opted in on an earlier build, updating stops the collection you never asked for. There is nothing for you to do.

Report a response you think is wrong

Long-press a message the agent produced and pick Report response: choose a category, add a note, then either copy the report or open a prefilled issue. Nothing is transmitted on its own — there is no reporting server behind this app, and adding one would contradict everything else it claims. The dialog says so, and warns that the tracker is public before you submit anything.

A standalone privacy policy

PRIVACY.md now documents in one place what stays on the device, every path that can send data off it, what never leaves at all, and why each permission is requested. The About screen links to it, so the app, the README and any store listing answer with one document instead of three.

Also in this release

  • Store listing texts, screenshots and graphics moved into the repository under fastlane/metadata/android/, guarded by a test that enforces what the stores actually reject.
  • Two builds of the same commit now carry the same build date — groundwork for a release you can reproduce from source and check against the published artefact.

Upgrading

Same signing key as 0.7.0, so this updates in place. Coming from 0.6.0 or earlier still needs an uninstall first — those builds were debug-signed.

Which file

  • knotwork-0.7.1-full-release.apk — the normal build, for sideloading.
  • knotwork-0.7.1-foss-release.apk — no Google or Firebase dependency anywhere in the graph, and no crash reporting at all.
  • knotwork-0.7.1-full-release.aab — store upload format; not installable directly.

Checksums are in SHA256SUMS.txt. Requires Android 16 (API 36) and roughly 2 GB of free RAM for the model.

Full detail: the 0.7.1 section of the changelog.