Azure-pipelines-tasks: Xcode builds suddenly failing with message 'error: <pod> does not support provisioning profiles

[christoferlof]

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

https://developercommunity.visualstudio.com/content/problem/508973/xcode-builds-suddenly-failing-with-message-error-d.html

[davidstaheli]

Thanks for reporting this @christoferlof. You reached the right people and we're investigating ASAP.

[jboisjo]

Same issue for us!

[madhurig]

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.

[maximeferron]

Same thing for us at CAE pipelines, pipeline error with the same behaviour

[davidstaheli]

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?

echo "uninstalling all cocoapods versions"
sudo gem uninstall cocoapods -ax
echo "installing cocoapods version 1.5.3"
sudo gem install cocoapods -v 1.5.3

[tigran-stdev]

@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.

[christoferlof]

@DavidStaheli confirmed. We now have green builds again 👍

Downgrading CocoaPods fixes the problem

[tmzblue]

@DavidStaheli we were struggling with this since the beggining of the month, now everything is green again ✔. Thanks a lot.

[hugo-retro]

@DavidStaheli We are coming at an awkward point. Currently busy moving over our apps to azure pipeline. Our react native ios based one builds funnily enough without issue. But our pure swift one does not. Cocoapods 1.5.3 makes no difference.

[hugo-retro]

Found a solution to our project. First, ensure you pod file has the following post-install section:

platform :ios, '9.0'

# Comment the next line if you're not using Swift and don't want to use dynamic frameworks
use_frameworks!

#--- This was what we had missing ---
post_install do |installer|
  installer.pods_project.targets.each do |target|
    target.build_configurations.each do |config|
      config.build_settings['EXPANDED_CODE_SIGN_IDENTITY'] = ""
      config.build_settings['CODE_SIGNING_REQUIRED'] = "NO"
      config.build_settings['CODE_SIGNING_ALLOWED'] = "NO"
    end
  end
end


target <your project> do
  <your pods>
end

Next we used the latest cocoapods version which worked (1.7.0.beta.3). So have this as a script before the build process:

echo "uninstalling all cocoapods versions"
sudo gem uninstall cocoapods -ax
echo "installing cocoapods version latest"
sudo gem install cocoapods --pre

[madhurig]

Thanks for reporting the issue and providing your solutions. We are closing this issue since it is resolved. We are looking into better ways to providing this integration with CocoaPods and signing as a future enhancement.

[esunilkumare]

@hugo-retro Your solution helped me solve same issue on an Ionic iOS build created from Azure Build Pipelines

[chimeraTrijay]

Found a solution to our project. First, ensure you pod file has the following post-install section:

platform :ios, '9.0'

# Comment the next line if you're not using Swift and don't want to use dynamic frameworks
use_frameworks!

#--- This was what we had missing ---
post_install do |installer|
  installer.pods_project.targets.each do |target|
    target.build_configurations.each do |config|
      config.build_settings['EXPANDED_CODE_SIGN_IDENTITY'] = ""
      config.build_settings['CODE_SIGNING_REQUIRED'] = "NO"
      config.build_settings['CODE_SIGNING_ALLOWED'] = "NO"
    end
  end
end


target <your project> do
  <your pods>
end

Next we used the latest cocoapods version which worked (1.7.0.beta.3). So have this as a script before the build process:

echo "uninstalling all cocoapods versions"
sudo gem uninstall cocoapods -ax
echo "installing cocoapods version latest"
sudo gem install cocoapods --pre

how do I add this in my pod file, it is not in my directory, and if it is created after run time how do I create it after installation in azure devops

[Juandi-M]

Found a solution to our project. First, ensure you pod file has the following post-install section:

platform :ios, '9.0'

# Comment the next line if you're not using Swift and don't want to use dynamic frameworks
use_frameworks!

#--- This was what we had missing ---
post_install do |installer|
  installer.pods_project.targets.each do |target|
    target.build_configurations.each do |config|
      config.build_settings['EXPANDED_CODE_SIGN_IDENTITY'] = ""
      config.build_settings['CODE_SIGNING_REQUIRED'] = "NO"
      config.build_settings['CODE_SIGNING_ALLOWED'] = "NO"
    end
  end
end


target <your project> do
  <your pods>
end

Next we used the latest cocoapods version which worked (1.7.0.beta.3). So have this as a script before the build process:

echo "uninstalling all cocoapods versions"
sudo gem uninstall cocoapods -ax
echo "installing cocoapods version latest"
sudo gem install cocoapods --pre

The real and elegant solution for this and other projects.

[Carolhaha]

@davidstaheli @hugo-retro Hi, I tried both solutions, but all these two will stuck in the uninstalling step without moving on, are there anything else I need to take care to make sure it keep going?