Skip to content

Feat: force dismiss captive signing#2

Open
virajpsimformsolutions wants to merge 2 commits into
IronTony:mainfrom
virajpsimformsolutions:feat/force-dismiss-captive-signing
Open

Feat: force dismiss captive signing#2
virajpsimformsolutions wants to merge 2 commits into
IronTony:mainfrom
virajpsimformsolutions:feat/force-dismiss-captive-signing

Conversation

@virajpsimformsolutions

Copy link
Copy Markdown

No description provided.

virajpsimformsolutions and others added 2 commits June 23, 2026 18:37
Expo AsyncFunction handlers are dispatched on AsyncFunctionQueue (a
non-main queue). DSMManager APIs (clearAllWebCookies, logout) must run
on the main thread, so endSigningSession could touch them off-main and
intermittently hang or crash. Hop to main before calling clearWebCookiesAsync.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
presentCaptiveSigningWithUrl presents the DocuSign signing WebView as a
native modal above the app's view hierarchy. The SDK only dismisses it on
the user's own Finish/Cancel — so a host app that tears down the session
programmatically (e.g. a remote "end consultation" signal) cannot remove
the modal: reset() resolved the JS promise but left the WebView on screen.

reset() now dismisses the presented modal on the key window's root view
controller. Gated on an in-flight signing (hadPending) so reset() never
tears down an unrelated modal when no signing is active.

Co-Authored-By: Claude Opus 4.8 (1M context) <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