Expo构建Ad-hoc IPA的解决方案：无法添加自定义描述文件问题

Hey there, let's work through this problem together— I’ve dealt with similar Expo ad-hoc signing hurdles before, so here are three actionable solutions to get your IPA ready for re-signing and distribution:

1. Generate a Generic IPA via EAS Build, Then Manually Re-Sign #

This is the most straightforward approach if you don’t want to mess with native code. Expo’s EAS Build can output a "generic" IPA that’s unbound to any specific signing profile, which you can then re-sign with your ad-hoc provisioning file.

• First, configure your eas.json to define a generic iOS build profile:

  {
    "build": {
      "generic-ios": {
        "ios": {
          "buildConfiguration": "Release",
          "distribution": "generic"
        }
      }
    }
  }
  

• Run the build command:

  eas build --profile generic-ios --platform ios
  

• Once the build finishes, download the generated IPA. Now unzip it to access the app bundle:

  unzip YourApp.ipa -d Payload
  

• Replace the embedded provisioning profile with your ad-hoc one:

  cp YourAdHocProfile.mobileprovision Payload/YourApp.app/embedded.mobileprovision
  

• Re-sign the app bundle using your ad-hoc certificate. Make sure you have the correct entitlements plist (match it to your provisioning profile’s permissions):

  codesign -f -s "Your Ad-Hoc Certificate Name" --entitlements YourEntitlements.plist Payload/YourApp.app
  

• Finally, re-package the IPA:

  zip -r ReSignedAdHocApp.ipa Payload
  

  Pro tip: Double-check that your entitlements include get-task-allow set to false for release builds, and that the bundle ID matches exactly between your app, certificate, and provisioning profile.

2. Export Native Code from Expo, Build Ad-Hoc IPA Directly in Xcode #

If you’re comfortable with Xcode, exporting the native project lets you leverage Apple’s official signing workflow directly.

• Export the iOS native project from your Expo app:

  expo export --platform ios
  

  This will generate an Xcode workspace in the dist/ios directory.
• Open the .xcworkspace file in Xcode. Navigate to your project’s target > Signing & Capabilities:
  • Toggle on Automatically manage signing, then select your personal Apple ID and the corresponding ad-hoc provisioning profile.
  • Or, if you prefer manual signing, select your ad-hoc certificate and provisioning profile directly.
• Set the build configuration to Release, then go to Product > Archive to create a build archive.
• Once the archive completes, open the Xcode Organizer, select your archive, and choose "Distribute App" > "Ad Hoc" to generate your signed IPA.

3. Automate Re-Signing with Fastlane #

For repeated signing tasks, Fastlane can streamline the process and reduce manual errors.

• Initialize Fastlane in your project directory:

  fastlane init
  

• Edit your Fastfile to add a lane for ad-hoc re-signing. This example assumes you’ve already downloaded a generic IPA from EAS:

  lane :resign_ad_hoc do
    # Download your ad-hoc provisioning profile (if not already local)
    sigh(adhoc: true, force: true)
    
    # Re-sign and package the IPA
    gym(
      export_method: "ad-hoc",
      export_options: {
        provisioningProfiles: {
          "com.yourcompany.yourappbundleid" => "Your Ad-Hoc Provisioning Profile Name"
        }
      },
      ipa: "YourGenericIPA.ipa"
    )
  end
  

• Run the lane to handle all signing steps automatically:

  fastlane resign_ad_hoc
  

Key Notes to Avoid Headaches #

• Ensure your ad-hoc provisioning profile includes all device UDIDs if you’re distributing to specific test devices (personal accounts require this; enterprise accounts don’t).
• Always verify that the bundle ID of your Expo app matches exactly with the one in your certificate and provisioning profile.
• If you run into code signing errors, check Xcode’s logs or use codesign --verify -vvv Payload/YourApp.app to debug issues.

内容的提问来源于stack exchange，提问作者Anders Gerner