Measure Widget Makes Application Unusable

[ericsamson_tract]

Has anyone found any work arounds for the new measure widget? It tanks our application as soon as a user opens it up by either slowing down the app immensely, or just crashing it completely.

Seems other people are experiencing this, I tacked on here but didn't get a response:

https://community.esri.com/t5/arcgis-experience-builder-questions/experience-builder-measuring-tool-...

I think it has something to do with the snapping capabilities, probably has to save all vertices in memory as soon as it opens? My app has like 50 layers, a couple of which are nationwide with potentially hundreds of millions of vertices. Maybe for larger apps there should be a version with no snapping at all?

Has anyone created a custom widget for this? Was about to go down that road myself, but rather not re-invent the wheel.

I had to remove it from my application and tell my users to use the web appbuilder version of our application for the time being. Not really a good solution to a simple mapping feature.

[Wei_Ying]

Hi @ericsamson_tract ,

Thanks for your feedback. ArcGIS Online just got new release last night. Have you ever tried on the new version and see if the issue is still happening? 

Thanks,
Wei

[ericsamson_tract]

Hey @Wei_Ying, we are experiencing this in the developer edition, so I tested it with an ArcGIS online version of experience builder (using the same map with the same data). I am still experiencing the same issue. The app slows down immensely as soon as you take a measurement. You have to refresh to reset the application.

Thanks,

Eric

[Wei_Ying]

Thanks for confirming! We have heard similar feedback. However we cannot reproduce from our side. It would be difficult for us without a repro case. 
Would you be able to share you application for us to investigate, if not i suggest contacting Esri Technical Support if possible https://support.esri.com/en-us/contact

Appreciated!

[ericsamson_tract]

Unfortunately the app is private and can't be shared externally. I will contact technical support and update here.

[Wei_Ying]

Also would you mind try the following:
1. When start new measurement, press on "Ctrl" key while measuring. See if the performance change
2. As you have many layers, turn most of them off, see if the performance change 

[ericsamson_tract]

Hey Wei,

Tried both of the above, problem persists.

1. The control key does not help, I believe it still finds all of the vertices in your map frame before measuring. All pressing control seems to do is it no longer allows snapping to those vertices. Also not really a solution for users, since they would need to remember to do that every time.

2. This problem happens even if I have 0 layers turned on. I think it could be reading all vertices even if layers are turned off.

[Wei_Ying]

Thanks a lot for testing that!
Yes please reach out Support team to troubleshot and they can help submitting repro steps.

[ericsamson_tract · Accepted solution]

@Wei_Ying I am working with the support team with a ticket currently, but for the meantime I created a custom lightweight version of the measurement tool for anyone else that is having this issue.