fix(network): bypass Cloudflare bot protection using WKWebView #8
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
capabilitiesfield to Organization modelProblem
Cloudflare recently started blocking requests from URLSession due to TLS fingerprint mismatch. The
cf_clearancecookie is tied to browser TLS fingerprints, so simple HTTP clients (URLSession, curl) cannot pass JavaScript challenges even with valid session keys.Solution
Created
WebViewNetworkServiceusing WKWebView which shares Safari's TLS stack. WKWebView automatically handles Cloudflare JS challenges and has the correct TLS fingerprint that Cloudflare expects.The service polls page content until valid JSON is detected, handling the delay while Cloudflare challenges complete.
Additional Fixes
capabilitiesfield to Organization model withhasChatCapabilityhelperUsageServiceandAppModelto prefer organizations with "chat" capabilitytimeoutcase to NetworkError enumActortoSendableconstraint to support @mainactor classesTest plan
🤖 Generated with Claude Code