Bitrise Build Issue Report template
Description of the issue
When running the build and archive step, I get the following error:
❌ error: exportArchive: "MyApp.app" requires a provisioning profile with the Associated Domains, Push Notifications, Sign in with Apple, and Access WiFi Information features.
❌ Error Domain=IDEProvisioningErrorDomain Code=9 ""MyApp.app" requires a provisioning profile with the Associated Domains, Push Notifications, Sign in with Apple, and Access WiFi Information features." UserInfo={IDEDistributionIssueSeverity=3, NSLocalizedDescription="MyApp.app" requires a provisioning profile with the Associated Domains, Push Notifications, Sign in with Apple, and Access WiFi Information features., NSLocalizedRecoverySuggestion=Add a profile to the "provisioningProfiles" dictionary in your Export Options property list.}
However, I’ve triple-checked that the App ID and provisioning profiles found in the Apple Developer portal all contain the above profiles.
A few lines above that error, I also find this line, also confirming that Bitrise has detected those capabilities:
com.myapp: [com.apple.developer.networking.wifi-info aps-environment com.apple.developer.applesignin com.apple.developer.associated-domains]
Environment:
Today, macOS
If on Bitrise.io: which stack? If not on Bitrise.io: on what operating system? (Plus any other information you can share)
Xcode Archive & Export for iOS v3.2.0
Reproducibility
- Does a “Rebuild” help? (You can trigger a rebuild from the Build’s page, by clicking the “Rebuild” button in the top right corner of a finished build) : NO
-
Does a rebuild without caches help? (You can remove the
Cache:Pull
andCache:Push
steps temporarily to not to use the cache, or you can delete all the caches on theSettings
tab of the app. : NO - Does the issue happen sporadically, or every time? : every time
- Does upgrading the build Step to the latest version help? : NO
- When did the issue start? : I have only tested this today
Local reproduction
_Can it be reproduced on your own Mac/PC by following our local debug guide? No