How to fix ' *pod* does not support provisioning profiles' in azure devops build agent

11
votes

I currently have problem with my pipeline in Azure Devops. Since March 27th, I got the error:

error: Alamofire does not support provisioning profiles. Alamofire does not support provisioning profiles, but provisioning profile prov profile name has been manually specified. Set the provisioning profile value to "Automatic" in the build settings editor. (in target 'Alamofire')

I have this error for all my pods.

The code: The exact same branch have built correctly the day before.

Xcode version: I know the agent is still on Xcode 10.1 and I haven't update my project to 10.2 so it should be good.

Provisioning profiles: Is valid.

Suspicion : Apple released a new version of Xcode and Swift on this day. Microsoft also update Agents on this day: github.com/Microsoft/azure-pipelines-tasks/commit/1b019b9f65202d65ac58150bff6514938b53ff78#diff-93b5db3773bba1013dce9d814869dffd

Soooo, anyone have an idea? What is wrong with my pipeline ?

1
swiftxcodeazureazure-devopsprovisioning-profile
Can you provide the actual relevant code? – JJJ
Error: /usr/bin/xcodebuild failed with return code: 65 – Maxime Lapointe
did you ever figure it out? – adrian.coroian
Can you please mark my answer as the correct answer? – willhess

1 Answers

28
votes

The issue is that the newest version of Cocoapods is trying to sign the frameworks.

Add the following code to your podfile

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