iOS App feature attachment upload

346
3
02-05-2013 09:02 AM
chadphillips
New Contributor
We have an iPad application that allows a user to attach multiple photos to a point feature then submit the data to an ArcGIS 10.1 feature server.  This issue we are running into is when the user has more than one photo attached not all the photos are successfully upload to the service.  For example we attach 10 photos to one point feature, submit the data and only 8 of the 10 photos successfully upload.  Looking at the code through fiddler we see the photos that don't make it throw this error "Lock request conflicts with an established lock [sde.DEFAULT]???.  We tested the app against a 10.0 feature service and the all the photos successfully save every time.

We are using ArcGIS iOS SDK 2.3.2 with an AGS 10.1 feature service(attachments enabled) created from a 10.0 sde feature.  Any help would be appreciated.

Thanks
0 Kudos
3 Replies
DanaMaher
Occasional Contributor
...we attach 10 photos to one point feature, submit the data and only 8 of the 10 photos successfully upload.  Looking at the code through fiddler we see the photos that don't make it throw this error "Lock request conflicts with an established lock [sde.DEFAULT]�?�. 
Thanks


So you are using AGSAttachmentManager, right? Have you tried chaining your photo uploads using the - (void)attachmentManager:didPostLocalEditsToServer: method of the AGSAttachmentManagerDelegate protocol you are implementing in your code? Your error sounds like a collision between numerous asynchronous calls, and the lock might be released between successive uploads.

This does sound like a bug in 10.1, but the upload chaining might be a workaround until it is addressed.
0 Kudos
DarrenMackiewicz
Occasional Contributor
Did you try filing an incident with Esri Tech Support? Did you figure this out?  Any more info? Having similar issues here.
0 Kudos
VincentSunga
New Contributor II
ESRI did end up getting back to us with the issues and said this was a bug. Last I heard they were going to implement a fix in an update...I'm guessing it's not included in the newest one if you are still having an issue. Might help to talk with them to confirm
0 Kudos