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; } } }

Layer fails to load in Collector

ColinBourne84

Hi All,

I have a layer that fails to load within the new version of Collector (Apple device). I get the following error message

Domain: com.esri.arcgis.runtime.error

Code: 2

Description: Invalid argument

The layer loads within Collector Classic and on other platforms (Android).

Just wondering if anyone else has had this problem or knows what the code is referring to?

Cheers

Colin

Vind meer berichten getagd met

Accepted answers

All comments

borcha48

I am having the same problem, collector and layers work fine on android. Map opens on Apple but collection layer has following error "Layer failed to load"

Thanks,

Sue

MartinAncilleri

We are also seeing the same issue.

Some Layers are failing to load on the new Collector App but ok on the Collector Classic.

Anonymous User

Anyone find an answer for this issue? It was just brought to my attention today by one of our users. We just recently received and implemented new iPads and the data for the web map all shows up in the Classic Collector but in the New Collector, we get some errors on two or three of the Feature Classes saying "Failed to Load". They all load fine in the Web Map. We are running our own organizational hosted services on 10.6.1 ArcGIS Server. Thanks for anyone who can assist.

borcha48

I called esri and got a tech guy on the line and he fixed the problem. I am attaching below the recap of what was done to get the layers to function.

To recap our phone call, you were seeing an issue in Collector for iOS 19.0.1 where one specific layer would not load in any web map. When you click the layer, you were receiving the error: "Code 2. Invalid argument". To fix this issue, we inspected the fields list in ArcGIS Online. We noticed that some fields had domains. We added a space to one value in the "Code" field in each domain, removed it, and saved the domain. On the backend, this changes the name of the reference to the domain. Like I mentioned, there was a known issue with the naming convention of these references that became apparent with the last release of ArcGIS Online. Simply resaving each domain fixes the issue.

Sue Borchardt

PhD Candidate - Teaching Assistant

Department of Geography, UW-Milwaukee

Assistant GIS Specialist

Cartography and GIS Center - Bolton Hall

DanielArsenault

I have this exact error, tried this domain trick, didn't work for me. i use the classic collector version for this layer ...

JacquelineMalloy

I have this same issue. The only difference is the error code I get is

"Domain: com.esri.arcgis.runtime.error

Code: 10018

Description: bad lexical cast: source type value could not be interpreted as target:"

This is in Portal, not AGOL. This service includes 3 point layers that are not displaying, and 2 line features that are displaying. All maps also work fine in Collector Classic. This same service is on another web map and all layers appear. I have republished the service and tried the domain trick suggested in the thread and still have the same issue, "Layer failed to load".

JeffShaner

Hi Jacqueline,

Sorry that you have run into this issue! Code 10018 looks to be a different issue than the domain issue reported above. Can you please log a technical support case so that one of our analysts can document the problem and we can work on a resolution?

Thanks!

Jeff

Kara_Shindle

I am trying to bring in a WFS we publish from our own server and I am receiving this error. The other layers hosted on AGOL load fine. I need to be able to add in services to the collector app from our server, as I cannot edit the domains within AGOL.

Kara_Shindle

Any answers if the layer dropping this code is a WFS hosted on our own server? I cannot go into AGOL & edit domains like the response suggests above. Do I need to just use Collector (Classic) instead?

UtilitiesCoordinator

I recently got an iPhone and the Collector app updated, which caused me to have the same problem, I eventually found a solution that worked. Try these steps below.

1) In ArcGIS Online go to Data - Fields for the layers you are trying to use in collector. In the List of Values, delete the spaces from the values under the Code heading. Do this one by one down the list, then start at the top of the list putting the spaces back in. Make sure there are no spaces before the first character. The click Save.

2) Open parent feature layer, and select Add to new map with full editing control. Remove any unneeded layers, and save each layer. Save the map with a new name.

3) Define the extent of the webmap you just save and un-check Use in ArcGIS Collector. Save the General and Webmap sections, and return to Content. Open layer again and recheck Use in ArcGIS Collector.

*This worked for me, and was the only method that preserved the layer schema's.

Good Luck

RustyBarker

I have a map with a layer that I setup last year (August 2019) and it worked just fine in Collector. Fast forward to last week and I went to make some edits while in the field and I am greeted with the following error:

Domain: com.esri.arcgis.runtime.error
Code: 2
Description: Invalid argument

The map and layer show up just fine in a web browser. Issue seems to be isolated to Collector App.

I have tried going through each domain, editing the codes, revert back to the original, and then re-saving but I continue to get the same error. Anyone else still having this issue? Really don't want to have to re-create this feature layer. Help!

MArreguin

This solution worked for me. I'm using Field Maps version 22.1.0.

One view layer in Field Maps wasn't drawing. I added a space to the domain codes and deleted the space, saved, refreshed my Field Map and the view layer started drawing again. Thank You!

JessicaWay1

We are having this same issue with a set of view layers wer are using in the Field Maps App. The layers had been working fine for several months and then suddenly we got the errors. Everything is working correctly in the web map but not mobile.

We tried the adding spaces to the 'code' in the domains but did not have success. Only rebuilting the layers from scratch fixed the issue.

AliDiba3

Hello,

I had this same problem and error in ArcGIS Field Maps with mobile map packages. I disabled editor tracking on the feature dataset that contained the feature class and this fixed the issue.

Adam

Doe mee aan het gesprek

Aangemelde leden kunnen berichten plaatsen, updates volgen en meer. Nieuw hier? Registreer een gratis account.

Snelle Links

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