Code signing tells iOS that your app comes from a known developer and has not been tampered with. For App Store distribution you need a Distribution Certificate and a matching App Store Provisioning Profile.

1. Create a Distribution Certificate

   1. Generate a Certificate Signing Request (CSR) on your Mac:
   • Open Keychain Access > Certificate Assistant > Request a Certificate from a Certificate Authority.
   • Enter your Apple Developer email, leave the CA email blank, and choose Save to disk.
   • Save the .certSigningRequest file.
   2. Log in to the Apple Developer Portal and go to Certificates, Identifiers & Profiles > Certificates.
   3. Click +, choose iOS Distribution (App Store and Ad Hoc), and upload your CSR.
   4. Download the generated .cer file and double-click it to install it into Keychain Access.
   5. Verify it appears under My Certificates with an associated private key.

2. Register an App ID (Bundle Identifier)

   1. In the Developer Portal go to Identifiers and click +. Select App IDs and type App.
   2. Set the Bundle ID to match your React Native project exactly (e.g., com.yourcompany.reelEaseAI).
   3. Enable any required Capabilities (Push Notifications, Sign in with Apple, etc.) and click Register.
   Important: The Bundle ID must exactly match PRODUCT_BUNDLE_IDENTIFIER in Xcode and the bundleId in your React Native config.

3. Create an App Store Provisioning Profile

   1. Go to Profiles in the Developer Portal and click +.
   2. Under Distribution, select App Store Connect.
   3. Select the App ID registered above, then select your Distribution Certificate.
   4. Name the profile (e.g., ReelEaseAI AppStore Distribution) and click Generate.
   5. Download the .mobileprovision file and double-click it — Xcode installs it automatically.

4. Configure Signing in Xcode

   1. Open your project's .xcworkspace in Xcode and select your app target.
   2. Open the Signing & Capabilities tab.
   3. For distribution, uncheck Automatically manage signing and under the Release configuration set:
      • Provisioning Profile — select the App Store profile you downloaded.
      • Signing Certificate — select your Distribution certificate.
   4. Confirm the Bundle Identifier in Xcode matches the App ID in the portal.
   Tip: If you see "No profiles for your team matching…", confirm the Bundle ID matches exactly, then go to Xcode > Preferences > Accounts > Download Manual Profiles.

5. Export & Share the Distribution Certificate

   1. Only one valid iOS Distribution certificate is allowed per team at a time.
   2. To share with a CI server or team member, export from Keychain Access:
      • Right-click the certificate (with its private key) and choose Export.
      • Save as a .p12 file with a strong passphrase.
      • Import the .p12 on the target machine using the same passphrase.

A provisioning profile ties together your App ID, certificate, and (for development) registered test devices. Different profile types serve different distribution scenarios.

Profile Types

Renewing a Provisioning Profile

1. Profiles expire after 1 year. Expired profiles will cause archive uploads to fail.
2. To renew: go to Developer Portal > Profiles, select the profile, click Edit, update the certificate if needed, and click Save. Re-download the updated file.
3. In Xcode go to Preferences > Accounts > Download Manual Profiles to pull the latest version.
4. Adding a new capability (e.g., Push Notifications) invalidates the existing profile — regenerate it after updating the App ID.

Managing Profiles via CI/CD

• Store the .p12 certificate and .mobileprovision file as encrypted secrets in your CI environment (GitHub Actions Secrets, Bitrise, etc.).
• Use Fastlane Match to sync certificates and profiles across machines via a private Git repo — the recommended approach for teams.
• Example Matchfile:

  git_url("https://github.com/yourorg/certificates")
  storage_mode("git")
  type("appstore")
  app_identifier(["com.yourcompany.reelEaseAI"])
  username("your-apple-id@example.com")

• Run fastlane match appstore to automatically download or create the distribution certificate and profile.

Once your build is archived and signed, follow these steps to prepare metadata, upload the build, and submit it for Apple review.

