iOS App Development

Purpose

Take an iPhone app from local requirements to a verified internal TestFlight build. Treat implementation, signing, upload, Apple processing, tester assignment, and device installation as separate states with separate evidence.

Core Rules

• Read repository instructions, requirements, project configuration, and release artifacts before declaring a blocker.
• Inspect a known successful app from the same owner when one exists. Reuse its account, signing, and release pattern without copying app-specific identifiers, entitlements, permissions, dependencies, or deployment targets.
• Keep the product display name separate from stable internal target and scheme names when renaming would create needless release risk.
• Set TARGETED_DEVICE_FAMILY: 1 for iPhone-only apps.
• Choose the minimum iOS version from required APIs and intended users. Do not copy another app's deployment target without evidence.
• Keep the app functional without an account unless account-backed behavior is an explicit requirement.
• Store secrets only through the repository's approved secret mechanism. Never print tokens, private keys, tester addresses, or account credentials.
• Do not claim TestFlight completion from a successful archive or upload alone.
• Do not commit or push unless the user has authorized it under the active repository instructions.

Start With Evidence