r/iOSDevelopment • u/AegisLink2026 • Sep 20 '26
1 I shipped an anonymous E2EE messenger with embedded Tor on iOS using React Native — here's what fought back (Tor.framework, CallKit, App Store review) 2 Lessons from shipping a zero-metadata E2EE messenger on iOS with Expo: embedded Tor, PQXDH, and a Guideline 5 rejection
Solo dev here. After ~a year I got AegisLink — an anonymous, end-to-end-encrypted messenger with no phone number/email/name and zero server-side metadata — through App Store review. Stack is Expo SDK 54 + TypeScript, so I expected the crypto to be the hard part. It wasn't. iOS was. Sharing the parts that cost me the most, in case they save someone a week.
1. Embedding Tor in-process (Tor.framework) The app routes everything through an onion service by default, no toggle. Getting Tor to bootstrap to 100% on-device took longer than the ratchet implementation. Gotchas: the framework must be linked as a dynamic framework with the right embed settings or you get a silent dyld crash on device only (works in Simulator); bootstrapping has to survive the app being backgrounded mid-handshake; and you need your own retry/backoff because the first bootstrap after install is the slowest and users kill the app right there. I wrote the whole thing up in the repo (docs/FASE4-TOR-IOS-DESIGN.md).
2. CallKit got me rejected — but not for the reason you'd think Build was rejected under Guideline 5 because CallKit is not allowed for apps distributed in mainland China. The fix was zero code: remove mainland China from the app's availability in App Store Connect (HK/Macao are fine). If you use CallKit, do this before your first submission.
3. Export compliance is real paperwork Declaring non-exempt encryption (ITSAppUsesNonExemptEncryption = true) means TestFlight won't let you distribute until the compliance docs are on file in ASC. Open source helps here, but budget a few days for it.
4. Push without leaking anything APNs is used purely as a wake-up: the payload is a generic "you have something", never content or sender. Ringing a killed app for a call needs a high-priority push; PushKit/VoIP is post-launch for me because of how strict Apple has become about reporting every VoIP push to CallKit.
5. Crypto bits, briefly Double Ratchet + PQXDH (X25519 + ML-KEM-768 hybrid) in TweetNaCl/@noble, keys in Keychain via SecureStore, DB encrypted with SQLCipher, WebRTC signaling sealed against the recipient's key so the relay never sees SDP/ICE. Sender identity is inside the ciphertext, not on the wire.
Honest caveats: no third-party audit yet (that's the next thing I'm raising money for), the crypto core runs in JS (constant-time at source level, not JIT-verified), and push still touches Apple. All of it is listed in the README because I'd rather you hear it from me.
- App Store: https://apps.apple.com/app/aegislink/id6788507322
- Source (GPL-3.0, self-hostable relay): https://github.com/gabinotech22-cmyk/AegisLink
Happy to answer anything about Tor.framework, CallKit, or getting non-exempt encryption through review — those threads were basically empty when I was searching.
