azure-pipelines-tasks: Xcode builds suddenly failing with message 'error: does not support provisioning profiles
Question, Bug, or Feature?
Type: Bug
Enter Task Name: Xcode@5
Environment
- Azure Pipelines
- Hosted Agent
Issue Description
iOS Swift app with some external CocoaPods dependencies. Built fine for weeks, since March 28th (CET) suddenly failing with error code 65.
error: <podname> does not support provisioning profiles. <podname> does not support provisioning profiles but provisioning profile <distrprofile> has been manually specified. Set the provisioning profile value to "Automatic" in the build settings editor. (in target '<podname>')
Changing provisioning mode to “Automatic” doesn’t resolve it as suggested.
Builds that passed on or before March 27th are now failing when resubmitted.
Update to task-lib 2.8.0 in tasks using iOS signing and secure files was merged to master on the 27th. Coincidence?
Error logs
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 1
- Comments: 24 (4 by maintainers)
Found a solution to our project. First, ensure you pod file has the following post-install section:
Next we used the latest cocoapods version which worked (1.7.0.beta.3). So have this as a script before the build process:
We’re investigating whether this could be caused by rolling out the latest version of CocoaPods last week. We’re trying to reproduce the error. Can someone please run this script as part of their pipeline to see if rolling back to a previous version of CocoaPods patches the problem?
Thanks for reporting this @christoferlof. You reached the right people and we’re investigating ASAP.
@hugo-retro Your solution helped me solve same issue on an Ionic iOS build created from Azure Build Pipelines
The update to the task-lib 2.8.0 hasn’t deployed yet, so that is unrelated. We are investigating. Thanks for reporting the issue.
I changed the script to make sure already existing post_install entries will be kept:
Personally? Turn off Flutter.
Thanks for the solution. I updated my Podfile with the content provided by you but I am getting this error now.
@DavidStaheli we were struggling with this since the beggining of the month, now everything is green again ✔. Thanks a lot.
@DavidStaheli Hi, I have just tried to rolling back to 1.5.3 version of CocoaPods as you requested and seems it solved the issue in my pipeline.