> Historical build-12/13/14 record. Current continuation: [CURRENT-STATUS.md](CURRENT-STATUS.md). > Do not infer current availability, installed versions or authorization from the old sections below. # HORST Secret Chat — iOS continuation, 28 October 2026 ## Latest checkpoint — build 14, 28 October 2026 Server/Web/own Onion 0.6.6 are live, verified at 19:38 UTC. Public source commit f44fc3dc4f065b1b8fc68b3c17aa6e69fc9435e6; source ZIP SHA256 608f637e631a31d53ac7c0ad38f65f7092eb05c7731ddb6c8e1f46157485774b. Old 0.6.5 archive preserved; no server history archive. New inbox capability route is live before mobile distribution. APNs and real accounts untouched. Android release APK/AAB build14 complete and signed, byte/signature/16KiB QA passed. Not uploaded to Play. Existing phones require the separately verified debug-signed test-device APK to preserve accounts (SHA da53afe41328b0a163b8f592d13f23442d5a9c9f08c0ca8cb37c126c3d2613fe). Both Xiaomi serials were unavailable via ADB; no phone was changed. Coordinator reservations were released with actual evidence. No PIN attempted. Use fresh coordination for any later attempt; never clear data or install release-signed APK over the existing debug installation. iOS build14 IPA passed Apple validation and upload at 19:28 UTC. Upload ID d4933af8-4739-4987-b38c-0584552b35ca, processing at last read. Do not re-upload. Once VALID, assign to the existing internal Martin group and use build14 voice/ retained-direct test notes. Physical iPhone voice acceptance remains open. Build13 is still internal IN_BETA_TESTING and external WAITING_FOR_BETA_REVIEW in Alle anderen; do not remove groups/testers or expire prior builds. No public App Store release. Build14 uses unchanged B13 native code, new web resources, build number and re-signing; native frameworks/profile/entitlements unchanged. Initial code/lab security review: docs/PRE-AUDIT-2026-10-28.md. Synthetic proof shows local-storage control can reset the PIN throttle. iOS has no dedicated native rotating Vault key (browser layer still PIN-encrypted). These are open scoped hardening findings, not a remote PIN bypass or plaintext-vault proof. Production npm audit reports zero advisories. Full post-update device review is still pending. Report does not claim independent certification. ## Current work — build 14, voice playback and retained direct messages The user confirmed iPhone voice playback never starts (time remains zero). New in-memory WebAudio controls replace native HTML audio controls on iOS. Native iOS 27 simulator tests pass WebM/Opus and MP4/AAC start, pause, resume, seek, DOM reattachment, disposal, invalid audio and cancellation while decoding. The original physical-device failure was NOT reproduced on a real iPhone; physical verification of the replacement remains pending. User additionally requests a per-message no-expiry choice for direct chats on iOS and Android. Added without changing existing messages, finite defaults, group TTL limits or the seven-day undelivered relay bound. A separate `/api/inbox/retained` endpoint protects against older clients rejecting and ACKing retained direct messages. Deploy server support before distributing 14. No device-version history is stored. No server conversation archive is added. 90 unit tests pass; shared UI tests pass iOS/Android/web retained and timed messages, original signatures and ACK cleanup. Build 14 is still being prepared: do not upload the pre-compatibility IPA/APK. Native iOS Swift/framework code is unchanged from build 13: resource-update packaging, CFBundleVersion 14 and re-signing, not a new native compilation. Final signed bundle, embedded assets and Apple validation must be checked. The user also authorized a small technical pre-audit after both app updates. Document findings with severity and proof; no independent-certification claim. ## Current checkpoint — external TestFlight submission, 28 October 2026, 18:15 UTC Build **0.6.6 (13)** is assigned to the existing external group **Alle anderen** (3234d379-b4fd-4781-bcf8-d6833a8b940f), and Apple accepted its beta review submission (HTTP 201). Readback: WAITING_FOR_REVIEW / WAITING_FOR_BETA_REVIEW. The internal Martin group also has build 13 / IN_BETA_TESTING. User explicitly requested external distribution and subsequently reported successful operation. Auto-notification is enabled for this build after approval, not for every upload. Group count was zero testers. Its public link was enabled by a concurrent user change; this workflow did not change that setting. Do not undo it. No public App Store submission and no Android production upload occurred. The user specifically authorized the APNs credential and it was created in Apple Developer: **35FXF6Z9JK**, Production, one topic **de.smfuture.smchat**, team 7VG938P5DX. Installed protected on the own HORST relay; only Secret Chat service restarted. Chat/main HORST health HTTP 200. Server receipt: `/opt/horst-secret-chat/deploy-evidence/apns-20261028.json`. The protected server backup matched the downloaded key's public DER SHA256. Transient downloaded key removed. Never include key material in source or Library. One production iOS registration is now present (previously none). The user first reported the recovery dialog again, then clarified build 13 was not installed, then reported that it worked very well. This is operator acceptance, not a separate instrumented foreground/background test. The targeted manual test preflight found no token for the previously authorized account names and did not send to the other registration. Do not claim APNs HTTP 200 or a captured device notification. Do not send arbitrary test pushes to a newly observed identity. A separate synthetic Apple-review account was registered and its login verified. Its 256-character recovery key is supplied only in Apple's demo-password field; review notes explain the recovery flow and choosing a new local PIN. Protected backup on own server. Never print, archive or upload it elsewhere. Real accounts remain unchanged. Six beta descriptions, contact information and build notes are in App Store Connect. Arabic API locale is ar-SA. Beta privacy supplement is published and byte-verified: https://chat.horst-fahrt.de/docs/privacy-beta.html SHA256 7a331ec1a229d946ab3d9954dfe8503d485c1d20a976e860f6d6dcf542938e9a. The existing privacy page links to it and no longer calls iOS unbuilt: SHA256 4aa55b4967f150967e057250cae076c597509056101527dd21d0c18057389ac5. Only these documentation files changed in the live 0.6.5 dist; no application assets, public 0.6.5 source archive, website presentation or other app changed. Receipt `/opt/horst-secret-chat/deploy-evidence/beta-privacy-20261028/receipt.json`. TestFlight's own install/usage/crash/feedback collection is disclosed separately from the messenger's absence of analytics SDKs. Production legal/export/store preparation remains a separate open task. TestFlight can auto-update beta builds, but will not automatically switch users to the App Store production app. They must install the App Store version once; do not first delete the beta. Account/key/chat preservation during that transition is a required future acceptance check, not yet proven. ## Historical checkpoint — before APNs setup and tester confirmation The user requires working notifications before another tester release. Build 13 had already uploaded at 02:00:34 UTC before that instruction; Apple processed it as VALID (b17999ec-8b6e-432b-8309-66b6648fc63e), but it remains MISSING_EXPORT_COMPLIANCE and is NOT assigned to the private Martin group. Fresh readback at 02:06:27 UTC: that group contains only build 12 and does not have access to all builds. No further release/assignment until APNs is configured and actual iPhone reception is checked. Do not expire the existing build without an explicit reason or replace it with an unverified push build. Build 13 fixes automatic redisplay of an unacknowledged recovery key on foreground resume, while preserving its encrypted backup and manual access in Settings. New valid incoming iOS messages trigger a generic foreground notice plus a bundled local sound; duplicates, own messages, history and control traffic stay silent. Recovery/export/resume, four registration-failure scenarios and the real isolated relay/two-browser iOS bridge regression passed. The native iOS code compiled, archived and signed. This does NOT prove audible reception on the real iPhone. APNs remains unconfigured and needs the specific approval described below. No key was created by an alternate tool. Proposed credential: HORST Secret Chat APNs Production, Production, topic-specific de.smfuture.smchat only, stored protected on the own HORST server. No message contents or decryption keys in pushes. Build 13 IPA: 4301511 bytes, SHA256 532639719dd2fe562efa6d7662ad32587387edd6436b385ff2e00085fd1ebf09. Mac export-b13/App.ipa and off-Mac backup C:/SMFutureBuild/downloads/HORST-Secret-Chat-0.6.6-build13-B13-candidate.ipa. Full archive/dSYMs backup: HORST-Secret-Chat-066-build13-xcarchive.tar.gz, 10752046 bytes, SHA256 62d7c75cde45df00e09991857434df936bd849a7c0241e0896d38ba1a0cb2377. Explicit upload and validation JSON have zero errors; temporary ASC key removed. Android build 13 also built and signature-verified. APK 34749349 bytes, SHA256 3d047bf2e292f35bfb8fd7c1c00d30de07c697c1b6d8b63d850aca98656ded80; AAB 17308200 bytes, SHA256 f39b29098e5c2607a5e8172e87deab6967b922a2b409bc94db7553281e87e9aa. Both use expected certificate 435403f9d69bb46a1ab95222c80dc4da1a1877ad27a5878323be3402bcf3d460. CRC/assets/native bridge/64-bit 16KiB checks passed. Android was NOT uploaded to Play or installed on the Xiaomis during this run. Native Android push-erasure QA R4 and R6 now PASS on the private Google Play API36 ARM64 emulator. Real FIS/FCM synthetic identity, deletion, pending-request failure and retry passed. R6 additionally disabled both guest network transports, proved local credential erasure despite offline failure, force-stopped the app, restored network and proved retry after a new process. Own ADB 5039/emulator 5592 stopped; no real users, devices or foreign processes touched. R5 failed at FCM authentication before deletion and is retained as a failed attempt. See ANDROID-MAC-QA-R6.json. TestFlight updates: testers can enable Automatic Updates for the individual app; this is tester-controlled, not a centrally forced install. Release only verified builds to the group. Do not enable blind automatic distribution of every upload. Source: https://testflight.apple.com/ (checked 28 October 2026). The following earlier build-12 sections are retained as historical evidence. Build 12 is still the tester-visible build, not the latest candidate. Current user instruction: Android production; iOS **TestFlight only**. No App Store review submission. Existing shared rented Mac only, no extension or new rental. ## Current verified result 0.6.6 / build 12 is uploaded and processed as VALID. App Store Connect app 6827768757, bundle de.smfuture.smchat, team 7VG938P5DX. Build ID cee0f9a4-d0b2-4d40-9711-aa08aacac4f4. Internal state IN_BETA_TESTING. Private internal group 091bb263-f89a-4512-8d86-2be4110afa36 contains build 12 and exactly one tester: the verified account holder Martin. Invitation state INVITED. No public link, external tester group or App Store submission. The current signed IPA is export-r4/App.ipa, SHA256 c5896ef440287de7716796450bc7f87c21d1522de1d768b8a2b7b89e345078f6, 4286293 bytes. It is copied and hash-checked on the build PC at C:/SMFutureBuild/downloads/HORST-Secret-Chat-0.6.6-build12-R4-candidate.ipa. The R4 xcarchive including dSYMs is also backed up there as HORST-Secret-Chat-066-build12-R4-xcarchive.tar.gz (10710879 bytes, SHA256 9006e479a7bfa065993ba8e628a96779b97d2c30d77ce2d870552ab89ed0c0e6). Earlier R1–R3 exports must not be used. R3's altool process incorrectly exited 0 despite four product-errors. Its initial success receipt was wrong and has been corrected. R4 fixes upstream Tor bundle metadata (MinimumOSVersion 15.0; valid three-part bundle versions, original Tor version retained separately). Library code bytes are unchanged. Upload now checks both the JSON product-errors and explicit success-message, then ASC processing. R4 validation/upload have zero product-errors; ASC upload COMPLETE has no warnings. ## Export scope The binary omits ITSAppUsesNonExemptEncryption and ITSEncryptionExportComplianceCode so ASC asks its questionnaire. It does not claim no encryption. Source inspection confirms published standard primitives ML-KEM-1024, ML-DSA-87, AES-256-GCM, HKDF/SHA-512, SHA-256, and published Tor protocols. The message protocol/source is publicly available. This test is for the owner's internal TestFlight use in Germany, not distribution on the French App Store. Apple's documentation requires third-party standard-crypto documentation only for French App Store distribution. The declaration API rejected the exact answers (proprietary=false, thirdParty=true, France=false) as not requiring a declaration. Build 12 was therefore marked usesNonExemptEncryption=false for this documented scope, and ASC changed from MISSING_EXPORT_COMPLIANCE to READY_FOR_BETA_TESTING, then IN_BETA_TESTING. This is not a worldwide legal/export clearance. Re-evaluate before French or other public distribution; do not invent CCATS/ANSSI documents. Sources checked 28 October 2026: - https://developer.apple.com/help/app-store-connect/reference/app-information/export-compliance-documentation-for-encryption/ - https://developer.apple.com/help/app-store-connect/manage-app-information/overview-of-export-compliance/ - https://developer.apple.com/documentation/bundleresources/information-property-list/itsappusesnonexemptencryption - https://csrc.nist.gov/pubs/fips/203/final - https://csrc.nist.gov/pubs/fips/204/final ## Outstanding iPhone work APNs server configuration is absent. The only current Apple keys are restricted to other HORST apps; they must not be reused. Preparing a new Secret Chat key in the Apple portal was rejected by automatic approval review because specific action-time consent for a persistent security credential was not yet given. Do not bypass via API, alternate credentials or tool changes. Required scope: production, topic-specific de.smfuture.smchat only, name HORST Secret Chat APNs Production; protected storage on the own HORST server for generic notifications, never content. After explicit approval, configure SMCHAT_APNS_KEY_FILE, KEY_ID, TEAM_ID and TOPIC for the Secret Chat service only. Other apps and their push keys stay untouched. Native Tor R8 simulator tests passed own onion HTTP 200, pause/resume with one Tor engine, cancellation and path/header/method restrictions. Physical iPhone tests are still pending. Test notes explicitly disclose missing background push and this QA boundary. Verify PIN/lock, recovery file sharing, camera, microphone, attachments, peer recovery, group owner rename, generic pushes and Tor on the iPhone. Use only synthetic accounts. Do not delete or take over Martin_R or rabbi1384. TestFlight does not require USB trust to the Windows PC. Do not reset the iPhone's trust/privacy settings. All source/build receipts must remain off the rented Mac. Own Mac root: /Users/m1/horst-secret-chat-066; shared locks and other apps must remain untouched. Temporary signing and ASC private keys were removed after each job.