search

doug-m / CollectorAuroraTesting

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

Overall review. #164

Open Shimoorook opened 5 years ago

Shimoorook commented 5 years ago

AuroraTest_082218_JYoon.docx

miaogeng commented 5 years ago

@Shimoorook

Works. Auto-sync option only counts the time while the app is activated. For example, if the auto-sync is set for 5minutes and your phone screen goes black after 1minute, it does not auto-sync, and goes back to 5minutes when you re-open/activate your phone.

We will look into this issue. Note: sf-1069

If the work area is created for offline mode, even when the map is synced, the newly updated features/functions do not get synced as well. For example, if the map turns on labels on AGOL or add a new field to the feature layers, those do not get synced to the ‘work area’(offline packages?).

You need to recreate the package again, as shown the screenshot below.

When creating work areas on AGOL with VT basemaps, it usually returned two outputs. (screenshots attached below). One that will just show the three vertical bars moving forever, and the other showing ‘packaging’ forever.

We are aware of two issues about this. One is performance improvement, the other is to have a better way to show packaging status.

The area that I used was smaller than ½ * ½ mile, default LOD, and ‘never’ for auto-sync. When refreshed in the middle, it will show that the area is created in AGOL and the app, but wouldn’t download and return an error message when clicked.

This is the same as https://github.com/doug-m/CollectorAuroraTesting/issues/158.

Working with two areas A & B that are almost identical and created on the app as an offline work area(?), when I create a feature in Area A, the feature shows up in Area B, but can’t be accessed. For some reason, if I create a feature in Area B, that can be edited and accessed from Area C. I’ve crated another Area C that is almost identical to Area A & B, I still can’t edit or access any features created on Area A or B, but I can still see features.

Can you create a separate github issue and share the maps and describe the steps, .etc?

Sometimes the map will just disappear and won’t comeback until the app is restarted. And sometimes the layers will not show up until the app is restarted as well.

Can you create a separate github issue and share the maps and describe the steps, .etc?

Offline areas created on the app doesn’t show up on AGOL ‘work areas’. This is expected unless you have some user case for this requirement.