Now Mobile for BlackBerry for iOS v20.1.0

  • Release version: Mobile
  • Updated July 10, 2025
  • 3 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Now Mobile for BlackBerry for iOS v20.1.0

    The iOS v20.1.0 release of Now Mobile for BlackBerry introduces several bug fixes and enhancements to improve application performance. This version is available for download from the Apple App Store and includes a demo feature for users to explore the Mobile Agent functionality.

    Show full answer Show less

    Key Features

    • Improved File Attachments: Fixes issues with Unicode filenames being incorrectly encoded.
    • Catalog Item Uploads: Resolves problems with uploading 'Variable' type attachments.
    • Dashboard Functionality: Corrects data visualization issues on iOS devices.
    • WebView Behavior: Addresses issues with the app reloading when transitioning from background to foreground.
    • Deep Linking: Ensures that deep links open within the app rather than in an external browser.
    • Quick Links Access: Fixes the 'Invalid URL' error encountered when using Quick Links.
    • Actionable Notifications: Rectifies issues with notifications not triggering correctly when multiple instances are logged in.
    • UX Analytics Collection: Addresses failures in mobile UX analytics data collection due to certificate issues.
    • Indoor Mapping Enhancements: Displays missing seat number labels on maps when using 'Get Directions.'
    • UI Rules Preservation: Ensures UI rules are maintained after a record refresh.

    Key Outcomes

    This update enhances user experience by resolving critical bugs and improving overall application performance. Users can expect smoother functionality when uploading attachments, navigating dashboards, and interacting with notifications. By downloading this version, customers will benefit from a more reliable and efficient mobile application experience, ultimately leading to improved operational workflows.

    The iOS v20.1.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

    Mobile iOS

    PRB1887761

    		 File attachments using a Unicode filename show a percentage encoded A filename containing Unicode characters is sent as a percentage encoded by the instance. As such, for presentation purposes, the filename should have the percentage encoding removed / decoded. This is caused by FileAttachmentView's using the FileMetaData.filename in the UI.

    Mobile iOS

    PRB1897716

    		 The user is unable to upload a catalog item with a 'Variable' type attachment

    The user can't upload 'Attachment' type variables. The variable must map to a field of sys_dictionary type 'Image'.

    Mobile iOS

    PRB1903899

    		 Data visualization is broken on iOS Dashboards do not work on iOS devices.

    Mobile iOS

    PRB1898263

    		 WebView reloads when the app goes from background to foreground even if the session is not expired This issue occurs with a client on version 20.x and an instance earlier than Zurich.

    Mobile iOS

    PRB1881945

    		 A deep link URL is loaded on an external browser instead of inside the Mobile App When a deep link is opened from inside the chat, the link should load inside the app. However, an external browser opens and loads the URL.

    Mobile iOS

    PRB1900982

    		 Quick Links in the iOS Now Mobile App do not open properly Quick Links function properly in the desktop version, but in the mobile version, selecting a link results in an 'Invalid URL' error.

    Mobile iOS

    PRB1890821

    		 Actionable notifications do not function properly on iOS On iOS, actionable notifications do not function properly. If the user is logged into multiple instances in the app and an actionable notification is triggered from a development instance, the actions do not appear.
    1. Trigger an actionable push notification from a development instance.
    2. Have multiple instances opened in the app.

      Notice that there is no push notification generated for the app in iOS devices.

    3. Remove other instances and keep the development instance logged in within the app.
    4. Trigger the actionable push notification from the development instance.

    Expected behavior: A push notification is seen when triggered, irrespective of single/multiple instances logged in.

    Actual behavior: There is no push notification action generated for the app in iOS devices.

    Mobile iOS

    PRB1891026

    		 Mobile UX analytics data collection fails due to a change in the certification authority UX analytics data for mobile applications is not collected due to an unsupported certificate installed on the analytics API.

    Mobile iOS

    PRB1891192

    		 A seat number label is missing from an indoor map A space name is not displayed when using 'Get directions' after making a reservation on iOS mobile
    1. Select Make a Reservation > See All.
    2. Select Desk > Browse All.
    3. Fill all details.
    4. Choose a Floor and uncheck All day, then select Next > Location > Submit.
    5. Select Get Directions on the created record.

    Expected behavior: The floor is opened and the seat number (for example, 411B is displayed on the map).

    Actual behavior: The text 411B is not displayed on the map.

    Mobile iOS

    PRB1860594

    		 UI rules are lost on a record form upon refresh When a record is refreshed, the app looks for the record's parent which is the embedded form. The embedded form's ID cannot be used to reference the correct record in the cache because it is contained in the cached list screen.
    1. Create a list screen of embedded forms for the instance.
    2. Create a UI Rule that hides a certain element in the header of the record to be refreshed later.
    3. Navigate to one of the records.

      Observe that the UI element is hidden (The UI rule is observed).

    4. Refresh the record.

    Observe that the previously hidden UI element is now visible.

    This version also includes other minor bug fixes and performance improvements.