I believe I have found an undocumented bug with the both Measurement Tool and Widget. I have a map with a polygon layer. Collectively the polygons cover the entire map area and this layer is configured with Framework > Select Data Records and Near Me > Set Location Actions. When using either the Measure Widget or the Measure Tool built into the Map Widget, I am unable to double-click to end the measurement. This applies to both line and polygon measurements. Additionally, clicking the map to add a vertex triggers the Actions in the Map Widget when using the Measure Widget. The Measure Tool does not trigger the Actions.
The Draw Widget appears to behave appropriately, disabling the Actions and ending the drawing on a double-click.
Hi @JeffreyThompson2 ,
Thanks for your feedback. Unfortunately I cannot reproduce on my side based on your description. Do I set the message action as you did?
Can you share your application?
I tried it again this morning and was not able to reliably reproduce the issue. I did see it happen once out of many attempts. I think it might be related to the issues other users have reported where the Measure Widget overtaxes their memory. Perhaps it can lag to the point where it will not register the double-click?
I have this same issue. It happens every time I use the measure widget. Has a solution been found?
Hi @SusieDFG,
Are you using Experience Builder in ArcGIS Online or Enterprise? If Enterprise, which version?
Are you experiencing this in all apps, or just one? Are you able to share a link to the application if it is public?
All the best,
Clio
I am using experience builder in ArcGIS online. I have the measure tool added as a widget to one experience which is the only one I have used the measure tool in. I unfortunately do not have license permissions to share publicly so I am not able to. I would believe it is related to the measure tool over taxing memory as someone else has suggested. My computer does use a lot of memory when I am using the tool.
That's no problem! Interestingly, a bug was raised in the past for this issue (BUG-000174087), however this has been marked as fixed, and I have seen users report that they are no longer experiencing the issue. I wonder if the issue you are having may be slightly different.
How many layers do you have in the web map that you are using in your Experience Builder app? Does it contain any group layers? And how complex is the Experience Builder app config?