search

microsoft / azure-pipelines-tasks

Tasks for Azure Pipelines
https://aka.ms/tfbuild
MIT License
3.5k stars 2.61k forks source link

Auto signing for XCode #18226

Closed FadwaZaghloul closed 10 months ago

FadwaZaghloul commented 1 year ago 
          Hello @alombard

I have followed your advices, but it still displays 2 errors:

error: No profiles for 'com.a.b.c' were found: Xcode couldn't find any iOS App Development provisioning profiles matching 'com.a.b.c'. Automatic signing is disabled and unable to generate a profile. To enable automatic signing, pass -allowProvisioningUpdates to xcodebuild. (in target 'c' from project 'A')

error: No profiles for 'com.a.b.c.intentsExtension' were found: Xcode couldn't find any iOS App Development provisioning profiles matching 'com.a.b.c.intentsExtension'. Automatic signing is disabled and unable to generate a profile. To enable automatic signing, pass -allowProvisioningUpdates to xcodebuild. (in target 'intentsExtension' from project 'A')

All of 2 imported profiles are valid, because if Im doing manual signing using 1 of them - it displays single error, that another profile is missing.

Also I noticed that command performed by XCode Task is the following:

/usr/bin/xcodebuild -sdk iphoneos -configuration Release -workspace /Users/runner/work/1/s/A.xcworkspace -scheme B archive | /usr/local/lib/ruby/gems/2.7.0/bin/xcpretty -r junit --no-color

There is no "-exportOptionsPlist" param appended to "xcodebuild". So it was ignored by XCode task. I have tried to put that param manually in command line, but "xcodebuild" says that using "scheme" param is not allowed to be used together with "exportOptionsPlist".

Did you face similar issue in your case?

Thank you, Alex.

CC @kanakaraju043

Originally posted by @svarnik in https://github.com/microsoft/azure-pipelines-tasks/issues/8811#issuecomment-747433858

RM-Eric commented 1 year ago

I am running in to this as well. Is automatic signing for production not supported? I can successfully sign with manual signing, but when automatic signing is selected the pipeline does not see the provisioning profile despite being installed in a previous step.

jdwirrenga commented 1 year ago

Also posted here, hopefully someone will look at these at some point.

github-actions[bot] commented 10 months ago

This issue is stale because it has been open for 180 days with no activity. Remove the stale label or comment on the issue otherwise this will be closed in 5 days