1.0.31-0.diagnostic.1189.b.0
25th September, 2026
This release is for diagnostic purposes only and is not intended for everyday use. Please bear this in mind.
Diagnostics
- Issue #1189: retain the same device-local Fast Setup record and interrupted-attempt pause used in build A.
- Build B scans one local file at a time during Fast Setup and other file scans; build A scans up to ten. Compare the two builds to help determine whether scan load contributes to the reported restarts. Neither build is a confirmed fix.
- In BRAT, choose this exact release as a frozen version when comparing A and B. 'Latest' may change as newer releases appear. See the BRAT developer guide.
- Use the commands 'Copy diagnostic record' or 'Save diagnostic record' to collect the JSON. The saved copy is written to the plug-in folder. After collecting it, use 'Resume diagnostic attempt' to try again. The automatic record contains timing, file counts, and sizes, but no file paths or file contents.
Build provenance
- LiveSync source commit: 29fbe6e. Built locally with ISSUE_1189_VARIANT=serial.
- Commonlib source commit: c28f8a520370d135e6313ffe94150725713e39b1. The bundle includes the attached, unpublished local tarball vrtmrz-livesync-commonlib-0.1.27-local-issue1189.tgz, SHA-256 8207e0d6e1f6cf0a4271cf03b986d97380c442bbcf2859334a3f3cc7f5b36842.
- The tarball declares Commonlib version 0.1.27 but differs from the published npm package with that version. LiveSync's package and lockfile still resolve the published 0.1.27, so npm ci alone will not reproduce this main.js. This modified Commonlib package was not published to npm.
- Release assets: main.js SHA-256 76b6e390f2e8e42527c42176521979cd5d4c34bd5dda1a20bbfcee9c19c9cad0; manifest.json SHA-256 60b790cdfc6b26b5747c65637a3ea9e45bc192abc62716b02bb6a83c2de09bb4; styles.css SHA-256 4ba00bef417ee98d9a62dd9febb792dc6555949cfc9e8e069450ad699ab2b9f0.
Validation
The local production build, release metadata check, and iOS 15 syntax check passed. The build has not yet been tested through BRAT or on the affected iOS device, and the cause of the restart remains unconfirmed.