[release/10.0] Revert Entitlement related changes from #116659 #119920
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.
Backport of #119824 to release/10.0
This PR reverts a change to the apphost writer that preserves the entitlements of the incoming apphost.
/cc @agocke @jtschuster
Customer Impact
If entitlements are preserved on the apphost, the Swift backtrace functionality is enabled. This causes a native callstack to be printed whenever a crash is produced. For crashes in native code, this is fine. For crashes in managed code, we have our own callstack dumping routine, and the Swift one is confusing for .NET users.
This change goes back to not preserving entitlements. As a result, users who want to fully sign and notarize their .NET binaries for Apple platforms will have to re-add required entitlements.
Regression
Testing
Manual verification.
Risk
Low. Mostly a revert to the previous behavior.