Troubleshooting the Field Service Technician App

Overview

This article is part of a larger guide covering the Field Service Technician App, from daily use to troubleshooting.

Most issues reported in the Field Service Technician App are resolved on the device itself, without any change on gaiia's side. A screen that fails to load, a scanner that will not open, or a location that will not broadcast is usually caused by a stale app session, an outdated app version, a missing device permission, or a device management restriction.

This article gives you an ordered troubleshooting path for two audiences: the technician holding the device, and the IT administrator managing the device fleet. Working through both sets of checks before contacting gaiia resolves the majority of reports, and when it does not, it gives our team the information needed to investigate immediately instead of asking for it.

Who does what

Follow the checks in order. Each audience owns a distinct set of steps, and skipping ahead to gaiia support usually adds delay rather than removing it.

Scroll right to view the whole table on smaller screens.

Technician checks

These steps are ordered from lowest to highest effort. Work through them in sequence and stop as soon as the app behaves normally again.

Note the date, time, and work order number of the failure before you start. That context is needed if the issue has to be escalated, and it is difficult to recover afterward.

A. Soft close the app

Closing the app from the app switcher clears the current screen and forces it to load again from scratch.

•  
  1. Swipe up from the bottom of the screen, or double-tap the Home button.
  2. Scroll to the Field Service Technician App.
  3. Swipe up on the app to close it.
  4. Open the app again and retry the action that failed.
•  
  1. Swipe up from the bottom of the screen, or tap the square overview button.
  2. Scroll to the Field Service Technician App.
  3. Swipe the app away to close it.
  4. Open the app again and retry the action that failed.

B. Restart the device

Power the device fully off, wait a few seconds, then power it back on and open the app again. A restart clears background processes that a soft close leaves running.

C. Force close the app

A force close, sometimes called a hard kill, ends the app process entirely rather than suspending it.

•  
  1. Open Settings on the device.
  2. Tap Apps, or Apps & notifications on some versions.
  3. Find and tap the Field Service Technician App.
  4. Tap Force Stop, then confirm.
  5. Open the app again and retry the action that failed.
• On iOS, swiping the app away in the app switcher is the equivalent of a force close. If you have already done this in step a above, continue to step d.

D. Confirm the app and operating system are up to date

Running an outdated build is one of the most common causes of screens that no longer load correctly.

1. In the app, open Settings, then App information, and note the Version.

2. Compare that value with the version listed for the app in the App Store or Google Play.

   If the two do not match, update the app before troubleshooting any further. On a managed device, the update may need to be pushed by your IT administrator.

3. Confirm the device is running a current version of iOS or Android, and install any pending operating system update.

E. Confirm app permissions

Location and camera permissions are granted at the device level. If they are revoked, the app itself gives little indication of why a feature stopped working.

1. In the app, open Settings, then Permissions.

2. Confirm that both location and scanner permissions are enabled.

   A technician whose location is not broadcasting to the dispatcher, or whose scanner will not open, almost always has one of these two permissions turned off.

F. Uninstall and reinstall the app

On a device enrolled in mobile device management, the technician will not be able to uninstall the app. Do not spend time attempting it. Hand the issue to your IT administrator, who can remove and redeploy the app from the management console.

Reinstalling clears the app's stored data, including any cached web session that is preventing a screen from loading. Delete the app from the device, install it again from the App Store or Google Play, sign in, and retry the action that failed.

G. Hand the issue to IT

If the app still misbehaves, contact your IT administrator and provide the following:

1. A screenshot or short screen recording of the issue.
2. The device type, model, and operating system version.
3. The app Version from Settings > App information.
4. The date, time, and work order number where the issue occurred.
5. Whether the device was outside cellular coverage at the time.

IT administrator checks

Complete these checks before opening a ticket with gaiia. They separate a platform issue from a device or device management issue, which is the single biggest factor in how quickly a report can be resolved.

A. Isolate the user from the device

Determine whether the problem follows the person or the hardware.

1. Have the same technician sign in to the app on a second device.
2. If available, have a different technician sign in on the original device.

3. Record which combinations reproduce the issue.

   If the technician works normally on a second device, the issue is specific to the original device and is almost never a platform defect. If the issue follows the technician across devices, note this and include it when contacting gaiia.

B. Rule out mobile device management

Managed devices restrict actions the app depends on, and those restrictions are invisible from gaiia's side.

1. Confirm which mobile device management provider the device is enrolled in.
2. Confirm the deployed app version matches the current release in the App Store or Google Play, and push an update if it does not.
3. Review whether any policy blocks web content, cookies, storage, camera access, or location services for the app.

4. If a reinstall is required, remove and redeploy the app from the management console rather than asking the technician to uninstall it.

   Where a redeploy through the console does not clear the issue, releasing the device from management, reinstalling the app, confirming it works, and re-enrolling the device is a valid last resort. Re-enrolling can reapply the original restriction, so verify the app still works afterward.

C. Clear the device browser cache

Parts of the app load web content, so the device browser's cache and cookies are shared with it. A stale cookie can leave a screen blank even though the app itself is healthy.

This step matters most for technicians who previously signed in to a sandbox instance and later moved to production. Credentials cached from the earlier instance are a known cause of screens that open blank, and clearing them resolves it.

1. On iOS, open the device Settings, select the browser, and clear its history and website data. On Android, clear the browser's cache and cookies.
2. Open the app again and retry the action that failed.

Screens that open blank

A blank or white screen when opening a work order, while the schedule itself still loads correctly, points to cached web content rather than to the technician's account or their assigned work. The app clears this cache each time it opens web content, but in rare cases an entry persists.

Work through the technician checks first, then the IT administrator checks, paying particular attention to clearing the device browser cache and to redeploying the app on managed devices. If the technician can open the same work order successfully on a second device, the cause is confined to the original device.

Contacting gaiia support

If the issue persists after both sets of checks, email support@gaiia.com and include the following. Reports that arrive complete are investigated immediately; reports missing device or timing details cannot be traced in our session logs.

Your Customer Success contact will confirm whether the behavior matches a known issue, share the resolution timeline where one exists, and notify you when a fix is released to the app.

Preparing technicians before go-live

Technicians who know the first three steps resolve most issues themselves, in the field, without a call to IT. Cover the following during onboarding.

Have technicians train on the device they will use in production, signed in to the instance they will use in production. Devices trained on a sandbox instance, or shared between users, are the ones most likely to fail on the first day of live work.

1. Restart the device.
2. Force close and reopen the app.
3. Check the app version in Settings > App information and update it if it is behind.
4. If the issue persists, contact IT with a screenshot and the device details, rather than continuing to retry.