|
| 1 | +<!-- SPDX-License-Identifier: MIT --> |
| 2 | +<!-- Part of PyBLE (https://pyble.dev) — see /LICENSE. --> |
| 3 | + |
| 4 | +# App 0.3.0 (9) — release readiness and channel handoff |
| 5 | + |
| 6 | +| Field | Record | |
| 7 | +|---|---| |
| 8 | +| Date | 31 October 2026, Asia/Bangkok | |
| 9 | +| Scope | App-only bounded current-text recovery; existing Play open-testing and TestFlight channels | |
| 10 | +| Source | Merged PR #40 at `6f5b3ea73a70342331fb49d0685938ce2a4cae11`; app tree `b12fe3621f1d100a3b3724d15ee0dea3b359acfe` | |
| 11 | +| State | Production Android and iOS packaging verified for this source; physical acceptance and final release admission remain outstanding. The physical-device follow-up identified a keyboard-layout issue being repaired separately, so these pre-fix artifacts are provisional and must be rebuilt after that change | |
| 12 | +| Local evidence | Ignored `local/recovery-completion/release/`: build/check logs, artifact manifest and retained signed binaries | |
| 13 | +| Public copy | [Prepared release packet](../../../publication/app-0.3.0-build-9-release-packet.md); no submission or availability claim | |
| 14 | + |
| 15 | +## Gate selection |
| 16 | + |
| 17 | +This increment changes the app, not the firmware bytes. The |
| 18 | +[qualification inventory](../c1-s1/04_Validation_Inventory_and_Operator_Recipe.md#1-evidence-and-gate-selection) |
| 19 | +requires affected app workflows on the five existing exact profiles and both |
| 20 | +platforms for that compatibility claim. An unchanged firmware is a named input |
| 21 | +with its own historical qualification limits. This work does not require or |
| 22 | +claim a new firmware release, fresh firmware OI-1 qualification or a Ready badge. |
| 23 | + |
| 24 | +| Gate | Required evidence | Current disposition | |
| 25 | +|---|---|---| |
| 26 | +| M-02 recovery acceptance | All DR-T01–14 required evidence, including representative physical generated-text recovery and both platform offline/current-board-consent records | Reconcile against the [execution record](00_Execution_Record.md) and actual device reports; installation/scan alone is insufficient | |
| 27 | +| App regression | Accepted source contract, red/green history, locked dependencies, ordinary tests, pinned goldens, platform builds and repository gates | PR #40 and its post-merge CI passed; 972 ordinary Flutter tests recorded; rerun affected checks for any further code change | |
| 28 | +| Five-profile app compatibility | Q01–Q10 below with exact app/firmware identity, actual observations and retained failures | Final complete candidate-bound matrix not yet established | |
| 29 | +| Production packaging | Android upload signer/AAB/APK/native alignment; iOS distribution export/IPA validation; capability parity | Android and iOS checks below pass for the recorded source; affected checks must follow a repaired candidate | |
| 30 | +| Release review | Frozen artifact identity, resolved mandatory failures, supported scope, privacy/dependency review and recorded acceptance | Not yet admitted | |
| 31 | +| M-05 channel delivery | Actual upload/processing/review/availability, followed by store-delivered installed identity and upgrade/launch checks | No upload or new channel delivery established by this preparation | |
| 32 | + |
| 33 | +Pilot participation and useful-return evidence remain separate from maintenance |
| 34 | +release admission. A second operator is required for the optional reproduction |
| 35 | +claim, not for an unrelated app release. Neither distinction waives mandatory |
| 36 | +physical or packaging evidence. |
| 37 | + |
| 38 | +## Required app compatibility rows |
| 39 | + |
| 40 | +| iPad row | Android row | Exact profile | App checks | |
| 41 | +|---|---|---|---| |
| 42 | +| Q01 | Q02 | `esp32-4mb` | Common workflow plus affected recovery | |
| 43 | +| Q03 | Q04 | `esp32-s3-n16r8` | Common workflow plus affected recovery; do not infer the profile from the `esp32-s3` chip string alone | |
| 44 | +| Q05 | Q06 | `waveshare-esp32-s3-lcd-147b` | Common workflow plus affected recovery; keep its exact-board/image identity distinct from generic S3 | |
| 45 | +| Q07 | Q08 | `esp32-c3-4mb` | Common workflow plus affected recovery and the real-app C3-G5 behavior | |
| 46 | +| Q09 | Q10 | `rpi-pico2-w` | Common workflow plus affected recovery on each physical platform; no new full GP2 qualification inferred | |
| 47 | + |
| 48 | +Each common row includes ordinary service-filtered discovery/HELLO, editing and |
| 49 | +saving a harmless file, Run/stdout/terminal state, Stop, exact file readback, |
| 50 | +disconnect/reconnect and workspace continuity. Retain the selected candidate's |
| 51 | +affected lifecycle/recovery scenarios. Record the actual result of every row; |
| 52 | +a scan result or one platform cannot stand in for another row. |
| 53 | + |
| 54 | +[C3-G5](../../../specifications/firmware/ports/esp32-c3-4mb.md#c3-g5--real-app-hil-on-both-platforms-frozen) |
| 55 | +requires Stop through the real UI against both a tight loop and print flood. |
| 56 | +Its C3-G2 oracle is exactly one matching `RSP{OK}` before `RUN_STATE(idle)` in |
| 57 | +less than 500 ms from complete STOP submission, a usable connection, and a |
| 58 | +subsequent bounded run. UI responsiveness alone cannot establish that wire |
| 59 | +latency. There is no new arbitrary repetition count added by this app increment. |
| 60 | + |
| 61 | +## Prepared Android production artifacts |
| 62 | + |
| 63 | +Both builds use normal `lib/main.dart`, production flavor and the established |
| 64 | +owner upload key. Secret values were obtained from the existing local secret |
| 65 | +manager and never written into source or logs. |
| 66 | + |
| 67 | +| Artifact | SHA-256 | Bytes | |
| 68 | +|---|---|---:| |
| 69 | +| `PyBLE-0.3.0-build-9-production-release.aab` | `fcf4692dbf7655f53a50a0687eedb81d9cf63bc601721552f622246d5cca0330` | 64,414,627 | |
| 70 | +| `PyBLE-0.3.0-build-9-production-release.apk` | `8656549a8480ae7ebfe9b6023220fa35c9b967fb07ca0a754a0ec24cd63e3e13` | 66,439,954 | |
| 71 | + |
| 72 | +| Check | Actual result | |
| 73 | +|---|---| |
| 74 | +| Package and version | `dev.pyble.pyble`, `0.3.0`, version code `9` | |
| 75 | +| SDKs / ABIs | Minimum 24, target/compile 36; `arm64-v8a`, `armeabi-v7a`, `x86_64` | |
| 76 | +| Signing | AAB JAR verification and APK signature verification pass; certificate SHA-256 matches the retained owner certificate `DCA95C5060CDF4936F19FD8C3212A871C223E2BA3FB67B6226179AFFDA62DD57` | |
| 77 | +| Bundle | Official bundletool 1.18.3 validation passes; tool digest checked against the retained verified digest; configuration declares `PAGE_ALIGNMENT_16K` | |
| 78 | +| Native libraries | All 12 packaged shared objects have every ELF LOAD alignment at least 16 KiB, including `libsqlite3.so` and `libdartjni.so` on all three ABIs | |
| 79 | +| APK alignment | `zipalign -c -P 16 -v 4` passes | |
| 80 | +| Permissions | Expected BLE, legacy location, Internet and AndroidX signature permission; no new authored platform permission | |
| 81 | +| Runtime page-size check | Production APK launched on the official API 36 Google APIs 16 KiB arm64 emulator; kernel `PAGE_SIZE=16384`, About `Version 0.3.0 (9)`, bundled native SQLite mapped from the APK, and fresh schema v1 created successfully | |
| 82 | + |
| 83 | +The 16 KiB runtime observation also force-stopped and relaunched the same |
| 84 | +installed package without data clearing. The normal disconnected screen |
| 85 | +returned; the retained fresh database and WAL reopened with `integrity_check=ok` |
| 86 | +and the expected `projects`, `project_files` and `settings` tables. This is a |
| 87 | +native packaging/startup smoke, not a physical BLE row or the full recovery |
| 88 | +acceptance matrix. The SQLite database's own page size is independent of the |
| 89 | +operating-system memory page size. |
| 90 | + |
| 91 | +The first local invocation incorrectly used `--no-pub` after fresh `pub get`, |
| 92 | +leaving the integration-test plugin in a generated Android registrant. Its |
| 93 | +failed log is retained. Repeating the canonical CI production commands, |
| 94 | +which allow Flutter to regenerate release plugin metadata, built both artifacts |
| 95 | +successfully without a source change. |
| 96 | + |
| 97 | +The APK uses the upload certificate, whereas Google Play can deliver its own |
| 98 | +app-signing certificate. Do not uninstall an existing user's Play app or clear |
| 99 | +its data merely to install this locally signed APK. Store upgrade acceptance |
| 100 | +must use the actual delivered package. |
| 101 | + |
| 102 | +## Prepared iOS distribution artifact |
| 103 | + |
| 104 | +| Field / check | Actual result | |
| 105 | +|---|---| |
| 106 | +| IPA | `PyBLE-0.3.0-build-9-app-store.ipa`, 23,782,489 bytes | |
| 107 | +| SHA-256 | `73ad7cda10c402a7f25316efc5e30f9c80bbd030e23c2bfc32313fd79c41c2ab` | |
| 108 | +| Identity | `dev.pyble.pyble`, `0.3.0 (9)`, normal `lib/main.dart` | |
| 109 | +| Build / deployment floor | Xcode 27.2 / iOS SDK 27.2; app and compiled deployment floor at least iOS 15.0 | |
| 110 | +| Export | App Store Connect distribution export; automatic signing with build-number management disabled; export destination only, no upload | |
| 111 | +| Provisioning | Production App Store profile; debugging disabled, no development-device list, beta reporting enabled; valid through 17 May 2027 | |
| 112 | +| Validation | `tools/validate_ios_ipa.sh` passes code-signature, compiled minimum OS, embedded-asset mode/classification and Xcode `swinfo` checks; only the three expected unsigned resource-bundle records are excluded | |
| 113 | + |
| 114 | +The archive and exported IPA are retained privately. A distribution package |
| 115 | +with no development-device list is not the separately installed development |
| 116 | +Preview app. Its local validation does not establish App Store processing, |
| 117 | +TestFlight availability, or store-installed upgrade behavior. |
| 118 | + |
| 119 | +## Distribution access and remaining account work |
| 120 | + |
| 121 | +The owner Android upload identity is locally usable and matches the historical |
| 122 | +certificate. A valid Apple distribution identity and cached production App |
| 123 | +Store provisioning profile are available. Signing access alone does not prove |
| 124 | +an authenticated store session, role, account version history or review status. |
| 125 | + |
| 126 | +No dedicated Play/App Store Connect connector or configured command-line store |
| 127 | +credential was found in the standard locations inspected. Account access and |
| 128 | +whether build 9 has already been consumed remain **unverified**. This is not a |
| 129 | +claim that the owner has no access through the respective web consoles. |
| 130 | + |
| 131 | +After the candidate is admitted, the authorized distribution operator must |
| 132 | +verify the exact package, unused build numbers and current declarations, upload |
| 133 | +the retained artifacts, resolve processing/review findings, and record actual |
| 134 | +availability and installed-store results separately. The prepared packet and |
| 135 | +artifact records make those steps concrete; they do not substitute for them. |
0 commit comments