Defects Fixed
The following defects were fixed in the Go for Android and iOS 14.0 release:
Case Number
Defect Number
Description
Discovered in Go App Version
00174586
064511
After upgrading to Go app version 12.0, the notification sound selection was reduced from six alert tones to one in the iOS. The configured notification tone was not applied to incoming notifications, and the default sound played regardless of the setting.
12.2.0
00178228
065757
The parts service order status reverted from Submitted to Open after users submitted the order through SFM while a background Smart Sync was in progress. The incorrect status displayed on the service order till the ongoing sync was completed.
12.3.1
00181246
066490
A notification badge displaying the number 1 appeared briefly on the Go App screen when users opened the app, even when no new announcements existed. The notification disappeared immediately when tapped, and users could not determine the source of the alert.
13.0.0
00181080
066793
Multiple deeplinks configured to run in sequence within a Mobile Activity Space (MAS) behaved inconsistently across platforms. The subsequent navigation to a View SFM screen did not complete after a full data sync was triggered.
13.0.0
00179979
067019
After a forced config sync push notification was sent from the Mobile Console, the Go app on iOS entered a continuous config sync loop. The sync did not stop after completion, preventing users from using the app.
12.3.0
00182840
067139
The Team Calendar in the Go app displayed both technician and equipment records from the Service Group Members list. Equipment records appeared in the team member selection panel alongside technicians, when only technician records should have been shown.
13.1.0
00182194
067142
Reassigning a Work Order from one technician to another through SFM using Smart Sync did not remove the calendar appointment from the original technician's calendar. The event remained visible on the original technician's calendar until a manual data sync was performed or the app was restarted.
13.1.0
00187053
067357
On iOS, the Go app navigated to the config sync page and froze after a forced config sync push notification was received. Users could not proceed with their tasks and had to force-close and reopen the app to recover. The issue occurred intermittently in production.
13.0.0
00187868
00184417
00184623
067445
The Team Calendar member selection counter displayed a fixed total of 5, even when the service team had fewer than five members. For example, a team with two technicians showed 2 of 5 selected, which caused confusion about whether team members were missing.
13.2.0
00184026
067528
Color coding did not apply correctly after users created an Event along with a Work Order from the Account. The calendar showed the Event in the default color instead of the configured color, which caused inconsistency and made it harder for users to identify events accurately until a subsequent sync updated the color.
13.2.0
00184119
067542
Closing an SFM within a Mobile Activity Space (MAS) navigated the app back to the MAS screen instead of the Work Order screen. Users had to close the MAS window a second time to return to the Work Order screen.
13.2.0
00185582
00186086
067861
On iOS, the Completion Artefacts SFM took 10 to 15 seconds to load after users tapped the action. This delay affected app responsiveness and slowed down task completion compared to earlier versions.
13.4.0
00184521
067863
A validation error triggered by a JavaScript code snippet during SFM execution caused a loading spinner to appear and remain on screen permanently. The OK button for the validation message did not render, leaving the app in an unresponsive state. Users had to force-close and relaunch the app to continue.
13.1.0
00186555
067999
Rich text formatting did not display correctly after users viewed records that contained rich text fields. The app showed bold text, italic text, and hyperlinks as plain text, which made the content difficult to read and reduced clarity.
13.3.0
00177400
065843
Formfill fields did not populate correctly in offline scenarios when multiple records were created and later synced. This issue occurred particularly under weak or unstable network conditions, resulting in inconsistent field mapping where some records were not populated as expected.
12.3.0
00177751
067078
Product details on work detail lines were intermittently missing after sync. Although the product was selected and appeared during parts consumption, it was not retained after sync, resulting in blank product fields for some records.
13.0.0
00183920
067429
Rescheduling a work order through the calendar Edit Appointment did not sync automatically and remained in pending update. After updating the appointment and saving, the changes were not synced as expected, causing delays in updating the work order schedule and requiring manual sync to reflect the changes.
13.1.0
00183781
066841
The image markup feature did not provide the arrow option while editing photos during upload. This issue prevented adding arrow annotations to images using the markup tool. The issue occurred due to a missed code merge.
13.0.0
00182524
00180596
066629
Service reports did not display correctly after full-screen signing in the Go App. After opening a service report from a closed work order and expanding the signature screen to full view, the screen expanded vertically instead of switching to landscape mode, which affected the proper display of the report.
13.0.0
00180066
066150
The back button did not return to the MAS page after a checklist was opened from MAS in the Go App. The app redirected to other pages such as Work Order, About, More, or Notifications instead of returning to MAS. This issue affected navigation on phones and prevented users from returning to the expected screen in their workflow.
12.4.0
00181093
066401
The Go App on iOS responded slowly and took up to several minutes to load screens, open SFM pages, use the time picker, and complete sync operations in environments with more than 1,000 installed products. This delay affected overall app responsiveness and slowed down daily tasks in large data scenarios.
12.3.0
00181194
066715
The Go App redirected to the Calendar page while editing a work order after the external keypad was disconnected. This behavior caused loss of unsaved data in checklists and debrief screens and interrupted ongoing work. The issue occurred because the device treated the keypad disconnection as a configuration change and reloaded the active screen, which returned the app to the Calendar page.
13.0.0
00174385
064638
The Go app on iOS showed incorrect behavior when creating a parts order from a work order, where the Email ID field populated the same value multiple times after selecting the Airport profile name. The problem was caused by inconsistent handling of field value updates through the code snippet API on iOS, which led to repeated updates of the text input despite the correct value being passed.
12.0.0
00181347
065650
The iOS Go app experienced an issue where the cursor and text field jumped while typing in long text fields, making text entry difficult. The issue occurred due to improper handling of content offset adjustments in the default iOS UITextView when the selected text range changed, which caused unstable cursor positioning.
12.3.0
00179747
00177693
00178139
00179026
065801
The Android preview build showed an issue where maps did not load when accessed from the Calendar screen. The issue occurred because the preview build used a debug fingerprint that was not associated with the Google Maps API required for the Go preview build, which prevented maps from loading on Android.
12.4.0
00177645
065919
The Go app stored authorization details, including authorization headers and auth keys, in the application log files, exposing sensitive information. This issue occurred because the notification service logged the complete notification response and configuration objects that contained authentication data.
12.4.0
00179455
066003
The Go app intermittently reset the Work Detail quantity to 1 after editing, instead of retaining the value entered by the user. This issue occurred during rapid data entry, particularly when adding a new labor line and using a comma as a decimal separator, and it was more noticeable with certain locale settings. The root cause was that the Add or Save action triggered before the Quantity field value finished updating due to a debounce delay in the input handling, which caused the previously entered value to be lost.
12.3.0
00179451
00179877
066102
The Go app displayed an issue where the Description field trimmed the last few characters of the text when viewed on a service task. The full text was visible in the browser, but the mobile app did not display the complete content.
12.4.0
00179979
066338
The Go app repeatedly prompted users to download an updated Compass configuration after a forced configuration sync notification was sent. This issue occurred because both the notification services and the background task processed the same notification at nearly the same time, which resulted in duplicate notification triggers and repeated prompts.
12.3.0
00181582
066444
The Go app showed an issue where the sync cloud icon flashed repeatedly, creating a continuous and distracting sync indication. This occurred because the successive sync logic triggered whenever pending changes existed, even if the previous sync attempt failed, which caused repeated sync attempts and continuous flashing of the sync icon.
13.0.0
00182776
00182200
00182199
00181078
00181927
066668
The Mobile Console did not display user-related information for Go app version 13.0 under the Usage by App Version section. This issue occurred due to an unintentional change in the eventType in version 13.0, which prevented the system from retrieving the required data.
13.0.0
00182869
00181243
00182390
00182111
00180835
N/A
On upgrading to the 13.0 version, if users performed config sync without the required User Preferences permissions, no errors were encountered. The config sync was shown as successful, and users could proceed to use the app. The expectation was that config sync should fail.
13.0.0
Was this helpful?