nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

'Feature isn't Valid' error for Field Maps on iOS

GISJess

Any idea why Field Maps would give a 'Feature not Valid' error for someone with an iPhone? I have a Field map, that works on my Android fine, both online and offline, all layers submit with no issues. However, my coworker who has an iPhone, is having issues with two of the several editable layers. Most of the layers work for him, but there are two layers that are giving him the 'Feature isn't Valid' error.

He is not using an offline map. Since he will be in the field soon, he will not uninstall/reinstall the app until after this week, and he will use one of the 'Generic Layers' that is working for him to take data for now.

Is this just one of those weird bugs, where I'll just have to reupload the layers with issues?

Thanks.

FieldMapsError.jpg

Slide2.JPG

wayfaringrob_0-1725734841921.png

Find more posts tagged with

Accepted answers

All comments

GISsolutionIZ

Update:
In my case, I was able to identify the issue. I had recently changed the Due Date field to be mandatory. However, a few months ago it was not a required field, and some tasks were created at that time without a due date. Now, when mobile workers try to work on those old tasks, an error appears because the Due Date field is now mandatory but has no value.

As a workaround, you may want to check if any field settings were recently changed. That is often the cause of this type of issue.

GISsolutionIZ

Our field workers are also receiving the validation error. I’ve set up the tasks in the form using contingent value fields, and I’m not sure if that might be causing the issue. However, only two workers are experiencing the error — others using the same tasks are not encountering any problems.

In any case, I hope this will be resolved soon.

261d9a9d-b8df-4c1c-ac94-cd271ffaa4f3.jpg

Capture_rawdem.JPG

mad4pup

Yup as of 6/3/2025 this is still an issue with iOS, I don't have any conditionally visible fields or anything required either 😞

McKenziGaines

Chiming in to say that as of 4/21/25, I have had this same issue with iOS. Once I removed all conditional visibility and required expressions, my form finally worked on my iPhone. It was working fine on an Android device from the start.

GISJess

If you're still experiencing this issue, I would suggest giving them a call and letting them know. They are more likely to fix it faster if there are more reports made about this bug.

MiltonSolano

@GISJess

I can attest this bug it is still present on Field Maps, version 23.3.0 on iPad (not only iPhones). My forms work great on Android devices with hidden field groups but raises errors on iPads. So I have to remove the conditional visibility for these fields.

Let's hope ESRI is aware of this bug.

Milton

GISJess

Update to this issue:

I was told by a representative, that there is a bug for iphones when using conditional visibility and making the hidden field required. To avoid this bug, do not make any fields that are hidden due to conditional visibility required.

I hope this is something that is fixed soon, as sometimes you need a field that pops up due to conditional visibility to be mandatory to answer.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.