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
// The action records a timestamp representing the last modification date of the entitlements file, so changes to the input must invalidate the build description.
/// The scope the task should use to evaluate build settings.
25
-
letscope:MacroEvaluationScope
26
-
27
24
/// The merged entitlements.
28
25
letentitlements:PropertyListItem
29
26
30
27
/// When performing a simulator build, we will have both signed and simulated entitlements; this enum indicates which variant of entitlements this task action is processing.
31
28
/// macOS and device builds will normally have only signed entitlements.
32
29
letentitlementsVariant:EntitlementsVariant
33
30
31
+
/// Whether unsafe modification of entitlements during the build should be allowed.
32
+
letallowEntitlementsModification:Bool
33
+
34
+
/// The destination of the processed entitlements.
@@ -257,7 +260,7 @@ public final class ProcessProductEntitlementsTaskAction: TaskAction
257
260
// Updating entitlements is not something that is actively encouraged or supported, however, this is a compatibility pain point for certain projects that we need to maintain some ability to do this. A better approach is to plumb this through the system so that we can track this as a proper dependency mechanism, potentially through our virtual task producers... however, until then, we enable this functionality for those existing clients.
258
261
259
262
// Also, we never modify the signed entitlements when building for simulators and ENTITLEMENTS_DESTINATION is __entitlements, since those are only expected to contain get-task-allow; see rdar://55324156.
outputDelegate.emitError("Entitlements file \"\(entitlementsFilePath.basename)\" was modified during the build, which is not supported. You can disable this error by setting 'CODE_SIGN_ALLOW_ENTITLEMENTS_MODIFICATION' to 'YES', however this may cause the built product's code signature or provisioning profile to contain incorrect entitlements.")
284
287
return.failed
285
288
}
@@ -391,12 +394,13 @@ public final class ProcessProductEntitlementsTaskAction: TaskAction
0 commit comments