Skip to main content
arrow-left Back to Docusign.com
Question

Signing Document after 2FA in Focused View causes infinite loading

  • July 27, 2026
  • 2 replies
  • 36 views
M
Newcomer
Forum|alt.badge.img+1

Hi,

Using Docusign JS to render the focused view version of document signing I have an issue where the document is stuck loading after signing and pressing submit.
This only occurs if I perform the 2FA within the same opened window.


For example, if I 2FA, close the document and re-open it (I am already verified and not re-prompted for 2FA) then sign the document and press submit the sessionEnd event is triggered and the page closes as expected.

It temporarily says submitting, and then the <div data-qa=”embedded-nav-container”> is replaced with <div data-qa=”embedded-document-loading”> and it is indefinite.

The JS console only contains this error, but given it works when not doing the 2FA flow immediately prior to signing I don’t suspect this is the issue.

`Framing 'https://apps-d.docusign.com/' violates the following Content Security Policy directive: "frame-ancestors 'self' https://apps-d.docusign.com". The request has been blocked.`


Any help would be appreciated and happy to provide any supporting info for debugging.

Thanks.
 

 

2 replies

Ivan.Dinkov
Docusign Employee
Forum|alt.badge.img+7
  • Ivan.DinkovDocusign Employee
  • Docusign Employee
  • July 28, 2026

Hi ​@Mitch D , It sounds like the sessionEnd event isn’t fired after “Finishing”, leaving the UI in an infinite loading state. The 2FA step changes how the post-sign redirect URL is built, and in the affected flows the signing iframe never sends the sessionEnd message back to your host page, so your listener never runs and the view stays stuck

 

Inspect the createRecipientView call you’re making for the signer. What returnUrl are you passing?
Does that URL actually receive an event=... query parameter when you reproduce the bug with 2FA in the same window?
In a healthy Focused View flow, the final URL in the iframe after Finish will look like e.g.
https://yourapp/embedded-complete?event=signing_complete&...

 

Can you try to explicitly append event=signing_complete to the returbnURL so the focused view code can derive sessionEndType even in the 2FA path.

Ivan D
M
Newcomer
Forum|alt.badge.img+1
  • Mitch DNewcomer
  • Author
  • Newcomer
  • July 31, 2026

Hi ​@Ivan.Dinkov 

I was recently in touch with another Docusign member via a support ticket I created.
It seems that our demo account uses a new Phone Authenticator page whereas our production is still using the Legacy Phone Authentication. Apparently there is a known issue with the new Phone Authentication page in embedding signing and returning back to the calling host.

I was able to identify a workaround to trigger my session end actions when returned to the 2FA loading page (where it was infinite) and close the window manually. 

My understanding was that in Focused View embedded signing the return URL was not used and the sessionEnd event was used to identify the action the user performed (e.g. signing completed, cancelled, etc).

I think for now my issue is resolved, knowing that there is an issue with the demo environment for this flow gives me confidence our solution is correct for the Legacy Phone Authentication implementation.

Thanks for your response.

Code of ConductAccessibility statement

Docusign Community

Code of Conduct