Skip to content

fix(ios): enable native messaging on app-bound domains - #525

Merged
markbang merged 1 commit into
mainfrom
codex/ios-app-bound-bridge
Nov 18, 2026
Merged

markbang merged 1 commit into
mainfrom
codex/ios-app-bound-bridge

Conversation

@markbang

Copy link
Copy Markdown
Collaborator

Summary

The iOS host declares WKAppBoundDomains but did not enable limitsNavigationsToAppBoundDomains on its WKWebView. WebKit consequently restricts JavaScript injection and message handlers, which the native login and file bridge depend on.

 let configuration = WKWebViewConfiguration()
+configuration.limitsNavigationsToAppBoundDomains = true

Evidence

  • Before: native acceptance reaches the welcome page, but the sign-in flow does not appear through the expected native bridge.
    After: enable the configuration required by WebKit's App-Bound Domains documentation. The same change compiles in the acceptance branch; this isolated PR runs the normal iOS simulator checks.
  • The host already restricts top-level navigation to its configured origin and opens external URLs in the system browser. Cross-origin embedded content remains supported by WebKit.

Merge Danger

Door: two-way

Blast Radius: iOS

This is required before rebuilding the App Store IPA. Native login acceptance continues separately in #523; a compilation pass is not a full device-login pass.

@markbang
markbang merged commit 4f575f9 into main Nov 18, 2026
8 checks passed
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