Blocking Loading Spinner

[ChrisSherlock91]

Library Version 4.0.1

When trying to use captive signing the loading spinner is never dismissed and blocks the user from interacting with the document. This issue only appears when signing demo urls and not production.

SDK function call - DSMEnvelopesManager().presentCaptiveSigning

This is currently blocking development for me, if I could get an update ASAP would be appreciated

[ashok-meena-engcp]

Hi @ChrisSherlock91 -

Thanks for posting this question.

Looks like you are using the signingURL variant to initiate the captiveSigning:

presentCaptiveSigning(
                                withPresenting: self,
                                signingUrl: signingUrl.absoluteString,
                                envelopeId: envelopeID,
                                recipientId: nil,
                                animated: true,
                                completion: { _,_  in })

Few clarifications:

• Was this working before with an older SDK version and now it's showing the spinner with 4.0.1?

• Are you able to load the signingURL in the safari browser (mobile web) and finish the signing for the demo signing URL?

• Given that it's working on the Prod signing URLs and not on Demo, are you using the Brand-File to customize the experience and it's not correctly setup on Demo environment?

TGK Financial Sample App has this use case illustrated.

Thanks

[ashok-meena-engcp]

FYI @ChrisSherlock91 - There is an open issue that affects Demo site and is being patched for signing component on broader level (independent of iOS-SDK).

[ChrisSherlock91]

@ashok-meena-engcp Thanks for the quick response, Yes this was working on the current version of the library. After some more research it seems like the open issue that affects demo is probably causing this issue as I noticed the android implementation is also having issues loading the documents.

[mmohareb]

Hello @ChrisSherlock91 the changes on the signing web application have been addressed and it should be working normally now.

Please let us know if you are able to confirm the same on your side.