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.
Hi Colin,
I think I added your individual username instead. I just added arcgisfieldmaps as well.
Thanks,
Travis
@LaurenHarter Colin is actively creating test features and trying to recreate the issues you have been experiencing on your ActiveTab2, but so far he hasn't noticed any slowdowns. Is there a particular feature(s) that are being created or updated which seem to give the most trouble? Any idea how long it takes to start seeing the slow down? Have they continued using those tablets and noticed any changes in the performance since then?
Thanks,
Travis
Hi Travis, I asked my crew for input on those questions and I'll add that info here when they get back to me. For now, I thought it would be helpful to Colin to note the features recorded on a typical survey:
~50-75 Territorial Point features
~30 Line features
2 Visit features
~5 Non-territorial Point features
Thanks,
Lauren
@LaurenHarter @TravisSizemore Do the field crews happen to be working offline/disconnected when they experience this behavior?
@ColinLawrenceYes, they only use Field Maps offline.
We experience the behavior while working online, even on recent versions of iOS on iPad Air and Pro. To me it seems not to depend on the OS if others experience the problems on Android devices.
Has this issue been resolved?
Our team is also experiencing this behavior, where the map (offline usage) will react very slow and creating and editing features will become nearly impossible.
We never really resolved it per se; our crews have just been periodically restarting the app and avoiding the devices that get bogged down the most. Hopefully ESRI will figure out what's causing this.
It's only a month since the last reply but I thought I'd check anyway, any news on a fix for this?
We're seeing the same issue with several Samsung Active Tab 3's.
Seconded. We are experiencing a similar scenario. The service in question is a related table. Unsure if anyone is using related tables.
The workaround I am using is to restart the service in server manager every few hours on days we have surveyors out in the field.