Code Signing Troubleshooting
Common Code Signing Issues
Section titled “Common Code Signing Issues”No Signing Credentials Configured
Section titled “No Signing Credentials Configured”Error:
Error: No signing certificate foundCode signing error: no credentials configuredCause:
- API key not set up at workspace level
- App signing configuration not set
Solution:
-
Go to Workspace Settings > Apple Signing
-
Verify API key is configured:
- Issuer ID is entered
- Key ID is entered
- Team ID is entered
- Private key (.p8) is pasted
-
Click Save if you’ve made changes
-
Go to App Settings > Apple Signing
-
Verify app configuration:
- Bundle Identifier is entered
- Signing Type is selected
-
Click Save if you’ve made changes
If you’re on the Free plan, you must upgrade to PAYG, Pro, or Business to use automatic code signing.
Certificate Expired or Revoked
Section titled “Certificate Expired or Revoked”Error:
Error: Certificate expiredCode signing error: certificate not validCause:
- Your Apple Distribution certificate has expired
- Certificate was revoked in Apple Developer account
Solution:
For auto-generated certificates:
- RunnerHub will automatically create a replacement certificate on the next build
- No action needed
For manually uploaded P12 certificates:
- Go to Workspace Settings > Apple Signing
- Click Remove Certificate
- Upload a new valid P12 certificate, or
- Let RunnerHub auto-generate a new certificate
Bundle ID Not Registered
Section titled “Bundle ID Not Registered”Error:
Error: Bundle ID not found in Apple accountProvisioning profile creation failedCause:
- Bundle ID in App Settings is not registered in Apple Developer
- Bundle ID has a typo
Solution:
- Go to App Store Connect
- Click Certificates, Identifiers & Profiles > Identifiers
- Verify your bundle ID is listed (e.g.,
com.example.myapp) - If not listed, click + to register a new identifier
- In RunnerHub App Settings > Apple Signing, verify bundle ID matches exactly (case-sensitive)
Bundle ID Mismatch
Section titled “Bundle ID Mismatch”Error:
Signing error: bundle ID mismatchExpected com.example.myapp, got com.example.wrongappCause:
- Bundle ID in App Settings doesn’t match your Xcode project
- Typo in either location
Solution:
- Open your Xcode project
- Select the target
- Go to Build Settings > Product Bundle Identifier
- Copy the bundle ID from Xcode
- In RunnerHub App Settings > Apple Signing, paste the bundle ID exactly
- Ensure it matches with no extra spaces
Provisioning Profile Not Found
Section titled “Provisioning Profile Not Found”Error:
Error: No provisioning profile found for bundle IDUnable to create profile: bundle identifier not registeredCause:
- Bundle ID is not registered in Apple account
- Your team doesn’t have permission to create profiles
- API key doesn’t have enough permissions
Solution:
-
In App Store Connect, register the bundle ID:
- Go to Certificates, Identifiers & Profiles > Identifiers
- Click + and create a new App ID with your bundle ID
-
Verify API key permissions:
- The API key must have Developer or App Manager role
- Go to Users and Access > Keys and check the key’s role
- If it has insufficient permissions, create a new key with proper access
-
Re-enter the API key in RunnerHub:
- Go to Workspace Settings > Apple Signing
- Click Remove API Key
- Add the API key again
Wrong Signing Type
Section titled “Wrong Signing Type”Error:
Profile mismatch: expected appstore, found developmentCode signing error: wrong provisioning profileCause:
- Signing type in App Settings doesn’t match your deployment target
- Built a development build but trying to submit to App Store
Solution:
-
Determine which signing type you need:
- development: Testing on devices, TestFlight testing
- adhoc: Ad-hoc distribution to specific devices
- appstore: App Store submission
-
In RunnerHub App Settings > Apple Signing, select the correct signing type
-
Run the build again
P12 Password Incorrect
Section titled “P12 Password Incorrect”Error:
Error: Cannot decrypt P12 filePassword is incorrect or P12 is corruptedCause:
- Password entered during P12 upload is wrong
- P12 file is corrupted or invalid
Solution:
- Try uploading the P12 again with the correct password
- If you don’t remember the password:
- Export a new P12 from Keychain Access with a new password
- Upload the new P12 to RunnerHub
Team ID Mismatch
Section titled “Team ID Mismatch”Error:
Team ID mismatch: API key is from team ABC123D45E, but signing is configured for XYZ789P01QCause:
- API key’s team ID doesn’t match the team ID in your signing configuration
- You’re trying to use an API key from a different Apple team
Solution:
-
Verify your Team ID:
- In App Store Connect, go to Account > Membership
- Copy your Team ID
-
In RunnerHub Workspace Settings > Apple Signing:
- Verify the Team ID field matches your actual Apple Team ID
- Update if necessary and save
-
If you’re using an API key from a different team:
- Revoke the old API key in Apple Developer
- Create a new API key for your correct team
- Update RunnerHub with the new key
Feature Not Available on Your Plan
Section titled “Feature Not Available on Your Plan”Error:
403 Forbidden: Code signing feature requires PAYG or higher planCause:
- You’re on the Free plan
- Free plan does not include automatic code signing
Solution:
Upgrade to PAYG, Pro, or Business:
- Go to Billing
- Click Upgrade Plan
- Select your desired plan
- Complete payment
Free plan users can still manage signing within their pipeline using Fastlane Match or manual setup.
Debugging Steps
Section titled “Debugging Steps”If you encounter a code signing error:
-
Check the job logs
- Go to the failed job in the dashboard
- Scroll through the logs for the error message
- Note the exact error text
-
Verify workspace configuration
- Go to Workspace Settings > Apple Signing
- Ensure API key is fully configured (all fields filled)
- Click Save to refresh
-
Verify app configuration
- Go to App Settings > Apple Signing
- Ensure bundle ID matches your Xcode project exactly
- Ensure signing type is appropriate for your use case
- Click Save to refresh
-
Check Apple Developer account
- Verify bundle ID is registered
- Verify API key is not revoked
- Verify certificate is not expired (if manually uploaded)
-
Re-run the job
- After making changes, run the job again
- Some issues require a fresh build to resolve
Getting Help
Section titled “Getting Help”If the issue persists:
- Check your job logs in the RunnerHub dashboard
- Verify all configuration steps in API Key Setup and Per-App Signing
- Confirm your plan includes code signing (PAYG or higher)
- Verify your Apple credentials are current and valid
- Contact RunnerHub support with your job logs
See also: