Dev 1.7 Embedded Survey123 Issue continues

[ScottHiggins_PVGIS]

Hi all,

There were a couple threads on this yesterday, and also comments saying this issue is resolved, but in the Developer edition 1.7 of Experience Builder, embedded surveys continue to not load/resolve. Survey123beta doesn't work for Dev environment either as this was purported to be a workaround in yesterdays discussions. The AGOL version of EB this did resolve it, and it also works fine with normal Survey123 url and not just Beta.

But our custom app is now pooched. 

This breakage is very problematic as we do need to demo for a client today. Dev Tool errors:

27b2b18…:1 Uncaught (in promise) {code: 403, messageCode: 'GWM_0003', message: 'You do not have permissions to access this resource or perform this operation.', details: Array(0)}

chrome-error://chromewebdata/:1 Refused to display 'https://www.arcgis.com/' in a frame because it set 'X-Frame-Options' to 'sameorigin'.

Any help before our presentations today to fix this toasting of many of hour of work would be appreciated.

[JamesTedrick]

Hi @ScottHiggins_PVGIS ,

Just to check, are you using the Survey123 widget or embedding through another widget?

[ScottHiggins_PVGIS]

Embed Survey, for editing existing data, in Dev 1.7.

[JamesTedrick]

Thanks @ScottHiggins_PVGIS ,

This is an issue that is caused by domain scoping and some fixes that were introduced to tighten token storage with the Survey123 web form. In your case, this is due your app being on a custom domain, which means that the cookie stored from the experience builder login is not available to survey123.arcgis.com. 

The Survey123 widget addresses this by appending the cookie in the widget code.  You may be able to do something similar with the Embed widget's code.  I'm not an expert on Experience Builder, but as a test, I would:
1. Make a new widget by taking the embed widget's code (client/dist/widgets/common/embed
2. Update the processUrl function (~line 330 of widget/runtime.tsx) and add an if statement that would match https://survey123.arcgis.com and append the app's token (based on the survey123 widget, that appears to be accessible as this.props.token in the widget scope).

[ZhifangWang]

Hi @ScottHiggins_PVGIS ,

Would you mind sharing how your users sign in to the private survey from the Experience Builder app before this issue occurs? Do they need to open another tab to sign in the survey first and switch back to the app page?

In addition, we had a potential fix for this issue on the Survey123 Beta website. Can you please help test it out? You need to replace your survey URL from https://survey123.arcgis.com/share/... to https://survey123beta.arcgis.com/share/...

[ScottHiggins_PVGIS]

Hey we tried the Survey123beta option Wednesday night it is responds the same. 

We are only testing it during development, and so it was a seamless experience, no logging in was required, it handled the cookie inside the window when the survey loaded, so no tab or switch was required. The Experience Builder window just stopped handling it, with no changes on our end. I can open the survey in its own window, and there is a token call that I can see in the Survey123 browser window. But this breaks the experience in experience builder if they have to open a tab with the survey, and its not embedded in a window in the experience.

[ZhifangWang · Accepted solution]

@ScottHiggins_PVGIS ,

Thanks for sharing the details.

The Survey123 Beta website has been updated in the night of 3/24 PDT (probably to the production soon), with a potential fix to the issue you described in Experience Builder Developer Edition. It will be great if you can help us test it, to see if your workflow recovers as previously.

[ScottHiggins_PVGIS]

We are back in business! Many thanks for the prompt fix. We have multiple surveys, so I am testing to see if anything else glitches but first couple seem to be good again. Thank you. I will provide details if anything else comes up.

[ZhifangWang]

@ScottHiggins_PVGIS ,

The fix has been deployed to the production Survey123 website, please let us know if you still observe any issues.

Thanks again for your feedback!