Mobile Agent - Intune for Android v19.4.0
Summarize
Summary of Mobile Agent - Intune for Android v19.4.0
The Mobile Agent - Intune for Android v19.4.0, released on April 3, 2025, includes essential bug fixes and performance improvements for users. Customers can download the latest version from the Google Play store and can also launch a demo using a demo account available post-download.
Show less
Key Features
- Bug Fixes: This release addresses several critical issues affecting app functionality.
- Demo Account: Users can utilize a demo account to explore the app's features before fully committing.
Key Outcomes
- Improved user experience with fixes for issues such as blank notification categories and app crashes during large image uploads.
- Successful creation of almhardware records when using asset management features.
- Enhanced stability, reducing crashes when submitting catalog items and ensuring proper URL handling.
- Minor bug fixes that contribute to overall app performance.
The Android v19.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 PRB1864255 |
The notification category list appears blank | A default theme with a white text color is applied, which appears blank against a white background. |
Navigate to . Observe that notification categories titles are blank. |
|
Mobile Android PRB1862459 |
The app crashes while uploading larger images | High megapixel images (50MB) uploaded as attachments cause the app to crash. |
Observe that the app crashes. |
|
Mobile Android PRB1853593 |
alm_hardware records are not successfully created when using the Create Asset or Retire Asset buttons in Now Agent |
The serial number entered is not submitted to the back-end. Therefore, the record is not successfully created. |
Observe that the record is not created and a success message is not displayed. |
|
Mobile Android PRB1868822 |
CabrilloBackPressHandler.flowEnded() can inadvertently back the user out of the entire application | When a catalog item is submitted and the Close button is selected, the app crashes and sends the user back to the Android home screen. |
Expected behavior: The catalog item page is closed and sends the user back to the previous screen. Actual behavior: The app is closed/crashed and sends the user back to the Android home screen. |
|
Mobile Android PRB1865339 |
Default list and form screens open instead of URLs with base instance configuration | A fix for URL transformation inadvertently brings in default list and form screen builders when a URL matches a well-known platform list or record URL. |
Expected behavior: The URL opens in an internal web browser. Actual behavior: A default native list or form screen is opened. |
|
Mobile Android PRB1866637 |
A custom map's single input doesn't display in full-screen mode | When a custom map input is a single visible input, an input form screen should always display in full-screen mode. |
This version also includes other minor bug fixes and performance improvements.