Latest Contributions by MC2

Hi James,      The survey has 24 questions total & is not very complex, I don't think.  No repeats. No calculations.  Only constraints limit 2 integer text boxes to 1 < . and . < 250. About 5 'relevants' like (${aQuestion} != "" AND ${anotherQuestion} = "B") to hide conditional sections pending response to initial 2-3 questions. There's 1 map, 1 photo, 1 Date, 8 short lists with < 5 items each, 1 longer list with ~100 items, and about 15 text boxes. Removed other constraints & calculations to bound the geopoint values because it didn't work on the web app version. Only issue seems to be the camera & trying to take a photo.   Thanks for any help! ... View more

Hi we seem to be having a similar issue, although not inside a repeat, and on both iPhones & Android. Accessing the camera to take a photo causes the app to crash completely, at least on first use. Crashed on me after accessing the camera & going "back" without taking a photo (iOS 10.0, iPhone 5S).  Crashed on 3-5 other people (various iOS & Android phones) at some point in the photo-capturing process. As Kevin mentioned above, of course this wipes out everything the user had already entered without auto-saving anything, and they're now reluctant to use the app for their project (some are tech-averse & were worried about losing data - this unfortunately sort of confirmed their fears). After deleting the app, installing the latest iOS update & reinstalling the survey, it didn't crash on me, but did still crash for other people. I gave permissions to access camera when prompted. I assume others did, but can't be sure. Sorry I don't have more details.  Maybe a permissions issue (since it seemed to most consistently crash on first use), or maybe the delegate handling the user interaction isn't set at first, or isn't quite acting as expected to either cancel/dismiss the camera or store the photo? Accessing the photo roll to select existing images is also extremely slow & makes the app unresponsive, but it didn't crash (this may be because my phone is too full of photos & it was trying to display a count of them all, but I still wonder if there's a way to not block the UI...?).  Also sorry, I wasn't able to open a report ticket & don't have time to chat, so had to put this here. Thanks as always for any help!!   ... View more

Ok, thanks for the quick reply ... Is there any way to determine the platform in the XLSForm so I could conditionally remove/apply the relevant constraints that are referencing the geopoint? Or another way to constrain the geopoint's extent? (I'm using pulldata() to determine x,y and then constraint inequalities to bound the acceptable input). ... Is there a way to catch/check if a value is null/empty/undefined? Not sure if that syntax exists here. Thanks! ... View more

This would limit the result to only showing 5 decimal places, but it doesn't require 5. The original problem was that the coordinate value was being truncated to only 2 digits, when it needed 4 or more. If you're manually editing the coordinates on a map, you can use a constraint to force a minimum length: string-length(${latitudePulledFromGeoPoint}) > 5 But otherwise there doesn't seem to be a mechanism for dictating precision/scale of the lat/long values (is there?) ... View more

This use of the `pulldata()` function does not seem to work properly in the web client versions of a survey. Using the approach above, the survey loads & works fine on mobile devices and in Survey123 Connect preview ... The Web client, in contrast, shows an error: Error loading survey. Error message: External instance "@geopoint" is empty., FormLogicError: pulldata with incorrect number of parameters found: pulldata("@geopoint", location , "y") Please contact survey author. This makes sense, because there is no "external instance @geopoint" ...  The geopoint doesn't exist until after the survey loads & gets user permissions to create a geopoint to reference... Are there different implementations of pulldata() to explain the "incorrect number of parameters"? The function signature explained in the post above only takes 3 arguments: pulldata(<@geopoint>, <${someGeopointToUse}>, "aDesiredGeopointProperty") ...But the pulldata() function as explained elsewhere requires 4: https://community.esri.com/groups/survey123/blog/2016/10/27/the-pulldata-function-access-external-data pulldata(<csvfile>, <returnColumn>, <lookupColumn>, <lookupValue>) Seems the Web App is assuming the latter, and/or the former is leaving 1 out, but's not clear which one. Any help or thoughts? This is one of the major obstacles to reconciling the mobile version of our survey with the Web App. Thanks! ... View more

- Did you set your viewController to be the delegate for callouts (` AGSCalloutDelegate`) ? This is initially `nil` & needs to be set or else annotations won't appear. You can then implement the delegate methods to control what the annotation displays. Displaying a callout—ArcGIS Runtime SDK for iOS | ArcGIS for Developers - Not sure it's relevant, but you call `showCalloutAtPoint...` immediately after adding the graphic. Does `myGraphic` appear? If not, maybe refresh the layer or map before calling this method? ... View more