Skip to content

feat(ios): #1301 best-effort App Groups capability enablement + manual-step guidance#1313

Merged
proggeramlug merged 1 commit into
mainfrom
worktree-ios-1301-appgroup
May 22, 2026
Merged

feat(ios): #1301 best-effort App Groups capability enablement + manual-step guidance#1313
proggeramlug merged 1 commit into
mainfrom
worktree-ios-1301-appgroup

Conversation

@proggeramlug
Copy link
Copy Markdown
Contributor

Closes #1301.

Context

The bulk of #1301perry setup ios --development, the on-device dev-sign path, devicectl install/launch, and device (vs. simctl) install instructions — already shipped in #1302 / v0.5.1023. The single open item was the issue's "related friction": App Group identifiers aren't auto-registered.

What this does

This is the best-effort closeout of that last item, bounded by what Apple's API actually allows.

perry setup ios --development and the perry run --target ios dev-sign path now read a declared [ios] app_group from perry.toml and enable the APP_GROUPS capability on the bundle ID via POST /v1/bundleIdCapabilities.

Apple's public App Store Connect API can toggle that capability but cannot create the group.* App Group identifier nor bind it to the App ID — there is no public endpoint for it (developer.apple.com/forums/thread/127917; confirmed against current ASC API docs). Rather than silently mint a profile that fails to validate the application-groups entitlement, we enable the capability and print the exact remaining manual portal step:

    Enabling App Groups capability... done

    note: App Group group.com.example.shared needs a one-time manual step — the App Store
    Connect API cannot create or bind App Group identifiers. In the
    Apple Developer portal (Certificates, Identifiers & Profiles):
      1. Identifiers → + → App Groups → register group.com.example.shared
      2. Identifiers → App ID com.example.app → App Groups → Edit → check group.com.example.shared
    Then re-run so the profile picks up the binding.

Changes

  • create_dev_profile_via_api: new app_group param; enables APP_GROUPS (409/already-enabled tolerant, never gates profile creation), then prints the register + attach steps.
  • read_ios_app_group_from_toml: [ios][app] → top-level precedence, matching app_metadata.rs; threaded from both setup ios --development and resign_for_development.
  • Unit test covering the precedence + empty/missing/invalid-toml edge cases.

Testing

  • cargo build --release -p perry — clean.
  • cargo test --release -p perry resign module: parse_ios_app_group_precedence, dev_entitlements_* all pass.
  • cargo fmt --all -- --check — clean.

Version bump + CHANGELOG entry intentionally omitted (folded in at merge).

…l-step guidance

`perry setup ios --development` and the `perry run --target ios` dev-sign path
now read a declared `[ios] app_group` from perry.toml and enable the APP_GROUPS
capability on the bundle ID via the App Store Connect API.

Apple's public ASC API can toggle the capability but cannot create or bind the
`group.*` App Group identifier (no public endpoint —
developer.apple.com/forums/thread/127917), so the one remaining manual portal
step is surfaced inline instead of silently producing a profile that fails to
validate the application-groups entitlement.

- create_dev_profile_via_api: new app_group param; POST /v1/bundleIdCapabilities
  (409/already-enabled tolerant, never gates profile creation), then print the
  register + attach portal steps.
- read_ios_app_group_from_toml: [ios] -> [app] -> top-level precedence, matching
  app_metadata.rs; threaded from setup + resign_for_development.
- unit test covering the precedence + empty/missing/invalid edge cases.
@proggeramlug proggeramlug merged commit 72a0b53 into main May 22, 2026
8 of 9 checks passed
@proggeramlug proggeramlug deleted the worktree-ios-1301-appgroup branch May 22, 2026 08:28
proggeramlug added a commit that referenced this pull request May 22, 2026
…sweep (#1414)

Rolls up 26 PRs that merged to main post-v0.5.1023 without version
bumps:

- node:crypto gap-fixes (#1386 #1393 #1394 #1402 #1405): randomInt,
  timingSafeEqual, getHashes/getCiphers, sha224/sha384, base64 digest,
  Buffer hash input, no-arg digest() → Buffer, pbkdf2Sync digest arg,
  scryptSync.
- node:perf_hooks (#1321 + #1328 #1342 coverage): performance + User
  Timing + PerformanceObserver native impl, granular node-suite +
  edge-case coverage.
- #1090 GC checkpoint runtime work (#1324).
- #1311 geisterhand on iOS (#1316 #1383 #1384 #1385).
- #1312 process.env.X (unset) is nullish undefined (#1314).
- #1319 thread-safety hardening for cross-thread runtime statics.
- #1322 exact-head GC evidence packet.
- #1323 wasm timers dispatch through mem_call bridge (#1329).
- #1317 node:timers/promises shadow-segfault fix (#1326).
- #1330 node:process suite (#1331).
- #1292 bcrypt.hash() returns String (#1307).
- #1293 fastify .json()/.body external-fastify dispatch (#1308).
- #1296 app pattern performance gaps.
- #1297 diagnostics_channel parity.
- #1301 iOS App Groups capability (#1313).
- #1318 #1325 os/methods/modern-methods static dispatch.
- #1315 expanded Node parity test coverage.
- #1382 ui-ios stdlib pump for async fetch.
- #1392 ui-wasm reactive state + setText (#1404).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

perry setup ios only provisions for distribution — add development-profile + device-registration + on-device run path

1 participant