1. Prepare App Store Metadata

   1. Log in to App Store Connect, go to My Apps, and click + > New App. Fill in:
      • Platforms: iOS
      • Name: Your public app name (max 30 characters)
      • Bundle ID: Select the App ID registered in the Developer Portal
      • SKU: A unique internal identifier (not shown publicly)
   2. Under App Information, fill in Subtitle, Category, Content Rights, and Age Rating.
   3. Go to Pricing and Availability to set price tier and available territories.
   4. Complete the App Privacy nutrition labels — declare all data types your app collects. This is mandatory before submission.
   5. Provide a Privacy Policy URL — required for all apps.

2. Prepare Screenshots & Preview Videos

   1. Prepare screenshots for required device sizes:
      • 6.9" iPhone (iPhone 16 Pro Max) — required
      • 12.9" iPad Pro (5th gen or later) — required if your app supports iPad
   2. Screenshots must be PNG or JPEG at the correct pixel dimensions and must accurately represent the app UI.
   3. Optionally add an App Preview video (15–30 seconds) to showcase key features.
   Tip: Use Xcode Simulator to capture pixel-perfect screenshots at required resolutions.

3. Archive & Upload the Build from Xcode

   1. In Xcode, select Any iOS Device (arm64) as the destination.
   2. Go to Product > Archive and wait for the process to finish.
   3. In the Organizer, select your archive and click Distribute App.
   4. Choose App Store Connect > Upload.
   5. Select the Distribution certificate and App Store provisioning profile, then click Upload.
   6. Xcode validates and transmits the build. It appears in App Store Connect within a few minutes.

4. Select the Build & Answer Compliance Questions

   1. In App Store Connect, under your version, click + next to Build and select your uploaded build.
   2. Answer the Export Compliance question. For apps using HTTPS only (no custom encryption), answer No.
   3. If your app uses the Advertising Identifier (IDFA), declare its usage truthfully.

5. Distribute via TestFlight Before Submitting

   1. Go to TestFlight in App Store Connect after uploading.
   2. Internal Testers (up to 25 team members) can install immediately — no review needed.
   3. External Testing (up to 10,000 users) requires a Beta App Review, usually 1–2 days.
   4. Collect crash reports and feedback from TestFlight before public submission.

6. Submit for App Store Review

   1. Complete all metadata, screenshots, and privacy disclosures.
   2. Fill in What's New in This Version with a description of changes.
   3. Add Review Notes if demo credentials or special setup are needed by reviewers.
   4. Set Version Release:
      • Automatically release after review — goes live immediately upon approval.
      • Manually release — you control the release date after approval.
      • Scheduled release — specify a date and time.
   5. Click Add for Review, then Submit to App Review.
   6. Apple's review typically takes 24–48 hours. Track status in App Store Connect.
   Common Rejection Reasons: Inaccurate screenshots, missing privacy policy URL, broken functionality, or metadata referencing other platforms (e.g., "Android"). Review the App Store Review Guidelines before submitting.

7. Handle Review Feedback & Rejections

   1. Rejection reasons appear in the Resolution Center in App Store Connect.
   2. Fix the identified issue, upload a new build if a code change is needed, reply in the Resolution Center, and click Resubmit for Review.
   3. If you believe the rejection was in error, you can appeal via the Resolution Center.

App Store Submission Checklist

• Distribution certificate installed and valid in Keychain Access
• App Store provisioning profile downloaded and assigned in Xcode
• Bundle ID in Xcode matches App ID in Developer Portal
• Version number and build number updated
• App icon configured (1024x1024 PNG, no alpha, no rounded corners)
• Launch screen configured
• Info.plist permission descriptions filled in (NSCameraUsageDescription, etc.)
• All required screenshots uploaded in App Store Connect
• Privacy nutrition labels completed
• Privacy policy URL provided
• Export compliance answered
• TestFlight internal testing passed
• Build processed and selected in the version page
• What's New / Release Notes written

• For a complete walkthrough of the App Store upload process, we recommend consulting the official documentation. It covers each step in detail to ensure a smooth and successful submission:
  
  📄 Official Guide: Upload iOS App to App Store