fix(ios): pin DiditSDK pod to 3.2.13 instead of tracking main#2094
Merged
Conversation
@didit-protocol/sdk-react-native's Expo plugin injects the Podfile entry pointing at .../sdk-ios/main/DiditSDK.podspec. On 2026-05-25 main was bumped to 4.0.0, which no longer satisfies the SdkReactNative.podspec constraint of `DiditSDK ~> 3.2`, so pod install fails on every iOS EAS build with a CocoaPods version conflict. Patch the plugin to use the 3.2.13 tagged podspec — the latest 3.2.x release that still ships the flat DiditSDK.xcframework + OpenSSL.xcframework the react-native-quick-crypto patch relies on for OpenSSL.
|
The latest updates on your projects. Learn more about Vercel for GitHub. 2 Skipped Deployments
|
…ments #2093 pinned the DiditSDK pod to 3.2.13, which gets pod install past the version constraint but introduces a new fault: VerificationError gained a .retryBlocked case starting in 3.2.10, and @didit-protocol/sdk-react-native@3.2.8's DiditSdkBridge.swift mapErrorType() switch only handles .sessionExpired / .networkError / .cameraAccessDenied / .unknown. Xcode errors out with "switch must be exhaustive" during the Fastlane step. 3.2.9 is the latest DiditSDK iOS release before the enum was extended, so the wrapper's 4-case switch is still exhaustive against it. Verified by diffing the swiftinterface across 3.2.8 / 3.2.9 / 3.2.10 / 3.2.13 — the .retryBlocked case lands in 3.2.10. The wrapper's other switches (VerificationStatus, VerificationResult) are unchanged across 3.2.x.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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
Cherry-pick of #2093 onto
qa.@didit-protocol/sdk-react-native's Expo plugin injects the iOS Podfile entry pointing athttps://raw.githubusercontent.com/didit-protocol/sdk-ios/main/DiditSDK.podspec. On 2026-05-25 thatmainbranch was bumped to 4.0.0, which no longer satisfies theSdkReactNative.podspecconstraintDiditSDK ~> 3.2. Every iOS EAS build now fails atpod installwith a CocoaPods version conflict.This patches the plugin to use the
3.2.13tagged podspec — the latest 3.2.x release that still ships the flatDiditSDK.xcframework+OpenSSL.xcframeworkthatpatches/react-native-quick-crypto+0.7.17.patchreuses for OpenSSL.Test plan
patches/is in the fingerprint inputs) completespod installwithout a DiditSDK version conflicthttps://claude.ai/code/session_013ovmPbLFvPhUCQq9qggyes
Generated by Claude Code