Conversation
Move HTTP-related code into a standalone Http module for better modularity. This includes HttpClient, request/response types, TLS pinning infrastructure, and endpoint handling. The Split module now imports Http and uses adapter protocols for authentication and notifications. Co-authored-by: Cursor <cursoragent@cursor.com>
SDK Readiness Test Results ✅
Legend: 🟢 significant improvement | 🔴 significant regression | ⚪ inconclusive (p≥0.05) ios-test-mock
|
SDK Readiness Test Results ✅
Legend: 🟢 significant improvement | 🔴 significant regression | ⚪ inconclusive (p≥0.05) ios-test-mock
|
SDK Readiness Test Results ✅
Legend: 🟢 significant improvement | 🔴 significant regression | ⚪ inconclusive (p≥0.05) ios-test-mock
|
SDK Readiness Test Results ✅
Legend: 🟢 significant improvement | 🔴 significant regression | ⚪ inconclusive (p≥0.05) ios-test-mock
|
Tests moved and adapted
README added
SDK Readiness Test Results ✅
Legend: 🟢 significant improvement | 🔴 significant regression | ⚪ inconclusive (p≥0.05) ios-test-mock
|
Tests cover: - HttpError: isProxyOutdatedError logic, internalCode handling, code extraction - HttpDataRequest: data chunk accumulation, completion/error flows, pinning credential fail handling Co-authored-by: Cursor <cursoragent@cursor.com>
Adds file references for all existing test files, mocks, and README.md so they are visible in Xcode's project navigator. Co-authored-by: Cursor <cursoragent@cursor.com>
SDK Readiness Test Results ✅
Legend: 🟢 significant improvement | 🔴 significant regression | ⚪ inconclusive (p≥0.05) ios-test-mock
|
SDK Readiness Test Results ✅
Legend: 🟢 significant improvement | 🔴 significant regression | ⚪ inconclusive (p≥0.05) ios-test-mock
|
|




iOS SDK
What did you accomplish?
How do we test the changes introduced in this PR?
Extra Notes