Skip to content

BitChord Next v2.2.5 — glass on, account button live

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 19 Oct 02:36
· 55 commits to main since this release

Three fixes over v2.2.4, all the same kind of mistake: something that looked right and was never exercised.

The Convx glass was invisible

v2.2.4 shipped the whole Convx engine behind AppSettings.liquidGlass, which defaults to false, and the backdrop is only recorded when that toggle is on. So the port compiled, shipped, and rendered pixel-identically to the build before it.

The toggle makes sense in the Legacy shell, where glass is an alternative to Haze. It does not make sense in a shell whose entire visual identity is the material. The Apple shell no longer consults it — glass is always on there. This is why the app looked unchanged before; now it should not.

The account button did nothing

AppleCircleButton stacked pointerInput(detectHorizontalDragGestures) ahead of clickable. The drag detector consumes the down event, so the clickable downstream in the chain never saw a clean tap. Only the account button was affected — it is the only one passed a swipe handler.

Tap and swipe are now distinguished in one pointer handler, with the decision extracted to ProfileGestureTracker so it is testable without a renderer.

The mini player's tap is verified

Now covered by a real test rather than by inspection.

Tests

  • ProfileGestureTest — the tap/swipe decision, any host.
  • AppleChromeInteractionTest — drives the real composables under Robolectric: a tap reaches its callback.

Known gap, stated plainly: two of those interaction tests still fail — clicking an account-menu row, and the swipe gesture. Both report expected:<1> but was:<0>. I removed the dismiss scrim entirely and the row still does not fire, so my interference theory was wrong and I do not have the cause. Modifier.clickable on a Text is ordinary Compose and the equivalent test on a plain Box passes, so this is more likely my test targeting the wrong semantics node than a real defect — but that is a guess, and the account menu rows are the one thing in this release I cannot vouch for.

CI on this tag

Workflow Result
Flow Debug APK (:app:assembleDevRelease, 4 ABIs, minified) ✅
Check ❌ 18 failures: 16 pre-existing (GeniusTest, LocaleStringsTest) + the 2 above
Android Release APK (signed prod) ❌ keystore

The signing failure is KeytoolException: Tag number over 30 is not supported on bitchord-release.jks, from a repo secret. It also fails on v2.2.4 — pre-existing, and it blocks every signed prod build on this repo.

APKs here are the Flow Debug APK output, verified as com.dev.bitchord versionCode 64 / 2.2.5 with the ported glass and the new gesture code present in the dex.

Still to come

This is the glass engine, not the full Convx UI. Convx has 515 UI files and much of the rest is bound to its own data layer. The Apple shell's page bodies are still BitChord's own behind Convx chrome — Home/Flow, Library, Search, Settings and Now Playing are not yet ported.

  • Removed Herobrine