iOS Release Notes for CloudHawk ELD (July 2026)

Application Replacement Procedure

ALL previous Android versions MUST be deleted, and the new version must be downloaded to ensure proper compatibility and installation. Carriers should ensure all driver data has been synced, and all log certification procedures have occurred prior to deletion/upgrade. We recommend that drivers completely log out of the application before performing the deletion/reinstallation.

Important Update: (More actions related to incorrect violation notifications for drivers)

The development team has made enhancements to the expected behavior between the mobile application’s interaction with the database. Recently, we have seen a reduction in the number of false violation notifications after this change was implemented. As we continue to address outstanding issues related to false violation notifications, it is essential that we immediately receive any reports from drivers/carriers. If drivers experience false violation notifications after installing the July 2026 release, please let your customer support representative know via the ticket submission platform. From this point forward, any previously submitted tickets related to false violation notifications can be considered outdated. To expedite and facilitate new concerns, our team will only investigate issues related to the newest Version 8.05.842. While this may not have addressed all incorrect violation notification issues, this is a next step in fully solving this issue.

Item	Platform	Description
1	iOS	Cycle values not reduced after reassigning accepted unidentified logs back to Unidentified driver profile.
2		Unidentified Driver Profile not included in Print/Display Logs (PDF) when PDF is generated on device.
3		Driven and On-Shift limits are not extended after enabling Adverse Conditions when driver reaches 90% of driving limit.
4		Force logout from the login screen has been repaired to route through optimum channels for debug and effectiveness.
5		MOA accounts show all assets belonging to the selected carrier, by filtering asset retrieval by HOS Account.
6		Repaired duplicate shipment records being created after saving a new shipment.
7		Documents list no longer disappears after using Search and Cancel until user refreshes or re-enters the Documents module.
8		Fuel Receipts list no longer disappears after using Search and Cancel until the user reenters the Fuel Receipts module.
9		Corrected the Manage Trailers add (+) icon tooltip to read “Add Trailer”.
10		Fixed an issue where the Personal Use option was enabled in app despite being disabled in portal.
11		A missing confirmation prompt in Duty Status after ignition cycle has been fixed.
12		A missing confirmation prompt in Yard Moves after ignition cycle has been fixed.
13		Duty status automatically switches from Yard Move to Driving when speed exceeds 32 km/h (20 MPH) - Repaired
14		Positioning Malfunction no longer incorrectly triggered despite valid GPS data during driving.
15		Exported UTC time-zone offset is now anchored to the record/cycle day, not the export instant — the logbook PDF header, unidentified-driver header, and Certification-of-RODS line compute the offset for the day being exported, so it is accurate across DST boundaries; the EST/EDT abbreviation now matches the offset, and the Canadian CCMTA authentication value is anchored to the cycle start.
16		RODS daily-log grid DST was off-by-one: this has been corrected so the printed daily-log grid no longer shifts an hour across a DST boundary.
17		Missing Required Data Elements (7.3.3) data diagnostic now recorded when an ECM-sourced event cannot obtain vehicle miles or engine hours, per Appendix A section 4.6 (manual events excluded).
18		Debug logs are automatically uploaded every 30 seconds while driver remains logged in - Repaired
19		Night-mode Material theme crash -Repaired
20		Suppressed false Power and EngineSync (“M”) malfunctions on always-connected, car-mounted tablets. Stalled and stale ECM values and disconnects are now measured and match the FMCSA definition (49 CFR Part 395 Subpart B Appendix A §4.6) so only genuine “unable-to-retrieve” intervals accrue toward the 30-minute / 24-hour thresholds.
21		GX6 BLE reconnect now keeps scanning reducing the worst-case ~107s reconnect observed on devices after the ECM radio powers off (fuel stop / DOT check).