Field Maps Cumulative Lag

[LaurenHarter]

My team is experiencing a lag in Field Maps that builds up; as more data are collected, the app gets slower until there is a 20-30 second lag after each "click" in the app. This is happening to most or all members of our team. For most people, shutting down and reopening Field Maps when it begins to slow down solves the problem. For at least one person, nothing seems to help, including clearing the cache, clearing out any unnecessary files and programs on the tablet, uninstalling and reinstalling Field Maps, and finally doing a factory reset of the device.

Any other suggestions would be appreciated. We are using Samsung Galaxy Tab Active2 tablets with Android version 9 OS.

[TravisSizemore]

We do have many layers with relationship classes so this may be a factor. 

Travis

[TravisSizemore]

Hi everyone,

As a new season is starting, we are still having this problem. The instability seems to be worse this year than last on the Samsung Galaxy Tab Active 2 tablets. We are seeing the following issues:

- The app shutting down immediately when opened

- Endless spinning wheels at any point in using the tablet

- Downloads or syncing freezing midway through and just not making more progress

- Downloads or syncing failing

- Logging out

Attached is a log from a recent day when this behavior was occuring. Does anyone have any new ideas?

Thanks,

Travis

[ColinMunro]

We had all of the same issues you mention. I had tried testing the same services/maps in Collector and still had latency issues, so figured it had to be an issue with the services.

After spending some time troubleshooting we found that upping the minimum instances running to 3 and setting the maximum number of instances to 6 in the Pooling settings for the service in Server Manager improved performance. The maximum (I believe) should never be more than the number of cores on the server machine. The service will restart when you do this.

I hope this is helpful.

[AnneDunckel]

HI!!!!

Good to hear I'm not the only one. We avoided using FieldMaps last year due to the bugginess, but are trying to move to it for our upcoming season. I CANNOT get FieldMaps to open any map without crashing immediately. Also using an Samsung Tab Active 2 tablet.  HEEEEEELLLLP! 

[KevinMorris2]

Anne,

If all your maps are crashing make sure your basemaps are the same datum as your data or use Web Mercator for everything.

Because you say all your maps don't work that leads me to believe some setting is missing or perhaps a domain or subdomain issue (just guessing here). Have you tried your maps on different devices to rule out a single make/manufacturer? On occasion, I've had to drop a map and recreate it due to some unknow issue. You might try that, but that's typically for the odd duck map that doesn't work.

Something to try is only create a single point feature and standard ESRI topo basemap to see if that works. If so then perhaps something in your schema is causing issues (or 1-M relationship that actually has multiple values for 1, etc.)

Also, I can't tell from this post if this is for AGOL or internal Portal. If you are using internal services, settings for certificates, and security are additional issues to deal with. Oh, you can also make sure the individual that is using Field Maps has access to all the data layers with sync enabled (even the ones without edit priv).

Sorry for the rambling, but I hope something I said helps.

[KevinMorris2]

This was emailed to me yesterday, "The Field Maps app from the latest Google Play store update (released 4/15/2022) causes the app to immediately crash on what appears to be all of our Samsung Tab Active2 tablets.  Other Android devices such as the Tab Active Pro and Galaxy S21 and later devices appear to be functioning properly.  It's unclear if this is specific to the device or the version of Android." Apparently, there is a beta release available that might solve the issue if you have access to the beta program.

[AnneDunckel]

Awesome thanks! Yea I just saw that the Beta version fixes this bug, which is AWESOME to hear! Tested it out and appears to be true.

[JoshConrad1]

All:

I have created a similar thread to this conversation (which can be found below):

https://community.esri.com/t5/arcgis-field-maps-questions/large-dataset-performance-issues/m-p/11965...

ESRI customer support tells me "this issue is to be expected".

We are now into September and the last reply was from April. Has the BETA version fixed the performance issue for the long run?

Thank you.

@sdegroot 

@DougBrowning 

[LaurenHarter]

The beta version did work well for us for the remainder of our field season.

[JoshConrad1]

@LaurenHarter 

Which version of Field Maps is your organization using? We are operating on 22.3.1.

I have not had any reports of cumulative lag in the past month so I am hoping the latest update from August 2022 did the trick. Thank you for your time.