Request storage access in iframe connect flow

[Larkooo]

Summary\n- Request Storage Access API in iframe connect flow before completing connect/skip\n- Allows third-party storage (cookies/localStorage) to persist across restarts in WKWebView\n\n## Testing\n- Not run (requires device/WebView testing)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
controller-example-next	Ready	Preview	Feb 5, 2026 5:33pm
keychain	Ready	Preview	Feb 5, 2026 5:33pm
keychain-storybook	Ready	Preview	Feb 5, 2026 5:33pm

[claude]

---

Code review

No issues found. Checked for bugs and CLAUDE.md compliance.

---

[claude]

Claude finished @Larkooo's task —— View job

---

Analyzing PR and updating documentation

I'll analyze the Storage Access API changes and update the documentation accordingly.

Tasks:

• Review the changed file to understand Storage Access API implementation
• Explore docs-repo structure and existing documentation
• Determine if documentation updates are needed
• Update relevant documentation files if necessary

Analysis:
The PR adds Storage Access API support to solve a specific iOS/WebView issue where third-party cookies and localStorage don't persist across app restarts. The implementation:

1. Calls requestStorageAccess() in both Connect and Skip flows when in iframe context
2. Only affects mobile/WebView users (not standalone web users)
3. Improves persistence of authentication state in iOS apps using WKWebView

Documentation Status:
After reviewing the existing documentation, I found that Storage Access API handling is already well-documented in the configuration.md file. The existing documentation covers:

• Storage Access API detection and management
• Cross-domain iframe functionality
• Browser compatibility notes for Safari/Chrome/Firefox
• The controller.open() standalone flow that establishes first-party storage

The changes in this PR align perfectly with the existing documentation and don't introduce new user-facing functionality that requires documentation updates. The Storage Access API call is an implementation detail that improves reliability of existing functionality rather than adding new features.

Conclusion: No documentation updates are needed. The existing documentation already covers Storage Access API functionality and this PR simply improves the reliability of that existing behavior for iOS/WebView users.

---