Now Support for iOS v20.4.0

  • Release version: Mobile
  • Updated October 2, 2024
  • 1 minute to read

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

    PRB1931580

    		 Intermittently, there's fetch errors when a user submits some records The user sees an error, either 'For Requestfor.NOWAPIError4 (Requestfor.NOWAPIError)' or 'Fetch error, please check fetch status'.
    1. Create a list of work order tasks in the 'Form' screen.
    2. Each task needs to have a link to a 'Cabrillo' page.
    3. The 'Cabrillo' page should contain a button to upload images or files.
    4. After selecting the images, or files through the upload manager, select the 'Back' menu to return to the 'Form' screen.

    Expected behavior: The user sees a list of work order tasks without an error.

    Actual behavior: The user sees a list of work order tasks and with error.

    Mobile iOS

    PRB1924641

    		 The chat icon is unresponsive when the user returns to the chat after accessing an incident and deleting an attachment The user must to log out and log in again to access the chat.
    1. Select the chat icon.
    2. Select the Check ticket and status topic.
    3. Once the incident is displayed, select View record.

      The incident opens.

    4. Add an attachment.
    5. Delete the attachment.

      The user is redirected to home screen.

    6. Select the chat icon.

    Expected behavior: The chat should open.

    Actual behavior: The chat icon does not respond, and the user must to log out and log in again to access the chat.

    Mobile iOS

    PRB1932213

    		 AppAuth doesn't launch Safari when the default browser is not Safari On iOS, when the device default browser is set to a non-Safari browser and SNAuthenticationBrowseriOS is set to Safari, authentication launches in the default browser, not Safari.
    1. Set a device's default browser to any non-Safari browser (Chrome/Edge).
    2. Log in to an instance.

    Expected behavior: Users are able to launch authentication in a Safari browser.

    Actual behavior: Users are launching authentication in the default non-Safari browser.

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