AstroMatrix · Flutter · 2026-10-17 · nothing pushed

What a maintenance release would change, platform by platform

This compares the live 11.1.7 builds with two local release candidates, commit by commit, including dependency changes. Both candidates exist only on this machine.

What the live builds were built from: still unconfirmed

Correction An earlier version of this page said live 11.1.7 was built from d89c1fc1 or 70a08d0a. That's withdrawn. The "real customers on build 98 by 10-13 14:00 UTC" signal came from the error log's platform field, which reports iOS and Android for the web build when it runs in a phone browser, and from test accounts. The first native build-98 customers actually appear on 10-15.

iOS 11.1.7 (App Store Connect): version created 10-13 13:24 UTC, build uploaded 14:21 UTC on the builder's machine. It cannot contain 3423e5a2/be0ccb87 (authored 15:22 and 15:43). It may contain the builder's own UI commits authored 12:39–13:02, and 1823371b (13:46).
Android 11.1.7: upload time unknown, so its source is unknown. It could even include the crash patches.
Also on App Store Connect: "11.1.7 (300100099)" is approved and waiting for a manual Release press. Build 99 contains the FEATURE-11 Daily work and the held startup change. Build 300100101 (11.1.8) is uploaded.

Why it matters for A vs B: if iOS 11.1.7 already has the builder's UI commits, Candidate B (based on 70a08d0a) would remove them from iPhones, a visible regression. B's base has to be set from the builder's answer, not from inference.

The two candidates

A · `hotfix/11.1.7-rb1-candidate`

Base 3423e5a2 · 23 commits on top of it

All approved fixes, plus nine of usmanali's UI commits that have never shipped (layout gutters, gradient fills, Friends in search, crystal tiles, journal aspect chip, Matrix detail-view default, a test, profile edits hold). They're included only because of the base it starts from.
0 analyzer errors 3,895 / 3,895 tests Android build

B · `hotfix/11.1.7-minimal-candidate`

Base 70a08d0a · 15 commits on top of it (base still to be confirmed against the live builds)

Only the approved fixes, plus the two plugin-patch commits that the checkout fix depends on. No Daily, FEATURE-11/26 or unshipped UI work.
0 analyzer errors 3,888 / 3,888 tests Android build unsigned iOS build

Candidate B, per platform

Commit	Change	Android	iOS	Verified so far	Still needed before rollout
Payments and native (higher risk)
`3423e5a2` `be0ccb87`	Patched copies of firebase_messaging 16.0.2 and in_app_purchase_android 0.5.0 replace the hosted packages (ISSUE-282/283 crashes)	yes: native Java/Kotlin patches	path change only; iOS code byte-identical to pub.dev	Diffed against the pub.dev originals: only the marked Android files differ. Guard test in the suite.	Android crash-rate check after a staged rollout
`26b62c73`	Android checkout: one launch per tap, fresh product details, BillingClient reconnect (ISSUE-696/697/699)	yes	purchase-funnel logging and the one-launch break only	Unit tests	Sandbox purchase on Android: duplicate tap, stale offer, backgrounded app. Depends on the vendored IAP plugin above.
`96f4d84d` `1bfd6b68` `b8ef6a9a` `e40b04e3`	iOS widgets: planetary hours, chart-location offset (ISSUE-385); Podfile.lock sync	no (ios/ only)	yes: Swift + project file	Unsigned iOS build compiles with the extensions	iPhone check: widget hour matches the app. The Podfile.lock drops three pods already removed from pubspec before 11.1.7.
Dart-only fixes (all platforms)
`ea6c1c1f` `5ea6ac03`	A refused journal edit says it failed (ISSUE-392), plus a test recording that queued edits later refused still show as saved	yes	yes	Unit tests	Device: a refused edit shows "Failed"
`4ec90fc9`	Back from a chart opened inside a detail screen (ISSUE-420)	yes	yes	Emulator: 5 back paths	One Samsung / One UI check
`dd78087a`*	Moon transits kept outside the self matrix (ISSUE-688)	yes	yes	Unit test on new-ui (*the code half only on B; its test file postdates the base)	Relationship matrix lists Moon transits
`d69e9c99`	Support chat: 5-line box with Return key; replies copyable (ISSUE-733/43)	yes	yes	Tests; emulator: newline, scroll, Copy	One iOS keyboard check
`269a0704`	Support option can't be double-sent while in flight (ISSUE-331)	yes	yes	Tests (not tapped live, to avoid posting to the production support inbox)	Device check with a test thread, or watch the repeat-tap count after release
`7faf3530`	Solar/Lunar Return panel labels (ISSUE-662)	yes	yes	Tests; emulator: Lunar Return panel	none
`87a229cd`	Tarot cards labelled for screen readers (ISSUE-725)	yes	yes	Widget tests	VoiceOver pass on iPhone

This table lists what B adds on top of its own base. What it adds relative to each live build depends on the builder's answer above.

Decisions before a push

Which commit was each 11.1.7 binary built from, iOS and Android separately? Ask the developer who built them. That answer sets Candidate B's base. If his UI commits are live, B must start from his commit, not 70a08d0a, or it will roll them back.
The approved "11.1.7 (300100099)" on App Store Connect will ship the Daily work and the startup change to iPhones as soon as someone presses Release. Agree who holds it.
Store numbering: Play needs a build number above 300100101. On iOS, 11.1.7 is released and 11.1.8 already has a build uploaded, so the maintenance release's version string has to be agreed.
A or B. B is the minimal one. A also ships nine unreviewed UI commits, including 1823371b, the likely fix for profile edits not sticking (ISSUE-692). If that fix is wanted, add it to B on purpose rather than taking all nine.
Platform verification from the table: Android checkout in a sandbox, the iOS widget, VoiceOver, plus the smaller device checks.
A separate branch exists. Another session created a local release/11.1.8-panel today: 11.1.8 plus the FEATURE-26 Daily panel, and none of these fixes. That overlaps the "hold 11.1.8" and "keep Daily separate" decisions.