[chore] iOS 1.15 (build 27): the microphone on the lock screen - #394
Merged
Merged
Conversation
For iOS this release is #393 and nothing else — the four other commits since ios-v1.14 are desktop, Android, the website, and 1.14's own release notes. What's New says so in both locales, and no screenshots were re-captured because nothing inside the app moved: the card is a lock-screen surface. The part that would otherwise have cost a twenty-minute CI run: #393 embedded a third target, and `asc_signing.py` had the two bundle ids written into it twice over — once as a tuple to iterate and once as a pair of outputs. A target with no provisioning profile does not fail at the point it is added. It fails at export, saying `No profiles for '…' were found`, about a bundle id nobody was thinking about. That list is now `SIGNED_BUNDLES`, and RELEASING.md says out loud that adding an embedded target means adding it there and registering it on the portal first. `com.pathors.parley.ios.activities` still has to be registered on the developer portal, with App Groups enabled and joined to group.com.pathors.parley.ios, before a tag will build. All three targets move to 1.15 (27) together; a mismatch is rejected at upload rather than at build.
✅ SonarQube Quality Gate passed — pathorsAI_parley0 open issues on this PR. |
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
2 participants
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.
iOS 1.15 is #393 and nothing else. The four other commits since
ios-v1.14are desktop (src/), Android, the website, and 1.14's own release notes — none of them ships in an iPhone build.The part that would have cost a CI run
#393 embedded a third target,
com.pathors.parley.ios.activities.asc_signing.pyhad the two bundle ids written into it twice over — once as a tuple to iterate, once as a pair of step outputs — so a tag push would have archived for twenty minutes and then failed at export withNo profiles for '…' were found, naming a bundle id whoever read the log was not thinking about. That is the exact failure modeRELEASING.mdalready documents for a missing profile; nothing connected it to adding a target.The list is now
SIGNED_BUNDLES, and both the script and the runbook say out loud that adding an embedded target means adding it there and registering the id on the portal first.com.pathors.parley.ios.activitiesstill has to be registered on developer.apple.com — App Groups capability enabled, joined togroup.com.pathors.parley.ios— before any tag will build.asc_signing.pylooks bundle ids up and refuses if they are missing; it never creates them, and the App Store Connect API key exists only as a GitHub secret, so there is no local path to do it from.Versions
All three targets move to 1.15 (27) together — app, keyboard, activities. A mismatch is rejected at upload, not at build, so they are bumped in
project.ymland the regeneratedInfo.plists are committed with it.What's New
Written for 1.15 in both locales and verified against the parser in
asc_submit.py: both sections are found, stop cleanly at the 1.14 heading, and come in well under Apple's 4,000-character limit (en-US 1,341; zh-Hant 413). zh-Hant is a peer of the English, not a translation of it.The copy describes the card, the three states it covers, the fact that nothing from the meeting appears on it, and the two new haptics. It promises nothing about resuming an interrupted recording, because that is not in this release.
No screenshots were re-captured. Nothing inside the app moved — the card is a lock-screen surface — so the existing 6.9-inch sets in both locales are still accurate.
Before this ships
The Live Activity carries one unverified assumption, documented in
docs/design/ios-live-activity.md: it is not established thatactivity.update(...)reaches a backgrounded app holding a recording audio session. The card is built to be correct either way — every clock is aText(timerInterval:)the system ticks inside the widget process — but TestFlight is where that should be checked, on a real device, before submitting to review.MicActivityPolicy.staleAfteris the single constant that changes if the answer is bad.Verification
xcodegen generate+xcodebuild -scheme Parley -configuration Debug -destination generic/platform=iOS→ BUILD SUCCEEDED.asc_submit.whats_newat version1.15.Info.plists confirmed at 1.15 / 27.asc_signing.pyparses; its API paths are unchanged and untestable without the key.🤖 Generated with Claude Code