Skip to content

fix(ios): upgrade the DocuSign iOS SDK to 4.4.0 - #16

Open
maxgenest wants to merge 1 commit into
IronTony:mainfrom
maxgenest:fix/ios-docusign-sdk-4.4.0
Open

maxgenest wants to merge 1 commit into
IronTony:mainfrom
maxgenest:fix/ios-docusign-sdk-4.4.0

Conversation

@maxgenest

Copy link
Copy Markdown

Problem

For some accounts, DocuSign returns recipient view URLs such as https://apps-d.docusign.com/authenticate?code=... instead of a Signing/MTRedeem URL. With DocuSign iOS SDK 4.3.0, presentCaptiveSigningWithUrl rejects them:

DocuSign could not open the signing ceremony: Envelope (envelopeId: "") has invalid captive signing url :"https://apps-d.docusign.com/authenticate".

The 4.3.0 binary only contains the signing/mtredeem/ path. The 4.4.0 binary also contains docusign.com/authenticate, and DocuSign's 4.4.0 release notes list "Captive (embedded) signing fails to launch for certain accounts" as fixed.

Change

  • ios/ReactNativeDocuSign.podspec: DocuSign ~> 4.3.0 to ~> 4.4.0.
  • README version tables and CHANGELOG entry under ## Next. I left the package version to you.

Compatibility

  • DSMManager.h, DSMEnvelopesManager.h and DSMNotificationCodes.h are byte-identical between 4.3.0 and 4.4.0, and so are the setup keys the module reads.
  • DSMErrorCodes.h only appends offline signing codes from 1074 up, so existing native.code values do not move.
  • Same two vendored xcframeworks, with privacy manifests.
  • The SDK minimum moves from iOS 12.0 to 15.0, below the module's 15.1.
  • A project with a committed Podfile.lock needs pod update DocuSign.

Testing

  • An Expo SDK 57 app on an iOS simulator, against a DocuSign demo account that returns apps-d.docusign.com/authenticate URLs: 4.3.0 rejected the URL as above, and 4.4.0 opened the signing ceremony. The URL came from POST /envelopes/{envelopeId}/views/recipient, with and without frameAncestors / messageOrigins.
  • The same URLs open on Android with DocuSign Android SDK 2.1.7, so this PR does not touch Android.
  • npm run build, npm run lint, npm test (101 tests) and npm run typecheck:examples pass.

🤖 Generated with Claude Code

For some accounts, DocuSign returns recipient view URLs such as
https://apps-d.docusign.com/authenticate?code=... instead of a
Signing/MTRedeem URL. DocuSign 4.3.0 rejected them, and
presentCaptiveSigningWithUrl failed with "invalid captive signing url".
The 4.3.0 binary only knows the signing/mtredeem/ path; 4.4.0 also knows
docusign.com/authenticate, and its release notes list "Captive (embedded)
signing fails to launch for certain accounts" as fixed.

DSMManager.h, DSMEnvelopesManager.h and DSMNotificationCodes.h are
byte-identical, and so are the setup keys the module reads. DSMErrorCodes.h
only appends offline signing codes from 1074 up, so existing native.code
values do not move. Packaging is unchanged: the same two vendored
xcframeworks, with privacy manifests. The SDK minimum moves from iOS 12.0
to 15.0, below this module's 15.1.

Verified in an Expo SDK 57 app on an iOS simulator, against a DocuSign
demo account that returns apps-d.docusign.com/authenticate URLs: 4.3.0
rejected the URL, 4.4.0 opened the signing ceremony.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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