Repository navigation
|
I upload with Helm or the asc CLI. Why does the compliance guard now run before those commands, and which subcommands trigger it? |
Answered by
mjmirza
Nov 15, 2026
Replies: 1 comment
|
Before 2.4.0 the guard only recognised fastlane, eas, altool, notarytool, Transporter, Gradle publish tasks, bundletool and xcodebuild archive. A build sent with These now trigger the scan. Read only commands such as |
0 replies
Answer selected by
mjmirza
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Before 2.4.0 the guard only recognised fastlane, eas, altool, notarytool, Transporter, Gradle publish tasks, bundletool and xcodebuild archive. A build sent with
helm-asc apps <id> builds upload --submit,asc builds upload,asc submissions createor Codemagic'sapp-store-connect publishwent to App Store Connect, and with--submitstraight into review, without a scan.These now trigger the scan. Read only commands such as
helm-asc apps list,asc apps listorapp-store-connect fetch-signing-filesstay silent. The fixtures are inagent-os/hooks/app-store-compliance-guard-test.shunder theasc-cases.