topic Sync Error - in ArcGIS Collector Questions

Sync Error -

AntonioCano — Mon, 03 Jun 2019 17:32:27 GMT

Receiving a sync error "An error occurred while synchronizing edits" with "No details" when using Collector for ArcGIS on Android V 18.0.3

Multiple troubleshooting efforts have been made including:

Push Edits only set ON
1. Refresh
2. Clear cache from the device
3. Clear cache from the Collector for ArcGIS App
4. Upload using cellular data with wifi feature off
5. Upload using various wifi network
6. Uninstall, Restart and Reinstall Collector for ArcGIS

Found article for downloading data from device and exporting as file geodatabase, but this is not ideal at the moment as there are multiple users.

Error occurs after small edits and across 5 different devices: 3 Samsung Galaxy Tab As and 2 Trimble TDC 100s.

Additionally the OS for devices are up to date.

Any idea as to how to troubleshoot?

Re: Sync Error -

ThomasJones1 — Wed, 26 Jun 2019 12:18:31 GMT

Hello Antonio,

Are you signing into Portal or ArcGIS Online in Collector? If you are signing into Portal I would recommend reviewing the Portal logs at 'DEBUG' level.

It may also be impotent to focus on the web map content. In particular the data source for each of the web map items (e.g. basemap, operational layers).

For Example:

Are the services in the web map using hosted or registered data sources?
Is a custom basemap being used?
Are you able to successfully edit in a web map in ArcGIS Online or Portal?

Finally I would also recommend attempting to capture network traffic from the mobile devices when trying to sync. You can use network capture software such as Fiddler to attempt to capture this information.

Thank you,

Thomas.

Re: Sync Error -

AntonioCano — Wed, 26 Jun 2019 14:34:35 GMT

Hi Thomas,

Thank you for your reply. The issue was occurring with AGOL. We ended up taking this case to Esri and were able to resolve. We did look at the network traffic on the mobile device, and noticed that the same hosted service was giving trouble editing in AGOL. After some research we noted that the issue stems from the m and z values being enabled during the creation of the feature class in ArcGIS Desktop. Once those were removed, operations resumed as normal.

Best,

-Antonio