Now Mobile for BlackBerry for iOS v21.3.0
Summarize
Summary of Now Mobile for BlackBerry for iOS v21.3.0
The Now Mobile for BlackBerry iOS app version 21.3.0, released on May 5, 2026, focuses on resolving multiple application issues and improving stability. Customers can download this latest version from the Apple App Store and also try a demo experience using a demo account provided after download.
Show less
Fixed Issues and Improvements
- Reservation Date Error: Corrects the default date on the reservation screen to show the current day instead of the previous day.
- Date Display Consistency: Aligns scheduled start and estimated end times between the mobile app and the platform for accurate time tracking.
- File Upload Stability: Fixes crashes and stuck uploads occurring during file attachment uploads when impersonating another user.
- Crash Prevention: Resolves fatal integer overflow crashes related to badge count on iOS devices.
- Writeback HTTP 500 Error: Addresses server errors when submitting actions that have both parameter screens and automatic redirection configured, ensuring successful writeback submissions.
- Session Refresh Behavior: Restores the user’s last visited page upon session timeout or pull-to-refresh to improve navigation continuity.
- Action Form Responsiveness: Fixes freeze issues with Submit and Cancel buttons after server-side writeback errors, allowing users to retry or cancel properly.
- Filter Button Visibility: Ensures the Filter button appears correctly on list screens after pagination loads more items.
- Notification Instance Alert: Prevents unnecessary instance change alerts when tapping notifications from the same instance.
- Smart Assessment Stability: Corrects crashes caused by rich text descriptive elements in questionnaires, allowing assessments to open correctly.
- Offline Attachment Visibility: Ensures photos added on new defect forms while offline appear immediately in Attachments and Activity Stream without needing sync.
Practical Impact for ServiceNow Customers
This release enhances the reliability and user experience of the Now Mobile for BlackBerry iOS app by fixing critical bugs that impacted daily operations such as reservations, task updates, file uploads, and offline defect reporting. Customers can expect smoother workflows, reduced crashes, and improved data accuracy between the app and the ServiceNow platform. These improvements contribute to efficient mobile agent operations and better field service execution.
The iOS v21.3.0 release provides fixes for the application.
Download the latest mobile app version
To download the latest release, visit the Apple App Store. Users can launch a demo to try the Mobile Agent. 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 |
|---|---|---|---|
|
iOS Mobile PRB1991062 |
Default date in the reservation screen is set to yesterday instead of today | The default date automatically fills the Date field on the 'Make a reservation' screen with yesterday's date instead of today. |
Notice that the auto-filled date is not the current date. |
|
iOS Mobile PRB2001344 |
The date shown on the mobile device is not the same one displayed in the platform | Scheduled start and Estimate end time is not the same between the Mobile Agent App on iPhone and the platform. | |
|
iOS Mobile PRB2006489 |
A NSGenericException Task gets created in a session that has been invalidated | File upload gets stuck or the app crashes while uploading files in impersonation mode. |
Expected behavior: The upload should be successful. Actual behavior: The upload gets stuck and the app intermittently crashes. |
|
iOS Mobile PRB2011334 |
The Agent app crashes on iOS devices | When the user has a badge count over a certain value, the initializer traps with a fatal integer overflow, causing the app to crash. | |
|
iOS Mobile PRB2006738 |
iOS writeback returns HTTP 500 when an action has a parameter screen and AutoRedirectDestinationId is configured | When an action has both a parameter screen (ParameterData) and an AutoRedirectDestinationId configured server-side, the iOS mobile client includes DestinationSubmittedForm in the writeback request alongside ParameterData. The server does not accept this combination and returns HTTP 500. |
Expected behavior: The writeback request is submitted successfully. The server responds 200 and the WOT is closed. Actual behavior: The server returns HTTP 500 and the WOT close action fails. |
|
iOS Mobile PRB2011561 |
Restore the last page when pulling to refresh or session timeout | When the user reactivates their hybrid webpage session after timeout (due to inactivity, backgrounding, or locking) or performs a pull-to-refresh, they are not returned to their last visited page. | |
|
iOS Mobile PRB2009678 |
Submit/Cancel buttons freeze after a writeback error on an action item form | When filling in an action item form (for example, a labor action item on a case), submission returns a server-side error. The error banner is shown correctly but the Submit and Cancel buttons on the form become completely unresponsive. The user cannot retry submission or dismiss the form — the only recovery is to force-close the app. |
Expected behavior: Selecting Submit retries the writeback. Selecting Cancel dismisses the form. Actual behavior: Both Submit and Cancel are completely unresponsive. |
|
iOS Mobile PRB2004817 |
The Filter button on list screens is hidden when the initial page load returns only one item and never re-appears after more items load via pagination | The Filter button should be shown on the top-right of the list screen if more than one item is displayed, but it doesn't appear. | |
|
iOS Mobile PRB2011924 |
Change Instance Alert is shown to the user when a notification is tapped on in the 'Notifications' tab for the same instance | ||
|
iOS Mobile PRB2007442 |
A smart assessment crashes when a descriptive element is set as richText | The application crashes. |
|
|
iOS Mobile PRB2008581 |
An offline new-defect form photo is not visible in the Attachments/Activity Stream until sync | When a new record is created offline via the New Defect Form, callAddAttachmentsScript (CellsContainerTemplateHandler+Redirection.swift) returns early without calling addParameterScreenAttachments, so the offline document cache is never updated with the form-input attachment. |
Expected behavior: The form photo is visible in Attachments and Activity Stream immediately after the defect is created, without requiring sync. Actual behavior: The form photo is invisible until sync completes. |
This version also includes other minor bug fixes and performance improvements.