Select to view content in your preferred language

Field Maps Crashing on Android Device After Collecting Point Feature

3880
10
Jump to solution
07-17-2023 02:17 PM
travisajohnson_wsp
Emerging Contributor

Hello,

I have a web map that has been configured for ArcGIS Field Maps using the field maps designer application on AGOL. It uses domain data capture and arcade expressions to auto name sample points that my field staff collect in a given sampling event. the arcade expression is set to look at various attribute fields and update the final sample nomenclature based on what was submitted.

The new web map/field maps has been working fantastically for my iOS users. Recently, we have had a staff member with an android phone start working within the web map. Every time they collect a GPS Point feature, Field Maps completely crashes without any error message. We also have polyline and polygon feature layers within this web map that the staff member is able to collect without any problem. The polyline and polygon features do not have any arcade logic associated with them and so that is why I am thinking it could be an issue related to that. Wondering if this is a bug related specifically with Field Maps Arcade expressions and Android devices. Hoping to either get some advice on fixes or raise awareness of a possible bug.

 

I can post the code if that would help. Again, we are only running into this issue on Android devices.

Tags (3)
0 Kudos
10 Replies
CSDING_GIS
Occasional Contributor

We were struggling with the same error message.

I have to admit that our case was definitely a bit special, since the setup of the form was not always made through the Field Maps Designer, but changes were made in the ArcGIS Online Assistant which is probably how the bug sneaked in.

When inspecting the form in the Designer, we found that one of the already added fields appeared on the right-hand side Form builder as a field to add.

CSDING_GIS_0-1754900654562.png

Even though in the Designer, there was no apparent reason why it would do that (all form field properties seemed to be correct), inspecting the field in the ArcGIS Online Assistant we realized that the form field was referencing a non-existent field (in our case, "Contaminants" instead of "contaminants")

0 Kudos