You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
log.Debugf("setting CODE_SIGN_STYLE unspecified for target (%s), defaulting to `Manual`", targetName)
Ahoy! Found this while debugging my workflow.
XCode projects that that don't specify CODE_SIGN_STYLE use Automatic code signing per iOS defaults.
Steps like xcode_archive end up setting up Manual code signing for these projects as a result, leading to unexpected code signing issues later in the build.
Not sure if other Apple platforms have different defaults for CODE_SIGN_STYLE.
Explicitly setting CODE_SIGN_STYLE is a workaround.
The text was updated successfully, but these errors were encountered:
Ahoy @jfrndz - As you mentioned, the code only falls back to manual code sign style if CODE_SIGN_STYLE is not defined in the project settings. Can you help us understand how this can happen in a project (that there is no code sign style defined)?
Side note: if you want to avoid unexpected code signing issues, we recommend disabling the automatic_code_signing input entirely - with this setting, the step won't modify any code signing setting in the project nor install any certificates and profiles.
go-xcode/autocodesign/projectmanager/projecthelper.go
Line 322 in 7e1bc5b
Ahoy! Found this while debugging my workflow.
XCode projects that that don't specify CODE_SIGN_STYLE use Automatic code signing per iOS defaults.
Steps like
xcode_archive
end up setting up Manual code signing for these projects as a result, leading to unexpected code signing issues later in the build.Not sure if other Apple platforms have different defaults for CODE_SIGN_STYLE.
Explicitly setting CODE_SIGN_STYLE is a workaround.
The text was updated successfully, but these errors were encountered: