⭐️ Mobile SSO: We’re introducing Single Sign-On (SSO) to the Platform apps. SSO enables you to require drivers to authenticate through your preferred Identity Provider (IdP) before accessing the mobile app. It helps ensure your mobile app meets internal security requirements. It also streamlines the login experience for drivers by using their active IdP sessions and eliminating the need to manually enter credentials.
You can configure your Authentication web service to reject any login attempts with traditional username and password credentials to force authentication via the IdP. Your Identity Provider must support OIDC-based authentication. For multi-tenant applications, you can provide multiple Identity Providers, allowing you to offer SSO to various user segments with unique authentication requirements.
Follow the steps in our Mobile SSO Guide to enable SSO for your app. This requires access to your IdP’s configuration page.
⭐️ Dashboard Layout Setting: We’ve added a new setting that lets drivers choose how their dashboard is displayed to better suit their device’s size and orientation. By default, the app uses Auto Layout, which typically shows one column in portrait mode and two in landscape. With the new Dashboard Layout option in the Settings screen, drivers can override this behavior and select the layout that works best for them.
Available options include:
- Auto (default)
- Always 1 Column
- Always 2 Columns
Please note: In this release, layout preferences are not saved across login sessions or devices. But that’s changing soon: in our next release, this setting will be saved locally.
⭐️ New Look for To Do’s: We’ve updated the design of our To Do’s on both the dashboard and the To Do menu. You can now customize the text on the call-to-action button so that you can add context about the requested task. The call-to-action button is now larger and repositioned at the bottom of each To Do so that it’s easier for drivers to interact with.
🔧 Optimized Data Consumption for Scanning: Our 1.60 release introduced Auto Scan, a package of improvements to scanning and image capture. This includes automatic image detection and capture, on-screen prompts to guide drivers, and mobile-side image enhancement so drivers see exactly what gets delivered. These enhancements resulted in a noticeable increase in data usage so the feature was made opt-in only. In this release we’ve made some optimizations.
- On iOS, there is no increase in data consumption.
- On Android, scanning results in a modest increase – 0.6MB to 0.8MB – but because scanning makes up a small fraction of overall app usage, the impact is minimal.
Improved scanning will remain opt-in for now, but will become the default in a future release. To opt-in to Auto Scan, please reach out to support@eleostech.com.
iOS
🔧 Improved Load and Stop Details UI: We updated the buttons on Special Instructions and stop details to a clearer “Show More” / “Show Less” button, improving visibility and usability for drivers. Also, the buttons are no longer visible when there isn’t more information to be shown. This brings iOS up to parity with the Android changes we made last release.
🐞 Fixed a bug where the padding for static text in a form field was not correctly aligned.
🐞 Fixed a display bug that caused Payroll text items to sometimes not size properly to fit the given content.
🐞 Fixed a bug with the TTS push notification on incoming messages while on the in-motion lock screen that caused TTS push notifications to no longer display when new messages are delivered.
🐞 Fixed a parity issue where if a user did not fill out a field on a form, iOS would omit the null field from delivery with the message.
Android
⭐️ Text-to-Speech Enhancement on In-Motion Lock Screen: We’ve enhanced the in-motion lock screen experience to make text-to-speech (TTS) messaging more accessible. Previously, if a driver missed the opportunity to play a TTS message (for example, when briefly stopped at a light or in traffic), that message would no longer be available when the in-motion screen reappeared. Drivers would have to find the message later and read it manually.
With this update, the in-motion lock screen now displays a new Unread Messages counter and a Play button. The counter updates in real time, showing how many unheard TTS messages are available, even if those messages were received before the in-motion screen appeared. If there’s nothing to hear, the Play button is disabled, making it easy to see at a glance whether a new message has been received. Tapping the button plays the most recent TTS message aloud.
To keep messages timely, the app automatically removes unheard TTS messages from the playback queue once they’re more than 8 hours old.
Heard and read status are tracked independently: hearing a message through TTS does not mark it as read and does not send a read receipt to your backend. Only when a message is opened and read will we send a read receipt.
🐞 Fixed a bug where the wrong notification sound was played rather than the one designated by the customer via the message API.
🐞 Fixed a rare crash in Navigation that occured when a user begins navigation to a stop on a load that has been removed from your load list.
🐞 Fixed an issue with the Galaxy Tab A that causes incorrect camera rotation when scanning.
🐞 Fixed a rare crash occurring when beginning turn-by-turn navigation and then backgrounding the app.
✅ As usual, this version of the Platform mobile app is designed to be backwards-compatible with your existing web services and doesn’t require server changes prior to being deployed. If a future version introduces a backwards-incompatible change, we’ll note that in this portion of the release notes.
Server and App Manager
The following items are server-side changes and are available without a mobile app update.
⭐️News Items API – Text Styling: News Items can now support HTML styling to add rich text, colored text and highlighted text to your News Items. Support is limited to the following HTML properties: <h1>, <h2>, <h3>, <b>, <i>, <u>, <ul>, <li>, <p>, and <span>.
Please note that HTML changes made to News Items that are displayed on app versions older than 1.61 may not be fully supported in those versions and could lead to less-than-desirable results.
🐞 Fixed a bug where Document Hub users in Arizona saw incorrect timestamps on submitted documents within the Document Hub. Arizona does not observe Daylight Saving Time, but the Document Hub was displaying times in Mountain Daylight Time (MDT) instead of Mountain Standard Time (MST), resulting in a one-hour discrepancy.
🐞 Fixed a bug where the user would see an infinite redirect error when attempting to access an App Manager link for which they did not have permissions.
🐞 Fixed a bug where old pre-fill values on components in App Manager would not get cleared when the underlying form did not have a field that matches the defined pre-fill.
