Important: GPS Issue reported in V3.3 of the Astea Mobile Native App for Android Devices


Userlevel 7
Badge +15

There is a known issue with the GPS tracking for users that are running version 3.3 of the Astea Mobile Native App on Android Devices, this issue does NOT APPLY to iOS Devices.  If MOE -10131 is set to a value of 1 the mobile device does not capture GPS coordinates, we are currently working on the fix for this issue and will include it in the upcoming 3.3.1 Native App release (the release date is still yet to be determined).  As a temporary workaround in the meantime you can change MOE -10131 to a value of 3, have your impacted technicians log out of the application and log back in again (this will download the updated MOE value to their mobile devices).  Then have them go to the Communication Diagnostics module and enable the “GPS Tracking” toggle on this screen, this will ensure that their GPS coordinates are captured in the meantime.

 

MOE -10131 Location Tracking: (1: Hidden but Location Tracking Enabled, 2: Hidden but Location Tracking Disabled, 3: Visible and Tech can edit, 4: Visible, Not Editable, Location Tracking Enabled, 5: Visible, Not Editable, Location Tracking Disabled )

2 replies

Userlevel 7
Badge +15

We have a fix for this issue that is currently undergoing QA at this time.  We expect it will be rolled out later this week in version 3.3.1 of the AndroidNative App.

Userlevel 7
Badge +15

QA has completed their testing on the Astea Mobile Android V3.3.1 release, this has now been submitted to the Google Play Store for approval...once that is completed it will start rolling out to the mobile devices (typically 1-3 business days).

Reply