Direct Answer: Testing Wire-Free on Physical Hardware
Running your AI-built iOS app in the macOS Simulator is great for quick layout checks, but simulators cannot test physical hardware: camera lenses, Face ID, push notifications, Bluetooth accessories, real touch gestures, and thermal throttling only function on an actual iPhone.
You do not need USB cables, Xcode wireless pairing, or 7-day personal certificates to test on your phone. The production standard for wire-free testing is Apple TestFlight Internal Testing.
Once you compile your .ipa binary locally, you ask your AI coding assistant through FlightDeck to inspect the archive, upload it to App Store Connect, monitor Apple's processing, and attach it to your internal test group. Your iPhone receives an over-the-air notification through the free TestFlight app to install the build—with zero cable clutter, zero developer-mode toggling, and builds that remain active for 90 days.
What You Need
Before initiating wire-free deployment, ensure you have:
- Paid Apple Developer Program Membership: Required for TestFlight access ($99/year).
- Physical iPhone: Running iOS 14 or later with the free TestFlight app installed from the App Store.
- Internal Tester Role: Your personal Apple ID must be listed under Users and Access in your App Store Connect team with at least the Developer or App Manager role.
- FlightDeck for Mac: Installed, running, and connected to your AI assistant (see our Cursor Setup Guide or Claude Code Guide).
- Compiled Signed IPA: A distribution-signed
.ipabinary on your Mac. (FlightDeck automates inspection, upload, and distribution; source compilation and signing are handled locally via Xcode or framework CLIs).
The Three Wire-Free iOS Deployment Workflows
Before uploading, understand the three wireless options in the Apple ecosystem:
| Feature / Requirement | 1. Xcode Wireless Debugging | 2. Free Personal Apple ID | 3. TestFlight Internal Testing (Recommended) |
|---|---|---|---|
| Physical Cable Needed? | Required once for initial pairing | Required once (or Wi-Fi after pairing) | Never (Over-The-Air install via App Store) |
| Apple Developer Account | Free Apple ID or Paid ($99/yr) | Free Apple ID | Paid Apple Developer Program ($99/yr) |
| App Lifespan on Device | 7 days (Free) / 1 year (Paid) | Strictly 7 days before certificate revoke | 90 days per build |
| Max Concurrent Apps | 3 active apps on device | 3 active apps | Unlimited TestFlight apps |
| Tester Reach | Only your paired personal Mac/device | Only your paired personal device | Up to 100 internal team members |
| Apple Review Required? | None | None | Zero review required for internal groups |
| Device Developer Mode | Required (iOS 16+) | Required (iOS 16+) | Not required |
| Workflow Tooling | Xcode GUI | Xcode GUI | FlightDeck MCP + TestFlight App |
Free personal Apple IDs revoke installed apps after exactly 168 hours (7 days). If you use a free account, the app will crash on launch on day 8 until you reconnect your Mac and re-sign. TestFlight internal builds avoid this entirely, remaining functional for 90 days.
Step-by-Step Solution: Deploying Wire-Free with FlightDeck
Step 1: Export a Signed .ipa Archive (CLI)
Compile your app for App Store distribution using your terminal toolchain:
For Native Xcode Projects:
# 1. Archive the project
xcodebuild archive \
-workspace MyApp.xcworkspace \
-scheme MyApp \
-configuration Release \
-archivePath build/MyApp.xcarchive
# 2. Export the signed distribution IPA
xcodebuild -exportArchive \
-archivePath build/MyApp.xcarchive \
-exportPath build/ipa \
-exportOptionsPlist exportOptions.plist
For Flutter Projects:
flutter build ipa --release --export-options-plist=ios/ExportOptions.plist
This outputs a pre-signed distribution archive at build/ipa/MyApp.ipa (or build/app/outputs/bundle/release/*.ipa).
Step 2: Inspect and Upload via Your AI Assistant (Prompt)
Instead of navigating the App Store Connect web portal or configuring complex upload tools, instruct your AI assistant to validate and upload the binary:
Copy and paste this prompt into Cursor, Claude Code, Antigravity, or Windsurf:
Inspect the signed iOS archive at [path/to/YourApp.ipa] for [Your App Name]. Verify that its bundle ID, version, and architecture match our App Store Connect settings, then stage the binary upload for my approval in FlightDeck.
What Your Assistant Does:
- It validates the local
.ipastructure (verifying embeddedInfo.plist, 64-bit ARM architecture slices, and bundle ID alignment). - It stages the upload and displays a confirmation card in the FlightDeck Desktop Approval Center on your Mac.
- You review the file size, version string, and SHA-256 hash, then click Approve.
- FlightDeck streams the binary directly to Apple's ingestion endpoints over a secure HTTPS connection.
Step 3: Monitor Processing and Attach to Internal Testers (Prompt)
Apple's servers automatically scan the binary, extract dSYMs, and verify format integrity. Once processing finishes, attach the build to your internal test group:
Check App Store Connect for [Your App Name]. Monitor our latest uploaded build until Apple finishes processing it. Once it is valid, attach it to our 'Internal Testers' beta group so I can install it on my iPhone.
What Your Assistant Does:
- It monitors Apple's server state until
processingStatetransitions fromPROCESSINGtoVALID(typically 5–15 minutes). - It verifies export compliance status. (If your
Info.plistincludes<key>ITSAppUsesNonExemptEncryption</key><false/>, Apple clears compliance automatically). - It stages the build attachment to your internal beta group.
- You click Approve in the FlightDeck Desktop Approval Center. Because internal testing requires zero Apple review, Apple registers the build for internal distribution, and testers can install it as soon as Apple's distribution CDN synchronizes (typically within seconds to a few minutes).
Step 4: Install Wire-Free on Your iPhone
- On your iPhone, open the TestFlight app.
- Under your app listing, tap Install or Update.
- The app downloads over Wi-Fi or cellular data and installs directly to your home screen with the characteristic TestFlight beta dot.
Verify Success: Confirming Active Distribution
Confirm that your iPhone is receiving the latest build by asking your assistant:
Verify that our latest build of [Your App Name] is now actively distributed to our internal TestFlight group. Tell me the version and build number that testers currently see.
What to Expect:
- TestFlight delivers a notification to your test devices and registers the update in your TestFlight library. (Notification timing depends on Apple's push service and device connectivity).
- Opening TestFlight displays the new build with an Update or Install button.
- The app installs wire-free directly to your device and remains active for up to 90 days.
Troubleshooting Common Wire-Free Testing Errors
1. Build Blocked by "Missing Export Compliance"
- Symptom: The build finishes processing, but a yellow warning badge appears in App Store Connect stating compliance is required.
- Cause: Apple requires every uploaded build to declare its encryption usage under U.S. export regulations.
- Resolution: Add
<key>ITSAppUsesNonExemptEncryption</key><false/>to your app'sInfo.plist(see Fixing Missing Encryption Key). For the current build, ask your assistant: > "Check export compliance requirements for our latest build of [Your App Name] and help me clear any missing declarations."
2. Tester Does Not See the Build in TestFlight
- Symptom: The build is marked
VALIDand attached to an internal group, but your iPhone TestFlight app shows an empty library. - Cause: The Apple ID signed into the iPhone's App Store must match the email invited to your App Store Connect team, and that user must have accepted their team invitation email.
- Resolution: Open App Store Connect $\rightarrow$ Users and Access, verify your personal Apple ID is listed, and ensure you accepted the invitation email on that Apple ID.
3. Build Taking Longer Than 20 Minutes to Process
- Symptom: Apple continues to report the build as processing.
- Resolution: Ask your assistant: > "Check if our latest build for [Your App Name] has finished processing yet." Apple server queues occasionally experience delays during major iOS launch cycles. Never re-upload the identical build counter; Apple will reject it with error
ITMS-90189. Wait for Apple's confirmation email or check for automated rejection notices.