This release note describes enhancements and fixes for EROAD Drive APK Version 1.14.0.

The following general enhancements were completed for this release.

We improved geofence matching. Drive now uses unique geofence GUIDs for job and yard move triggers, preventing site ID conflicts and enabling smarter yard move prompts for drivers. Using GUIDs ensures the geofences are unique.

We developed an account-level setting so that customers can limit vehicle, trailer, and dolly selection to those in the driver's terminal. After enabling this setting, drivers see only vehicles and equipment assigned to their terminal or unassigned.

360 administrators can set a new policy that turns on alerting when drivers attempt to sign out or change vehicles before they have completed all jobs on the current route. For example:

Drive now supports multiple versions of Copilot via a new companion app, "Drive Navigation." This app decouples Copilot from the Drive APK, reducing Drive size and allowing faster, more flexible updates to supported navigation versions.

We updated the logic for the Directions button to better support the Sysco workflow.

Now, the button only appears when location details are available, and it makes sense to show it. It will no longer appear if directions are not relevant. This change minimizes incorrect directions and supports a smoother experience for drivers.

The following DVIR enhancements were completed for this release.

To ensure that drivers do not accidentally use unsafe vehicles and to align with safety requirements, we enhanced out-of-service handling as follows:

Administrators can turn on this behavior with a policy.

Drive and 360 now trigger a Violation alert if a driver begins driving without completing a required pre-trip DVIR inspection. This ensures inspections are not missed and supports compliance monitoring.

Drivers: Notification and the Driver Log:

Admins: Driver Log View and Violations Report

This release addresses an edge case in the "Drive Without Pre-Trip Inspection" violation logic. Previously, a violation could trigger multiple times within the same shift if a driver resumed driving after switching statuses. The system now ensures that once this violation is triggered, it will not re-trigger for the remainder of the shift. Logging out and back in, or changing vehicles, will still allow a new violation to be recorded as expected.

Compliance regulations do not require DVIR access during roadside inspections. We have removed the DVIR button from the Roadside Inspection screen.

The following general issues were fixed for this release.

To improve usability, Drive now displays notifications on the Dashboard in reverse chronological order—newest messages appear at the top. This ensures that the most relevant and timely information is always shown first.

Resolved periodic Application Not Responding (ANR) issues on Zebra devices by optimizing dashboard loading logic and reducing redundant system calls.

Resolved an issue where unnecessary account sync operations disrupted communication between Drive and CoreHub. Account data is now only refreshed when actual changes are detected, preventing redundant updates and improving system stability.

We resolved in issue in which geofences were not triggering auto-arrive events when vehicles where turned off inside geofences.

During the sign-in process, on the Select Vehicle screen, the PIN screen would display when the driver changed the screen orientation between portrait and landscape. This was fixed so the PIN screen does not display.

Previously, tapping on a Job notification card would close the Drive app instead of redirecting Drive to the Jobs screen. This issue was fixed so that Drive correctly displays the Jobs screen.

When a driver selects a trailer that is assigned to another driver, a Trailer Reassigned notification displays for the original driver. Previously, this notification would remain on the screen even when the original driver selected a new trailer. The issue was fixed so the notification leaves the screen as expected.

Updated jobs were not synchronizing as expected in the Drive app. This issue was fixed so that Job update notifications arrive and data displays as expected.

Fixed an issue in which co-drivers were not properly logged in after vehicle assignment. Both drivers are now correctly logged in and switchable on the Dashboard.

The following DVIR issues were fixed for this release.

Fixed a bug in which the "no vehicles selected yet" notification displayed when the Inspection History app was selected—even though a vehicle was already selected.

Fixed a bug in which trailer inspections were blocked when DVIR is enabled for the trailer but not for the vehicle.

The following ELD issues were fixed for this release.

Previously, a driver's logout status was not correctly updated when they logged out of Drive with a vehicle and one or more trailers attached. This issue caused drivers to appear as if still logged in. We fixed this issue to accurately reflect the driver's logout status, reduce administrative overhead, and improve compliance tracking.

An issue occurred when the connection between the telematic unit and the Drive app failed; the Drive app would not create an Auto driving event upon re-connection while the vehicle was in motion before and after the reconnection. This issue was fixed so that the Drive app always creates an Auto driving event when the vehicle is in motion and reconnection occurs.

While vehicles are in motion, the Drive screen locks to comply with safety regulations. However, if there is a co-driver, the co-driver can unlock the screen for use. This could cause the co-driver to accidentally action or disrupt the primary driver's Hours of Service (HOS) compliance. Now, when the vehicle is in motion and the screen is unlocked by the co-driver, neither driver can select or action the primary driver's notification cards. Any driver attempting to interact with the primary driver's cards while the vehicle is in motion will receive an "Unable to perform action while vehicle is in motion" notification.

Note: This only applies to driver cards, such as HOS alerts, and does not include vehicle cards like messages and jobs.

We resolved an issue in which the Hours Recap (historical snapshot) screen did not display accumulated hours. This problem occurred as a result of a change made to support the French translation. This issue was fixed, and accumulated hours are now displaying correctly.

(Canada ELD) We fixed an issue in which the unidentified driving locked screen disappeared when the vehicle speed dropped below 8 km/h. The fix ensures that the locked screen remains in place until the vehicle speed has been 0 km/h for three consecutive seconds.

The following platform enhancements were completed for this release: