You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
EAS Build fails to generate a provisioning profile for the iOS Share Extension automatically.
When running eas build --local --platform ios --profile production, the build fails with a missing provisioning profile for the Share Extension.
EAS only recognizes and handles credentials for the main app , but not for the Share Extension. Should this happen automatically or am I missing some config setup?
Ive created a new project to test it and experience the same issue.
Have also tried defining the extension in app.json using extra.eas.build.experimental.ios.appExtensions config.
I am able to run the app / extension fine in the simulator and it works great.
🛠️ To Reproduce
After running eas build - the first error I receive is this:
[RUN_FASTLANE] [!] Error building the application - see the log above
[RUN_FASTLANE] Error: The "Run fastlane" step failed because of an error in the Xcode build process. We automatically detected following errors in your Xcode build logs:
- No profiles for 'x.share-extension' were found: Xcode couldn't find any iOS App Development provisioning profiles matching 'x.share-extension'. Automatic signing is disabled and unable to generate a profile. To enable automatic signing, pass -allowProvisioningUpdates to xcodebuild. (in target 'ShareExtension' from project 'exposhare')
[RUN_FASTLANE] [!] Error building the application - see the log above
[RUN_FASTLANE] Error: Starting from Xcode 14, resource bundles are signed by default, which requires setting the development team for each resource bundle target.
To resolve this issue, downgrade to an older Xcode version using the "image" field in eas.json, or turn off signing resource bundles in your Podfile: https://expo.fyi/r/disable-bundle-resource-signing
I can get around this by selecting a team within Xcode for both the app and the share extension.
But then, I run into this error:
[RUN_FASTLANE] [!] Error building the application - see the log above
[RUN_FASTLANE] Error: The "Run fastlane" step failed because of an error in the Xcode build process. We automatically detected the following errors in your Xcode build logs:
- No profiles for 'ex.share-extension' were found: Xcode couldn't find any iOS App Development provisioning profiles matching 'ex.share-extension'.
📋 Describe the bug
EAS Build fails to generate a provisioning profile for the iOS Share Extension automatically.
When running
eas build --local --platform ios --profile production
, the build fails with a missing provisioning profile for the Share Extension.EAS only recognizes and handles credentials for the main app , but not for the Share Extension. Should this happen automatically or am I missing some config setup?
Ive created a new project to test it and experience the same issue.
Have also tried defining the extension in app.json using
extra.eas.build.experimental.ios.appExtensions
config.I am able to run the app / extension fine in the simulator and it works great.
🛠️ To Reproduce
After running eas build - the first error I receive is this:
I can get around this by selecting a team within Xcode for both the app and the share extension.
But then, I run into this error:
⚙️ Environment Details
app.json
eas.json
Please complete the following information:
For build issue give the output of the following command
npx react-native info
The text was updated successfully, but these errors were encountered: