bazelbuild / bazelbuild/rules_apple

Directions for provisioning entitlements that require hardened runtime

Open
#2,560 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Starlark
Stars
593
Forks
334
Avg merge
16h 48m
Merged PRs (30d)
9

Description

Repro here: https://github.com/ed-irl/bazel-ios-codesigning-repro. You must make some changes to the repo code (outlined in the README.md) attempt to run the signed app on a device to reproduce the bug.

The code signing profile actually does seem to work, but when you attempt to launch it on a device the signature fails to verify with a message: `Failed to verify code signature of /var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.0SjU0G/extracted/TestBazel.app : 0xe8008015 (A valid provisioning profile for this executable was not found.)`

The repro doesn't contain an example using manual profiles, but in the project I'm working on I was also unable to get verifiable provisioning to work with manual signing (with the same error).

Contributor guide

Open the contributing guide

Research direction

Start with the linked bazel-ios-codesigning-repro repository and follow its README.md, making the listed changes before installing the signed app on a device. Confirm the 0xe8008015 verification failure and compare the automatic and manual provisioning cases; done means identifying actionable provisioning directions or a reproducible rules_apple fix.

Written by the indexing model from the issue text.

Assessment

Domain
build-system, mobile-dev, security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.