[chore] iOS 1.6.2 (build 17): the host return decides at runtime - #322
Merged
Merged
Conversation
Ships #321. 1.6.1 carried a compiled-in `#available(iOS 26.4, *)` gate that refused the jump back to the host app on the newest iOS — a number written from early reports, on devices where the path observably still works. It is now a runtime decision made from a remote flag, per-device evidence, and the OS build as a key rather than a threshold, so the answer can be corrected without a release and a device re-tries by itself after an iOS update. Build 17 because App Store Connect has already seen 16. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
✅ SonarQube Quality Gate passed — pathorsAI_parley0 open issues on this PR. |
Open
2 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Version bump so #321 can ship.
ios-v1.6.1is already on TestFlight at build 16, and App Store Connect refuses a build number it has seen — so the one commit sitting untagged onmainneeds 1.6.2 / build 17 to leave the repo.What ships
#321 — the jump back to the host app after a dictation. 1.6.1 carried a compiled-in
#available(iOS 26.4, *)gate, written from early reports that Apple had closed the path, and it was switching off a trip that observably still works.HostReturnPolicyreplaces the number with a runtime decision: a remote kill switch, evidence the device collected about its own attempts, and the OS build string as a key rather than a threshold — so a wrong answer is correctable in minutes instead of in a release, and a device re-tries by itself after an iOS update.The bump
ios/App/project.yml:CFBundleShortVersionString1.6.1 → 1.6.2,CFBundleVersion16 → 17, both targets.ios/App/Parley/Info.plist,ios/Keyboard/Info.plist: regenerated withxcodegen generate, committed alongside — editing the plists alone is overwritten on the next generate.ios/AppStore/metadata/{en-US,zh-Hant}.md: a "What's New — 1.6.2" written for someone who noticed they had to swipe back, in both locales.No app code changes here.
After merge
git tag ios-v1.6.2 && git push origin ios-v1.6.2—ios-release.ymlarchives and uploads to TestFlight from there. The workflow refuses to build if the tag disagrees withCFBundleShortVersionString, which this bump satisfies.bunx tsc --noEmitandbunx vitest runboth pass (269 tests), though nothing here is TypeScript.🤖 Generated with Claude Code