update_project_code_signing

Updated code signing settings from 'Automatic' to a specific profile

You shouldn't use update_project_code_signing.
Have you considered using the recommended way to do code signing: https://docs.fastlane.tools/codesigning/getting-started/?

update_project_code_signing
Supported platforms ios
Author @KrauseFx

Parameters

Key Description Default
path Path to your Xcode project
udid DEPRECATED! Use :uuid instead *
uuid The UUID of the provisioning profile you want to use *

* = default value is dependent on the user's system


Documentation

To show the documentation in your terminal, run

fastlane action update_project_code_signing

CLI

It is recommended to add the above action into your Fastfile, however sometimes you might want to run one-offs. To do so, you can run the following command from your terminal

fastlane run update_project_code_signing

To pass parameters, make use of the : symbol, for example

fastlane run update_project_code_signing parameter1:"value1" parameter2:"value2"

It's important to note that the CLI supports primative types like integers, floats, booleans, and strings. Arrays can be passed as a comma delimited string (e.g. param:"1,2,3"). Hashes are not currently supported.

It is recommended to add all fastlane actions you use to your Fastfile.


Source code

This action, just like the rest of fastlane, is fully open source, view the source code on GitHub


Back to actions