Field Maps update to 25.2.X creating editing issues

GrantHoward1

Still investigating what the heck is going on, but it seems users who have older versions of Field Maps 25.1.X (or older) can still edit editable map features. Users on version 25.2.X cannot edit those same editable map features. They don't even get a feature popup when they tap the feature.
This issue does not seem to be limited to iPads, iOS versions, Androids, etc. 

It appears that the root of the issue is based on the Field Maps app version being used.

This is a huge issue for us as many (but luckily not all) of our field staff devices update apps automatically. We are a Public Works department and we use ArcGIS Online as our work order system.

This issue is very serious to our work functions and business continuity. 

Anyone else having similar issues? I saw a fresh post stating that the new Field Maps app versions were also causing issues when connecting to Trimble GPS devices.

ESRI, I sure hope you are dedicating an army of resources to fixing this critical issue. 
Maybe consider rolling the app version update back?

NoahDeer

@ColinLawrence 

Resolved my issue, unsure if it's still relevant to this thread:

Problem - Infinite or excessive form loading when trying to add a new feature or edit existing. Some features don't load, others lag then don't allow submission, others work perfectly. No error codes. IOS and Android. No issues before 25.2 release.

Cause - Issues occurred on layers with calculated expressions for some fields. Expressions involved using the point location in a calculation (lat, long) or to retrieve an attribute from an underlying feature/layer. 

Thus, the form was trying to run a series of calculations using coordinates that did not yet exist.

My field map collection settings are configured to make “No changes to the map” when “Collecting new features.” So, this may not be an issue for users with the configuration “Center the map and add a point at your location” as it might first retrieve coordinates and then run the expressions? However, I believe I had an issue for both configurations.

Solution - Alter the Arcade expressions for each field to not run the code until it is given coordinates (point added/updated). Now, all layers load immediately and have no issues adding/editing features.

Thoughts - 25.2 may include a procedural change in background processes when adding/editing features, attempting to run all arcade expressions even before the point is created. Regardless, this was not a problem before this version. Another note - one arcade expression, simple "Now()," used to retrieve date/time, would completely prevent the form from loading.