OT1 6.2.2 Point Release for Drive/Command Infrastructure and Mobile App
Attention for all Driver users, there is a 6.2.2 Point Release coming for the Drive/Command infrastructure and mobile apps. This is for DRIVE only (no other OT1 components) but its Drive mobile .apk and small updates to Drive host infrastructure.
Fixes
| Work Number Item | Issue |
| DVIR-1083 | There is a known issue in Omnitracs Drive where a Vehicle that was connected to and associated to a previous Trip may show up on a DVIR that is performed after a different Vehicle is connected. This issue has been be resolved in the 6.2.2 release. |
| DVIR-1082 | There is a known issue with Omnitracs Drive whereby trailers are occasionally being dropped unexpectedly while driving. In addition, there can be unexpected behavior in the system when a driver Drops/Hooks a trailer in the XRS mobile application interface instead of the Omnitracs Drive interface. This issue is a combination of XRS-9941, DVIR-793, and DVIR-665 (DVIR-1083) has been resolved in the 6.2.2 release. |
| DCMD-5946 | When using the Unplanned Stops feature in Omnitracs Drive, there is a known issue where an ‘Unassign Trip’ operation fails when the ‘Arrive’ Task of the first Stop was already been completed. This issue has been resolved in the 6.2.2 release. |
| DCMD-5945 | There is a known issue in Omnitracs Drive where some 3rd party Android mobile apps cannot be launched from within Drive. This issue has been resolved in the 6.2.2 release. |
| DCMD-5940 | In Omnitracs Drive, drivers cannot switch the active driver to the CoDriver while the vehicle is in motion. This issue has been resolved in the 6.2.2 release. |
| DCMD-5942 | Drive- Hamburger menu located at the top left hand corner of the page in Drive is sensitive to touch inputs. If the user taps on the menu sideways, or the edge of the hamburger menu, it does not appear to register a touch. Sometimes it requires a firm touch to register. This issue has been resolved in the 6.2.2 release. |
| DCMD-5989 | There was an unanticipated issue with the Drive 6.2.1 release where Drive would not open successfully after upgrading from a previous release of Drive. This was caused by a faulty database migration feature for the Drive Location Plug-in. This issue has been resolved in the 6.2.2 release. |
| DCMD-5990 | There was an unanticipated issue with the Drive 6.2.1 release where the Bluetooth Printing failed to initialize properly. This issue has been resolved in the 6.2.2 release. |
| MA3PI-1791 | There was an unanticipated issue with the Drive 6.2.1 release where the Drive infrastructure could not successfully resubmit Integration Events (aka IntEvents) to external endpoints after an initial failure. This issue has been resolved in the 6.2.2 release. |