Survey123 connection blocked in Chrome after Nov 2025 update

[mattkramer]

Hello,

I was wondering if anyone else is experiencing issues with survey123 forms embedded in dashboards. Users who are using Google Chrome and have installed the most recent (Nov, 5th 2025) update have not been able to access forms via ArcGIS Dashboards. They are getting connection blocked and CORS errors. These issues are not present when accessing the forms/dashboards in Edge.

If anyone has any information on this, it would be appreciated!

[Geoeki]

@Ruth_JiatengXu I can confirm...embedded Survey123 component in our custom app doesn't work either due to this:

That's a big issue...Chrome will soon require this and using Firefox or Edge as a workaround isn't working either in a company of 80k employees, when Chrome is the standard group-wide browser.

[Ruth_JiatengXu]

Hi @Geoeki ,

Thanks for sharing here. According to the screenshot your provided, the iframe does not appear to be one created by the Survey123 JS API. The "allow" attribute needs to be added when the iframe is initialized; otherwise, it won't work.

You can use the Survey123 JS API to embed Survey123 form as follows:

Survey123 JS API blog: https://community.esri.com/t5/arcgis-survey123-blog/introducing-the-survey123-web-app-javascript-api....

If it is still not working for you, could you please share a sample app with us so we can investigate? You can send it by email as well.

Thanks,

Ruth

[Bernd_Loigge]

Hi @Ruth_JiatengXu 

I am an colleague of  @Geoeki . I have posted here as well: https://community.esri.com/t5/arcgis-survey123-questions/survey123-webform-in-iframe-blocked-by-chro...

We are initializing the Survey123WebForm in an Angular App using the same concept like described in the blog post.

How to set the allow attribute on the iframe correctly?

          const formObj = {
            clientId: GisExplorerSurvey123FormComponent.CLIENT_ID,
            container: this.survey123?.nativeElement,
            portalUrl: this.strManagerService.getPortalUrl(),
            hideElements: ["field:location", "topbar", "submit"],
            version: surveyItemInfo.version,
            jsApiVersion: surveyItemInfo.version,
            itemId: surveyItemInfo?.itemId,
            mode: undefined as string | undefined,
            globalId: undefined as string | undefined,
            token: this.strManagerService.getToken(),
          };

          this.survey123WebForm = new Survey123WebForm(formObj);
          const container = this.survey123WebForm.getContainer();
          const iframe = container.querySelector("iFrame");
          iFrameDiv.setAttribute("allow", "geolocation self https://survey123.arcgis.com; camera self https://survey123.arcgis.com; microphone self https://survey123.arcgis.com; local-network-access *");

Thanks,

Bernd

[Ruth_JiatengXu]

Hi @Bernd_Loigge ,

This code can be removed, as the Survey123 JS API automatically adds the allow attribute to the iframe.

const iframe = container.querySelector("iFrame");
iFrameDiv.setAttribute("allow", "geolocation self https://survey123.arcgis.com; camera self https://survey123.arcgis.com; microphone self https://survey123.arcgis.com; local-network-access *");

Thanks,

Ruth

[Bernd_Loigge]

Hi @Ruth_JiatengXu ,

The solution was to switch to the latest version of the Survey123 JS API and remove the manually set allow attribute from the iframe.

Thank you,

Bernd

[VAAVAA]

thank you

[EricKriener]

this isn't just a survey123/iFrame thing... it's happening for dashboards, arcade, and wab apps that are hosted/built on AGOL and are trying to get at our public arcgis server REST services

[ctalleygreenville]

Yes, we are having issues with this as well.  Especially embedded web maps/apps using the Embed code that are using our Stand alone arcgis Server Rest Services.  I will likely submit to Esri especially if Edge will no longer work as well.

[DavidFlack]

I am having this problem in Edge 143.0.3650.66. The fix suggested by @Daniel_Perkins  appears to be viable.  

To access the settings in Edge:  edge://flags/#local-network-access-check and set this to Disabled.  Then restart the browser.

[BenClark]

Any word on a permanent fix for surveys nested within Experiences using the Embed widget? My organization is just about to deploy a public-facing initiative that includes two Experience/Survey123 combinations that no longer work. I don't think we can move forward now without an actual fix that doesn't require client-side actions or outright re-designing the affected resources.