Latest Contributions by AaronKoelker

I ran into this error today as well with a similar scenario. Narrowed the issue down to a single point feature class that was keeping the group from uploading to AGO -- and realized that while I had an attachment table and relation in my fgdb for that feature class, they weren't correctly associated with it (I think I did some renaming at some point). So after deleting those attachment items and re-enabling attachments on the feature class, I was able to publish all the layers just fine.   Seems like a number of things will trip the staging error, but worth checking your attachment settings.   Edit (12/2/2025): Fate has brought me here again, six years later, so I will add another scenario to this post.  Was running into this issue once again working with ArcGIS Indoors data, and the solution was to run the Upgrade Indoors Database. I assume this fixed some validation rule issues that I created by exporting/importing some of my Indoors feature classes into my fgdb. So if you're getting this error and happen to have validation or attribute rules in your data, check those for any issues, too.  ... View more

Good point, I'll keep an eye on any running/suspended apps as I use it more to see if there's a culprit. -Aaron ... View more

Phil I'm on 3.5164 (64bit). The device is a Samsung Galaxy S9+ (model SM-G965U1) with Android OS 9 running. -Aaron ... View more

After further testing with 3.5, I'm actually still getting pretty frequent crashes. Sometimes the app will run fine for 15-20 minute stretches with no issue -- other times I'll get three or four successive crashes in a row immediately upon launching that app. I haven't yet been able to pick out any rhyme or reason to the behavior yet. Aaron ... View more

Ok, thank you for the update ... View more

Doesn't seem like the QuickCapture app made it to the Google Play Store yet (the url in the resource page doesn't exist), and the direct download link from MyESRI is an exe instead of an apk, which seems strange? ... View more

Will do, thanks for the update. -Aaron ... View more

Adding my experience to this discussion since it is close, though I see it on all my surveys instead of just one. Using a Samsung Galaxy S9+ and Survey123 for Android has become unusable for me since the 3.3 update. Upon opening any survey, the app crashes somewhere between immediately and maybe 30 seconds or so. I can open a survey and not make any inputs on the screen, and the app will still close out at random. Disabled the app's permissions for location services and still see that same behavior, so not sure what's running in the background and tripping the crash. I get this behavior on all surveys, ranging from complex surveys with pulldata and external CSVs, to a simple test survey with a single yes/no question. Have reinstalled the app multiple times, and cleared installation folder manually through the file explorer. I also attempted to test the 3.4 EAC beta, but see the same behavior. If anything, the crash occurs quicker. Haven't been able to get a hold of another android device in my office to test, but my coworkers iPhone devices are able to run the same surveys without issue. Works ok in the browser, too. So it seems to be android or device specific. Wondering if anyone else is seeing issues on Galaxy devices after 3.3? Part of my position is to help support all our GIS users with their mobile solutions, including Survey123, so not being able to test or use any of our surveys has me in a bit of a pickle. EDIT: Looks like the addition of a 64-bit version in 3.5 has solved my issue regarding the Samsung Galaxy S9+, which is a 64-bit device. The app is much more stable and usable! ... View more

Ah! Thanks James. That's exactly what I'm looking for. I had done it in the pop-up configuration. Don't know how I've missed that "define fields" option after all this time. Appreciate it! -Aaron ... View more

I know that through hosted feature views I can protect my public survey submissions from being edited or deleted, and I can control what fields are visible for a public-facing AGO web map, but is there anyway to completely hide a field from a hosted feature layer view? I've found that while I can disable them in the view's Visualization tab, you can simply open the REST service URL of the public view, click the the "View In: ArcGIS.com Map" button, and see all the fields via the pop-up on submissions that were created by anonymous users.   I'm in a scenario where we're collecting submissions on storm debris from the public, and need them to provide contact info in case we need more detail from them, but I don't necessarily want that contact information to readable by the public as well, only my org users.   There's the option to control what anonymous editors can see, but I need an option to control what anonymous viewers can see.  ... View more

If they just want to use your survey as a starting point to design another survey for their own needs, you can send them the XLS file from Survey123 Connect. ... View more

Hey Robbie, did you ever find a fix or workaround to this? Other than removing the attribute expressions? I'm running into the same issue. ... View more

Thanks for the info Zhifang! The workaround functions like you said and will work out just fine for us. Much appreciated! -Aaron ... View more

I created another discussion for this same issue after not finding anything in the GeoNet search, and then came across this one in related content afterward... I'm seeing the same inconsistencies in my reverse geocode as you. Works fine in the field app, but the same survey in the web form only returns intersections (sometimes the intersections don't even make sense if the point is away from one.) Trying to get a survey reconfigured for hurricane season and am eager to get this solved before then. Inconsistency in reverse geocoding results across field app and browser  EDIT: There's now a workaround in the linked topic above. ... View more