Preserve HealthKit capability when re-signing apps#1762
Draft
jsilets wants to merge 1 commit into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Apps containing
com.apple.developer.healthkitlose HealthKit access when AltStore or AltServer re-signs them because AltSign does not register the matching App ID feature.Fix
Update AltSign to the commit that maps the HealthKit entitlement to Apple Developer Portal's HealthKit feature. AltStore's existing feature registration and signing flow handles the capability without additional Swift changes.
Depends on rileytestut/AltSign#45. This should remain a draft until that change is merged and the submodule pointer is updated to the upstream commit.
Related to #1518.
Testing
git diff --checkpasses.AltTeststarget fails before execution because its unchangedNukemodule search path cannot be resolved.On-device provisioning verification is still pending.