fix(mas): declare exempt encryption (skip App Store export-compliance prompt)#187
Open
oratis wants to merge 1 commit into
Open
fix(mas): declare exempt encryption (skip App Store export-compliance prompt)#187oratis wants to merge 1 commit into
oratis wants to merge 1 commit into
Conversation
App Store export compliance flagged the MAS upload ("missing export compliance")
and the France branch demanded a CCATS-style document upload. Markup's only
crypto is standard HTTPS/TLS (rustls — exempt), so set
ITSAppUsesNonExemptEncryption=false in the MAS bundle's Info.plist before
signing: the App Store then auto-clears export compliance with no prompt and no
France docs, matching the iOS app.
Also add an optional MAS_BUILD_NUMBER env that overrides CFBundleVersion —
needed when re-uploading the same marketing version (the store requires a
strictly higher build number).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
The first Mac App Store submission tripped the export-compliance flow: ASC showed "missing export compliance" on the build, and the France question routed to a heavyweight document upload (CCATS-style).
Markup's only cryptography is standard HTTPS/TLS (via
reqwestrustls-tls), used solely to talk to GitHub — i.e. exempt encryption. The iOS app already declares this withITSAppUsesNonExemptEncryption = NO; the Tauri Mac build didn't.Fix (
scripts/build-mas.sh, before signing):ITSAppUsesNonExemptEncryption = falsein the.appInfo.plist → App Store auto-clears export compliance (no per-upload prompt, no France declaration).MAS_BUILD_NUMBERto overrideCFBundleVersion(needed to re-upload the same marketing version with a higher build number).Verified on a fresh universal build (1.0.1 build 2): flag present, still
x86_64 + arm64, signed/sandboxed/profiled,codesign --verifypasses. macOS-only; no effect on the direct DMG.🤖 Generated with Claude Code