Reword the RunGlassesAction intent description so the upload passes ITMS-90626 - #307
Merged
Conversation
…TMS-90626 App Store Connect rejects an upload when App Intent metadata names a reserved term: 'App Intent description "Run an OpenGlasses action you've exposed to Siri — built-in, authored, or custom" cannot contain "siri"'. Dropped the word; the description now says "exposed for voice", which is what the sentence meant anyway. Audited the whole metadata surface rather than just the flagged string — every other IntentDescription, intent title, and AppShortcut phrase is clean, and the only other "Siri" under Intents/ is a code comment. Ordinary UI copy (settings rows saying "Siri Shortcuts") is not scanned; only the metadata the App Intents processor extracts. The runtime dialog strings in this same file still mention "Siri & Search" when telling the user where to re-enable a missing action. Those are values returned from perform(), not extracted metadata, so they should not trip the check — worth knowing in case a future upload disagrees. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
Fixes the ITMS-90626 upload rejection:
App Store Connect scans extracted App Intent metadata — titles, descriptions, AppShortcut phrases — and rejects reserved terms in them. Dropped the word; the description now reads "exposed for voice", which is what the sentence meant anyway.
Audited the whole surface, not just the flagged string
Every other
IntentDescription, intent title, andAppShortcutphrase is clean. The only other "Siri" underIntents/is a code comment. Ordinary UI copy is not scanned — the settings rows saying "Siri Shortcuts",SiriExposureView's "Siri & Search" title and so on are all fine and untouched.Residual risk worth knowing
The runtime dialog strings in this same file still say "Check OpenGlasses Settings → Siri & Search" when telling the user a missing action needs re-enabling. Those are values returned from
perform(), not extracted metadata, so they shouldn't trip the check. Flagging rather than pre-emptively reworghtint them, since they're the clearest wording for the user. If a future upload disagrees, that's where to look.Verification
String-literal change only, so no behavioural risk. Not build-verified — worth noting that App Intent metadata problems only surface in a Release/SDK build via
appintentsmetadataprocessor, and a bad intent can silently wipe all intent metadata. A plain string swap can't do that, but the upload itself is the real check here.🤖 Generated with Claude Code