NEPacketTunnelProvider stopped connecting on arm macOS 14 during tests

Question

Created Nov ’24

Replies 1

Boosts 0

Participants 2

I have tests where I connect to NEPacketTunnelProvider. I run tests with circleci and fastlane, on self hosted intel and arm macs. I updated macs from macOS 13 to macOS 14 and the tests on arm stopped connecting, while the same tests on intel kept working as usual. Moreover, I noticed the tests don't work when run from circleci and fastlane. If I cancel the job and click "connect" myself on the app that stayed hanging from the cancelled tests, the connection will succeed. But if the tests are running, the connection will fails. Running the tests from xcode succeeds too.

These are the logs from the tunnel. Could you suggest me where to dig? Or maybe you can see the issue from the logs?

Tunnel logs when they fail

Boost

Answer 1

DTS Engineer OP

Apple

3w

I suspect that this is relevant:

Signature check failed: code failed to satisfy specified code requirement(s)

NE is trying to verify a designated requirement (DR) and that’s failing. This usually means that the code is built incorrectly, so that version N+1 doesn’t satisfy the DR recorded for version N. I talk about requirements, and how macOS uses DRs, in some detail in TN3127 Inside Code Signing: Requirements.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

0