[beruro]

Problem

The iOS release workflow only accepts App Store Connect provisioning profiles and always exports with app-store-connect. The resulting IPA can be uploaded to TestFlight but cannot be installed through Pgyer on registered devices.

Solution

Add an ad-hoc distribution choice to the existing iOS release workflow while keeping App Store Connect as the default. The workflow selects the dedicated Ad Hoc profile, validates that it contains registered devices and disables debugging, generates matching export options, and validates the exported IPA against the selected distribution method. TestFlight upload remains restricted to App Store Connect packages.

Potential risks

Ad Hoc builds install only on devices embedded in the selected provisioning profile; the current profile contains one registered iPhone. Adding devices later requires regenerating the profile and rebuilding. The existing App Store Connect path remains the default and retains its prior profile and upload checks.

Verification

• node --test scripts/ios-release/manual-signing.test.mjs scripts/ios-release/readiness.test.mjs — passed, 33 tests
• git diff --check — passed
• Ruby YAML parser loaded .github/workflows/ios-testflight.yml successfully
• Decoded the generated Ad Hoc profile locally and verified its bundle ID, team, expiry, and registered-device list; no profile contents or signing material are committed
• Full GitHub Actions Ad Hoc build has not run yet because the workflow change must merge to the protected develop branch first