It might be worth noting that our forms use a good bit of Arcade. I also discovered that a bad bit of Arcade code that I was trying to use in another web map caused the Map Viewer to partially lock up.
Description of the buggy behavior: If I try to edit a point the edit pan gives me the spinning circle. The map viewer will still let me minimize the edit tool pan but the pop-ups stop working. I can expand the edit pan, but I get the spinning wheel. I can still pan the map.
I removed this Arcade code from the calculated field for the layer I was working with, and the problem disappeared:
// Set date and time to now if the field is empty. This prevents field users from changing the date if they //need to edit a previous observation point in Field Maps.
if (!IsEmpty($feature.ObservationDate)){
return
}
Else {
now()
}
Is poorly written Arcade code messing with the Map Viewer a documented issue?