search

doug-m / CollectorAuroraTesting

Manage testing feedback for Collector holistic testing.
0 stars 7 forks source link

"No collectable layers are visible" persists inaccurately #108

Closed btpschroeder closed 6 years ago

btpschroeder commented 6 years ago

Issue

I am unable to view the editing template for collecting data in the feature list. No amount of panning or zooming makes the ""No collectable layers are visible" message disappear.

Expected Behavior

The bottom dialog should populate with layers.

Map and Credentials

Unable to provide direct access, but am happy to share any metadata or information you might need. The items are hosted on a Portal, and both the web map extent and feature layer extent include the area in which I am working.

Steps to Reproduce

N/A

Device Information

holistic-no-layers

Kevin-GIS commented 6 years ago

Might be similar/related to SF 912. However the workaround doesn't apply. So the underlying issue might be different.

btpschroeder commented 6 years ago

I should also note that this same workflow works seamlessly in the latest (non-beta) version of Collector:

holistic-working-collector

btpschroeder commented 6 years ago

I strongly suspect this is related to the layer and not the web map. After doing further testing, some feature layers are working properly while others aren't -- and the ones that don't work are all being generated the same way. I'm attaching the layer JSON should that be useful. collector_feature_json.txt

Kevin-GIS commented 6 years ago

@btpschroeder what version of Portal are you working with?

Is that a hosted feature service or a federated feature service?

Kevin-GIS commented 6 years ago

@btpschroeder I tested with my 10.6 portal hosted feature service layer/map and I couldn't reproduce the issue. I would like to compare our services together if possible. Is it possible for you to create a test user account so that I can gain access to that map to test with?

btpschroeder commented 6 years ago

@Kevin-GIS All of our layers are hosted feature layers. Our test Portal is on 10.5.1. I'll contact the team and see what I can share with you... would be nice to give you as much access as possible so we can figure out what's causing this in Aurora. I'll follow up.

Kevin-GIS commented 6 years ago

Hi @btpschroeder I have been able to reproduce the issue you're seeing with that particular map/service, using the account you shared.

I understand that its using a Location Tracking layer, but how was it originally created? Was it created using this method https://www.arcgis.com/home/item.html?id=051146f34aec4ef8ac228b5e6b2b8eac or generated from a layer template directly inside Portal?

I am not seeing this issue using another one of my maps that has a Location Tracking layer in it.

The 'Time Info' section of the JSON is formatted slightly differently between both services, therefore that might be where the issue is. However, that could also be due to the version of Portal being used vs AGOL.

Is this the only map that you're having this issue with?

Kevin-GIS commented 6 years ago

Closing as non-reproducible. This behavior has been addressed in SF 922.