Skip to content

build(ios): declare standard encryption and bump the build number to 22 - #2989

Merged
datlechin merged 2 commits into
mainfrom
build/ios-encryption-declaration
Sep 18, 2026
Merged

datlechin merged 2 commits into
mainfrom
build/ios-encryption-declaration

Conversation

@datlechin

Copy link
Copy Markdown
Member

Summary

Two build settings for the first App Store submission of the iPhone and iPad app.

  • ITSAppUsesNonExemptEncryption goes from NO to YES. The app bundles OpenSSL, libssh2 and BoringSSL for SSH tunnels and TLS connections to database servers, which is standard encryption in addition to what iOS provides. The owner decided to declare it. App Store Connect now asks the export compliance questions for each build; the answer is standard encryption algorithms, no proprietary cryptography.
  • CURRENT_PROJECT_VERSION goes to 22. App Store Connect already has 1.0 builds up to 21, and 21 was uploaded from a local bump that was never committed, so the next upload has to be 22.

No CHANGELOG entry: neither change is visible in the app.

Verification

The Release archive built from this branch carries ITSAppUsesNonExemptEncryption = true and CFBundleVersion = 22 in its Info.plist.

@datlechin
datlechin merged commit 232e8da into main Sep 18, 2026
4 of 6 checks passed
@datlechin
datlechin deleted the build/ios-encryption-declaration branch September 18, 2026 17:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant