QuickCapture offline web map cache - layers disappear

[StaceyTorigoe]

I was super excited about the new web map caching features. I'm a huge fan of using QuickCapture for allowing field workers of all tech levels to collect invasive plant data in the field. However, not being able to use offline web maps the way you can in Collector was a huge drawback. The web map offline caching shows a lot of promise for making QC more useful. 

I have a project with a web map loaded (for export imagery layer and one polygon feature layer). I open the map, pan around, and switch to airplane mode as recommended to save the cache. My feature layer (boundaries) immediately disappears. Occasionally (maybe once every 10 tries) the feature layer is still visible. Any ideas why the boundary layer only sometimes sticks around?

[IsmaelChivite]

Hi @StaceyTorigoe  We would like to look at your project in more detail to diagnose the problem. Would you mind email quickCapture@esri.com so we can schedule a quick call?

[JohnathanHasthorpe]

Hi @StaceyTorigoe we are aware of the bug and are investigating the cause. We will update this post with more information.

Thanks

John

[StaceyTorigoe]

Thanks Johnathan and Ishmael. Sorry just saw this, will email you. Please let me know if you are able to fix the bug, it would make QC able to fill an immediate need for offline data capture! 

[JohnathanHasthorpe]

We will be adding a new property to the project JSON in version 1.13 (due March 2021), to address this issue. If you go into the JSON editor and change the value for the featureRequestMode property from onInteractionNoCache to onInteractionCache (and then save the project) you will no longer see the issue.

However, making this change means that there will be a slight lag in web map updates when online. It can take a few seconds for any newly submitted features to appear. 

In a future release we will make this a setting in the designer, so you wont need to do this manually.

[JohnathanHasthorpe · Accepted solution]

We will have a fix for this in 1.15. It will no longer be necessary to use the featureRequestMode property.