Field Maps Freezing Issue — Need Guidance

[JorgeMarioRestrepoMurcia]

Field Maps Freezing Issue — Need Guidance

We are experiencing intermittent freezing in Field Maps (Android) when editing a specific feature layer. The form becomes unresponsive while typing, and the device log repeatedly shows:

[SNAPPING] missing cache info, invalidating cache [SNAPPING] rebuilding cache

We already removed most Arcade expressions and domains, reinstalled the app, and tested on multiple devices. Other layers work normally — the issue only affects this one layer.

Has anyone seen freezes caused by snapping cache rebuilds or heavy domains in recent Field Maps versions?

Any help or suggestions would be appreciated.

[MarcMuehleisen]

I have a similar behaviour in a field that has a specific visibility rule (entering a "password" so further fields appear).

Can you point me to the logs and where i can find them so i can see if this is the same log message.

Thank you!

Edit: found the logs, but the message in our case is not the same and not helpful

[JeremyBrown4]

I'm having a similar issue in the last few weeks on android tablets only. I have a very complex form with a lot of calculated fields and conditional visibility that has worked fine in the past, albeit a little slow, but that's understandable. What I've noticed recently is that when typing in a 'Notes' field (255 character, multiline, string field), it seems like every character typed causes all the fields to recalculate. Eventually this overloads the form and it freezes. I see nothing useful in the log file either. It doesn't even seem to think there was an issue. I have tried to replicate this issue on an iPad, but it doesn't freeze up like the android device does. I am running 25.3.0 on all devices. I wonder if this is a bug with the newest release?

[CharmaineSnape1]

I think it is a bug as we have upgrade to 25.3 in the last two weeks and are getting a simliar issue and we were not getting this in the older version.

[JeremyBrown4]

The new 25.3.1 update is available and it seems to have fixed my issue. Hope it solves everyone else's too.