Now Mobile - Intune for Android v17.4.0
Summarize
Summary of Now Mobile - Intune for Android v17.4.0
The Android v17.4.0 release of the Now Mobile app addresses several issues to enhance user experience. Customers can download the latest version from the Google Play Store and explore the app using a demo account available post-download.
Show less
Key Features
- Bug Fixes: Several specific issues have been resolved in this update, improving app functionality.
- Performance Improvements: Enhancements have been made to increase overall app performance.
Key Outcomes
With this release, users can expect:
- Improved navigation experience, correcting back button functionality.
- Proper rendering of pre-filled PDFs, preventing file corruption issues.
- Reduced memory-related crashes when operating in offline mode.
- Elimination of duplicate list items in legacy lists, enhancing data integrity.
Overall, this update aims to streamline the user experience and resolve critical issues that may affect daily operations within the app.
The Android v17.4.0 release provides fixes for the application.
Download the latest mobile app version
To download the latest release, visit the Google Play store. Users can launch a demo to try the ServiceNow Agent app. You can use a demo account from the initial post-download screen or the instance list screen.
Fixed in this release
| Problem | Short description | Description | Steps to reproduce |
|---|---|---|---|
|
Mobile Android PRB1739688 |
The user is unable to follow links to third party apps | ||
|
Mobile Android PRB1729686 |
PDFs with pre-filled form data do not render properly | Pre-filled PDFs with fonts that aren't embedded result in a corrupted file. | |
|
Mobile Android PRB1735791 |
The Back button sends the user to the main screen instead of the previous screen |
Expected behavior: The user is directed to the previous screen. Actual behavior: The user is directed back to the screen. |
|
|
Mobile Android PRB1741217 |
A blank screen or crash occurs after an action is performed in offline mode | When Android is in offline mode with large documents in memory, an action may result in the Android OS killing the activities in the back stack. If the action is on a form screen and requires user input from a form, the memory pressure increases. The TabsActivity may get killed by the OS, and the form screen view model is then cleared. As a result, the bundle containing the form template is no longer available. This results in a blank screen. | |
|
Mobile Android PRB1744555 |
Unnecessary getGroup requests are sent to mobile scripts when the user reaches the bottom of a legacy list | Swiping up after reaching the end of the list sends additional getGroup requests to mobile scripts, resulting in duplicate list items. |
Expected behavior: The client stops sending getGroup requests. Actual behavior: Additional getGroup requests are sent to mobile scripts, resulting in duplicate list items. |
This version also includes other minor bug fixes and performance improvements.