Tracks not uploading from Tracker App in iOS

[DavidEvans5]

We have a tracker application we created within our ArcGIS Online account (all the maps and data is hosted through our AGOL account) to monitor areas our City Public Works department have passed through to fog for mosquitoes.

Everything appeared to be work as it should during testing with tracks automatically pushed from the iPad (the Tracker app is installed on) and viewable within the Track Viewer application. Now tracks are no longer being pushed automatically and we cannot even use the manual "Upload Now" button to push them (tapping the update button does not activate that function and the date of last upload remains July 21, 2020).

Restarting the app and restarting the iPad itself do not fix the problem. I am afraid to sign out of the app incase I lose the data that is stored under that account. Is there something I'm missing or some other setting needed to upload our tracks?

One further detail (I'm not sure if this would have any bearing on the problem we've encountered) is that we wanted the mobile user to be able to view their tracks through a regular web map without having to give them the full admin privileges usually required to View Location Tracks and access to the Track Viewer. We therefore set up a custom user type within the "Member Role" settings with the "View Location Tracks" privilege and assigned the account that is logged in on the Tracker App on the iPad to this customer user type.

I appreciate any assistance that can be provided.

[Anonymous User]

Hi David,

Can you triple tap on your username row in the profile screen. This will enable developer options which will show a "logs" button. You can tap this to view device logs. Once you are able to do that, can you try doing a manual upload and see what is logged?

[DavidEvans5]

Hi Aaron,

Here are the logs that were exported when I followed your directions:

8/10/20, 10:40 AM Ping tracking service

8/10/20, 10:39 AM Failed to update last known location

8/10/20, 10:39 AM Ping tracking service

8/10/20, 10:39 AM Regenerating lines

8/10/20, 10:39 AM Reachability changed: Connected

8/10/20, 10:39 AM Tracking started

8/10/20, 10:39 AM Tracking manager lines table loaded

8/10/20, 10:39 AM Tracking manager log table loaded

8/10/20, 10:18 AM Failed to update last known location

8/10/20, 10:18 AM stationary updating LKL service with last location

8/10/20, 10:17 AM Failed to update last known location

8/10/20, 10:17 AM stationary updating LKL service with last location

8/10/20, 10:16 AM Failed to update last known location

8/10/20, 10:16 AM stationary updating LKL service with last location

8/10/20, 10:15 AM Failed to update last known location

8/10/20, 10:15 AM stationary updating LKL service with last location

8/10/20, 10:14 AM Failed to update last known location

8/10/20, 10:14 AM stationary updating LKL service with last location

8/10/20, 10:13 AM Failed to update last known location

8/10/20, 10:13 AM stationary updating LKL service with last location

8/10/20, 10:11 AM Failed to update last known location

8/10/20, 10:11 AM stationary updating LKL service with last location

8/10/20, 10:10 AM Failed to update last known location

8/10/20, 10:10 AM stationary updating LKL service with last location

8/10/20, 10:09 AM Failed to update last known location

8/10/20, 10:09 AM stationary updating LKL service with last location

8/10/20, 10:08 AM Failed to update last known location

8/10/20, 10:08 AM stationary updating LKL service with last location

8/10/20, 10:07 AM Failed to update last known location

8/10/20, 10:07 AM stationary updating LKL service with last location

8/10/20, 10:06 AM Failed to update last known location

8/10/20, 10:06 AM stationary updating LKL service with last location

8/10/20, 10:05 AM Failed to update last known location

8/10/20, 10:05 AM stationary updating LKL service with last location

8/10/20, 10:05 AM Ping tracking service

8/10/20, 10:05 AM tracks fail-safe timer triggered

8/10/20, 10:04 AM Failed to update last known location

8/10/20, 10:04 AM stationary updating LKL service with last location

8/10/20, 10:03 AM Failed to update last known location

8/10/20, 10:03 AM stationary updating LKL service with last location

8/10/20, 10:02 AM Failed to update last known location

8/10/20, 10:02 AM stationary updating LKL service with last location

8/10/20, 10:01 AM Failed to update last known location

8/10/20, 10:01 AM stationary updating LKL service with last location

8/10/20, 10:00 AM Failed to update last known location

8/10/20, 10:00 AM stationary updating LKL service with last location

8/10/20, 9:59 AM Failed to update last known location

8/10/20, 9:59 AM stationary updating LKL service with last location

8/10/20, 9:58 AM Failed to update last known location

8/10/20, 9:58 AM stationary updating LKL service with last location

8/10/20, 9:57 AM Failed to update last known location

8/10/20, 9:57 AM stationary updating LKL service with last location

8/10/20, 9:56 AM Failed to update last known location

8/10/20, 9:56 AM stationary updating LKL service with last location

8/10/20, 9:55 AM Ping tracking service

8/10/20, 9:55 AM Ping tracking service

