Permission policy violation for geolocation access when using Docusign JS

Hello Team

Could you please give a try with the below:

attributes: {
    iframe: {
      allow: 'geolocation'
    }
  },

https://stackoverflow.com/questions/64582203/how-do-i-allow-the-geolocation-api-inside-an-iframe

https://www.docusign.com/blog/developers/new-browser-security-settings-and-iframes

https://github.com/krakenjs/zoid/issues/297

"Select as Best" below if you find the answer a valid solution to your issue and mark it as resolved.

--
Thanks & Regards

Sai HariPriya Dandamudi | Developer Support Engineer | DocuSign

Hello,

Where are we supposed to add that code snippet?

Like @liquid-chai  the solution I find online is to add allow=“geolocation” in the `<iframe>` but adding the code snippet in the docusign.signing does not change anything.

Nowhere in the documentation of the focused view do I find that additional properties can be added so i am stuck with this same problem.

signing_iframeless_mobile.backbone-app.js?cs=536edd6bdbee4c9ad628:2 [Violation] Permissions policy violation: Geolocation access has been blocked because of a permissions policy applied to the current document. See https://goo.gl/EuHzyv for more details.
(anonymous) @ signing_iframeless_mobile.backbone-app.js?cs=536edd6bdbee4c9ad628:2
ready @ signing_iframeless_mobile.6672.js?cs=273da2bbf6939ef6591a:2
(anonymous) @ signing_iframeless_mobile.backbone-app.js?cs=536edd6bdbee4c9ad628:2
(anonymous) @ signing_iframeless_mobile.backbone-app.js?cs=536edd6bdbee4c9ad628:2
(anonymous) @ signing_iframeless_mobile.js?cs=5b477ac2:2
(anonymous) @ signing_iframeless_mobile.5132.js?cs=455f504302575d1778c2:2
kc @ signing_iframeless_mobile.1800.js?cs=88485f841e6f40003f94:2
e.unstable_runWithPriority @ signing_iframeless_mobile.1800.js?cs=88485f841e6f40003f94:2
Wo @ signing_iframeless_mobile.1800.js?cs=88485f841e6f40003f94:2
Lc @ signing_iframeless_mobile.1800.js?cs=88485f841e6f40003f94:2
(anonymous) @ signing_iframeless_mobile.1800.js?cs=88485f841e6f40003f94:2
k @ signing_iframeless_mobile.1800.js?cs=88485f841e6f40003f94:2
E.port1.onmessage @ signing_iframeless_mobile.1800.js?cs=88485f841e6f40003f94:2

As a note I also find it odd that “iframeless” files are being called when the focused view is designed to be embedded in an iframe.

Thanks in advance.

@Sai.Dandamudi Can you please elaborate as to where these need to be set when using the focused view?

For anyone who is having the permissions gelocalization error, I spoke with docusign global support and they confirmed that it is currently not possible to use geolocation with focused view but an enhancement request has been filed to add this to the product in future versions.

Even with the error message the session starts well, this geolocation error should not impact the content to be loaded only the geolocation will not be saved.

So @liquid-chai's loading spinner error possibly is due to something else.

I am also having the same issue but i never requested for geolocation to be used. I did everything through API endpoints and i get the embed url from my server then I redirect myself to a signing page in my angular proyect. I will leave my code as well as the error message which is the same as seen by this question. After I redirect i get the DocuSign methods from the window and follow the instructions in this page https://developers.docusign.com/docs/esign-rest-api/esign101/concepts/embedding/docusign-js-embedded-reference/#introduction

In the final step where you use the mount method is where i get the error on the console

same error,

any luck fixing it?

ok guys I figure it out

look here

https://developers.docusign.com/docs/esign-rest-api/how-to/request-signature-focused-view/

step 4

you have to specify  messageOrigins  and frameAncestors to basically let docu sign know that iframe can be rendered on your page and then also clientUserID to specify which signer is going to sign in the iframe

I’m struggling with this, too, and am already designating that. It’s still complaining. I’m not using iframes. I’m using div tags, copied from recent examples, but if I take out the frameAncestor reference, it still complains and just spins. 

My team had this same error. The loader would spin, we couldn’t sign the documents, and got the “geolocation” error. We had all the origins set correctly. Was able to solve this by sending the clientUserId.

Like this:

1. Create Envelope With clientUserId
2. Generate recipient signing URL with the clientUserId
3. Open session for signing

  "template_roles": [
        {
            "email": "somethingfake@email.com",
            "role_name": "signer",
            "name": "Dude Br.",
            "client_user_id": "abcdefghij"
        }
    ],

It’s here in the documentation.

https://developers.docusign.com/docs/esign-rest-api/esign101/concepts/embedding/embedded-signing/?utm_source=chatgpt.com

Go to the section “The embedded signing workflow is usually performed in three steps:”