NoteType (TEXT / TASK_LIST / SHOPPING_LIST) persists in an additive
NoteEntity.typeKey column (ObjectBox auto-migrates; old rows = TEXT).
List bodies stay GitHub-flavoured '- [ ]' lines so search, field
encryption, backups (defaulted noteType) and Trash keep working.
Editor: checklist + basket buttons convert any note; rows are uniform
underlined line fields (13sp) - product, 'Quan.' quantity (defaults to
1 on blur), and POS-style price showing raw cents while focused and
$1.23 on focus loss. Sticky total bar sums qty x price of checked
rows in integer cents via an explicit {q.. p..} end-of-line marker so
product text is never scanned for numbers.
Fixes found in device testing: cards rendered raw markdown for list
notes stranded as TEXT by partial builds - read-time Note.inferListType
now heals them; quantity field was clipped invisible (64dp vs the 48dp
icon target) - replaced by the free-text line; the serializer emitted
a bare 'q' slot (broken '{q p1.23}' markers, stray ' x' folds) - now
null-when-default. Add-tag suggestions rebuilt on flatMapLatest so the
autocomplete re-queries per keystroke.
versionCode 32->33, versionName 0.3.8.0, APP_VERSION in lockstep.
Per-version user-facing changelog moved out of the README table into
PREVIOUS_HISTORY.md (newest-first sections, Development Plan §11.1).
On tag push the workflow now harvests the matching section via
scripts/ci/release-notes.py and uses it as the release description,
uploading an Incido-<version>-changes.md beside the APKs; a missing
section falls back to the plain default description. CONTRIBUTING §5
documents the new release-notes maintenance step.
The build step minted a fresh keystore inside the checkout on every
run, so each CI release was signed with a different key. Upgrading
from any previous release then failed with a signature conflict
(INSTALL_FAILED_UPDATE_INCOMPATIBLE) — and with allowBackup=false,
the only workaround was uninstalling, which destroys the user's
notes.
The keystore is now minted once in /tmp/gitea-runner-work (the same
persistent cache that already holds the JDK and Android SDK) and
copied into the checkout before building. Every release from now on
shares one signing key, so in-place upgrades work. Only a runner-host
rebuild would mint a new key (breaking exactly one upgrade).
Note: v0.3.7.0 was signed with an ephemeral key that no longer
exists, so the v0.3.7.0 -> v0.3.7.1 upgrade still requires a one-time
uninstall (export a backup first).
The v0.3.7.1 release run failed in the attach step: the 28.7 MB debug
APK upload took ~126s through the Cloudflare proxy, which returned
"error code: 524" (origin timeout, ~100s limit). The step then crashed
parsing the non-JSON error page as JSON, and the release APK was never
attempted — leaving release 36 with zero assets.
upload_asset() now:
- retries with --retry-all-errors so HTTP error responses (524) are
retried, not just connection failures;
- verifies success server-side by listing the release assets after
each attempt (a 524 often means the origin saved the file before
Cloudflare gave up, so the response body is not trusted);
- only fails after 5 attempts with the asset still missing.
Maintenance release.
UI polish:
- Editor top bar decluttered: camera / attach-file / add-tag moved out of
the title bar into a Keep-style bottom action row, so the title and
remaining buttons (favourite, save, overflow) always fit, even on
narrow screens. Title is now "New note" / "Edit note" with ellipsis.
- Search auto-focuses when opened and shows a clear button while typing.
- Long tag lists in the navigation drawer now scroll within the sheet
instead of overflowing the bottom (weight(1f) on the scroll column).
- Add-tag sheet opens with the keyboard already up.
Bug fix:
- Image viewer no longer flashes a false "couldn't decode" error on
every persisted image open (the old LaunchedEffect checked the bitmap
before the async load finished); genuine failures now show
"Couldn't load image" in place of "Loading…".
New flat app icon:
- incido_flat_icon.png replaces the v0.3.3.8 artwork: adaptive
foregrounds (108-432px) + legacy mipmaps (48-192px) regenerated;
ic_launcher_background re-tinted #010435 -> #352999 to match.
Hygiene:
- Unused persistedBytes param dropped from AttachmentStrip; redundant
repoForViewer alias and dead _ignored val removed; fully-qualified
Spacer/Image/Column/Dispatchers references replaced with imports.
versionCode 31->32, versionName "0.3.7.0"->"0.3.7.1",
SettingsViewModel.APP_VERSION bumped in lockstep.
- Deleting a note now soft-deletes it (trashed flag on NoteEntity,
additive schema, auto-migrated); trashed notes are hidden from Home,
Favorites, Untagged, tag views, and ordinary search.
- New Trash drawer entry lists soft-deleted notes; each Trash card's
overflow menu exposes Restore and Delete permanently.
- NoteFilter gains a Trash case; repository gains moveToTrash /
restoreFromTrash / deletePermanently; backups round-trip the
trashed state.
- Version bump (lockstep): versionCode 30->31, versionName
0.3.6.3->0.3.7.0, SettingsViewModel.APP_VERSION, README intro +
changelog, ReleaseNotes.kt 5-most-recent window.
- Development Plan §10: fix the merged 0.3.4.0/0.3.3.8 table row and
backfill the missing 0.3.6.2/0.3.6.3 rows; add the 0.3.7.0 row.
- README changelog: backfill the missing 0.3.6.2 row; promote the
Unreleased Trash row to 0.3.7.0.
- signingConfigs.release now throws GradleException at config time
when keystore/release.jks is missing, printing the exact keytool
command from keystore/README.md instead of letting packageRelease
die later with the cryptic
"SigningConfig release is missing required property storeFile".
- .gitea/workflows/release.yml now mints the dev keystore on the
runner before assembleRelease (previously the signing config
was empty on a fresh runner, so the release APK was never
produced).
- versionCode 29 → 30, versionName "0.3.6.2" → "0.3.6.3";
APP_VERSION in SettingsViewModel bumped in lockstep; README
"Current release" + intro paragraph + Changelog row updated.
Refs: Incido Development Plan §11.
Two emergency-patch UX fixes on the New/Edit screen:
1. Title left-aligned against the back arrow.
NoteEditorScreen used CenterAlignedTopAppBar, but with six
actions on the right (camera, attach, tag, favourite, save, more)
the visually-centred title landed right next to the action cluster.
Swap for Material 3's standard TopAppBar so 'New' / 'Edit' sits
flush right of the back arrow on the left.
2. Colour chooser is now equally spaced between the title bar
and the top of the note. The picker Row had padding(vertical = 4.dp)
(4dp above + 4dp below), but the OutlinedTextField below has an
intrinsic top inset (~16dp) inside its border, so the perceived
gap from the picker to the first line of the note dwarfed the
gap from the title bar's bottom to the picker's top. Remove the
vertical = 4.dp and bracket the Row with two explicit
Spacer(Modifier.height(12.dp)) siblings so the picker sits 12dp
from the title bar AND 12dp from the field's top border.
versionCode 27 → 28
versionName 0.3.6.0 → 0.3.6.1
APP_VERSION 0.3.6.0 → 0.3.6.1