Hello,
I recently republished a survey with some small changes and noticed this issue with the geoshape field - it seems to be creating a duplicate of the map window below it as a blank box. I am using Survey123 Connect's Standard Template, last modified 9/16/25.
Below is an image of a dummy survey I made with just a geoshape question without any formatting except being required and a second example question from the template retained. I've uploaded the XLS Form for you to test.
Any idea what I can do to remove this box? It is showing up in both Chrome and Edge browsers.
Thanks for your thoughts!!
Solved! Go to Solution.
This is a bug unfortunately. I raised it with ESRI and they have escalated to high. BUG-000183824 if you need to quote it.
If you put ?version=latest on the end of your survey URL it will vanish. It seems this is an issue where 3.25 version of survey123 is fine, but 3.24 (the current live version) is broken.
I also started experiencing this in a geopoint question that's been running on the web for quite some time, republished with Connect version 3.24.31 today (I'm not sure if it started today as I don't always open the form, but it's been less than a week for sure).
This is a bug unfortunately. I raised it with ESRI and they have escalated to high. BUG-000183824 if you need to quote it.
If you put ?version=latest on the end of your survey URL it will vanish. It seems this is an issue where 3.25 version of survey123 is fine, but 3.24 (the current live version) is broken.
Thank you! This is most helpful. I will mark it as a solution, since this is a great intermediate step while the bug is being resolved, even though the actual issue isn't resolved.
I tried to put ?version=latest at the end of the survey URL. But, it didn't work for me.
Could you please specify exactly where to add?
Thanks!
I went and tried add that to the URL but it didn't work. However, if I required it to use 3.25 in the survey123.arcgis.com Settings page, that resolved the issue.
Me too!
@ksimm I tested this today with version 3.25 available to download now. I was not able to recreate the issue anymore. May you test this at your end and confirm if this fixes the issue for you.
Hi @JohnsonMichelle @ksimm @SMH-Rio @Almaz_Naizghi @Teresa_Blader @MarcelBeckmann ,
The fix for this issue has been deployed to the production environment. Please republish your survey to apply the update.
Thanks,
Ruth