Are you referring to the "Sign to Run Locally"? If so, then the issue here is that local signing doesn't maintain a proper "relationship" between builds, so the system is forcing you to approve the build again because it appears to be an entirely "different" app. I'm using a custom build system, not XCode, so the build pipeline calls codesign manually for ad-hoc signing. I don't think this will happen if you're using one of our signing methods. In that case, the system should treat the new build replacing the old build the same way it would treat any other app update. It's good to know, thanks! However, this approach still involves user interaction, which is not really suitable for a stateless CI executor...