8/10/20, 9:55 AM Failed to update last known location

8/10/20, 9:55 AM stationary updating LKL service with last location

8/10/20, 9:54 AM Failed to update last known location

8/10/20, 9:54 AM stationary updating LKL service with last location

8/10/20, 9:54 AM Ping tracking service

8/10/20, 9:54 AM tracks fail-safe timer triggered

8/10/20, 9:53 AM Failed to update last known location

8/10/20, 9:53 AM stationary updating LKL service with last location

8/10/20, 9:52 AM Failed to update last known location

8/10/20, 9:52 AM stationary updating LKL service with last location

8/10/20, 9:51 AM Failed to update last known location

8/10/20, 9:51 AM stationary updating LKL service with last location

8/10/20, 9:50 AM Failed to update last known location

8/10/20, 9:50 AM stationary updating LKL service with last location

8/10/20, 9:49 AM Failed to update last known location

8/10/20, 9:49 AM stationary updating LKL service with last location

8/10/20, 9:48 AM Failed to update last known location

8/10/20, 9:48 AM stationary updating LKL service with last location

8/10/20, 9:47 AM Failed to update last known location

8/10/20, 9:47 AM stationary updating LKL service with last location

8/10/20, 9:46 AM Failed to update last known location

8/10/20, 9:46 AM stationary updating LKL service with last location

8/10/20, 9:45 AM Regenerating lines

8/10/20, 9:45 AM Purged 0 features

8/10/20, 9:45 AM Failed to update last known location

8/10/20, 9:45 AM stationary updating LKL service with last location

8/10/20, 9:44 AM Regenerating lines

8/10/20, 9:44 AM Regenerating lines

8/10/20, 9:44 AM Regenerating lines

8/10/20, 9:44 AM Failed to update last known location

8/10/20, 9:43 AM Tracking started

8/10/20, 9:43 AM Tracking stopped

8/10/20, 9:42 AM Failed to update last known location

8/10/20, 9:42 AM Tracking started

8/10/20, 9:42 AM Purged 0 features

8/10/20, 9:41 AM Ping tracking service

8/10/20, 9:41 AM Ping tracking service

8/10/20, 9:41 AM Failed to update last known location

8/10/20, 9:41 AM Tracking stopped

8/10/20, 9:41 AM Tracking started

8/10/20, 9:41 AM Regenerating lines

8/10/20, 9:41 AM Ping tracking service

8/10/20, 9:41 AM Reachability changed: Connected

8/10/20, 9:41 AM Received applicationWillTerminate Aug 10, 2020 at 9:41:01 AM

8/10/20, 9:41 AM Tracking manager lines table loaded

8/10/20, 9:41 AM Tracking manager log table loaded

8/10/20, 8:34 AM Ping tracking service

8/10/20, 8:34 AM Ping tracking service

8/10/20, 8:34 AM Ping tracking service

8/10/20, 8:34 AM tracks fail-safe timer triggered

Hope this helps!

[Anonymous User]

Okay so for some reason it seems to be unable to update your last known location feature.

Can you verify that your account in AGOL has access to the location tracking feature service (by default the service and layers are shared to the org)? You can search your org using this:

typekeywords: "Location Tracking Service" NOT typekeywords: "Location Tracking View"

and it should return one feature service/layer.

If you can access that item, can you query the last known location layer and see if you see your username returned in the list of features. Like:

created_user = 'myusername'

[DavidEvans5]

I created a Group to keep the Tracker content separate from our other features/maps, and the "TrackerTest" account is a member of this group and should have access to both the Tracks and Location Tracking feature services.

Here is the search result for "Location Tracking Service" 

(The highlighted symbols indicate the layers are shared with the "Mosquito Fogging Tracker" group)

Here is what is shown in the "Last Known Locations" data:

The username is the one that is set up in the Tracker App on the iPad (BtownTracker) the created date is showing 7/15/2020 and the timestamp is 8/10/2020.

[JBorgal]

Does this workflow only apply to iOS? Do Android users have the same ability? If not should they capture fiddler logs?

[DavidEvans5]

I changed the Role assigned to the user account that is logged-in in the Tracker App to a regular "Data Editor" role and the tracks have now been pushed so I can view them all in the Track Viewer.

I am curious still whether its possible to create a custom role that has the "View location tracks" privilege that I can assign to the user account(s) that would benefit from being able to see the Tracks (not least the guys performing the mosquito fogging so they don't go over ground they have already covered). Currently the "View location tracks" privilege is only available to the top tier Administrator role. Are there any plans by ESRI to update one or more of the other roles (i.e. Data Editor, Publisher) with this privilege or create a new "Tracker" role?

When creating custom roles, it might also be useful to be able to start with one of the preset roles and modify it, as opposed to needing to configure everything from scratch (I guess I should post this to the Ideas section).

Thanks