--- sourceDocument: Mobile App Release Notes sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/mobile-release-notes Release : - mobile ft:locale : - en-US ft:publication_title : - Mobile App Release Notes ft:clusterId : - rnmo bundleId : - rnmo --- # Now Support for iOS v20.1.0 # Now Support for iOS v20.1.0 {#ariaid-title1} Release version: Mobile Updated July 10, 2025 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) 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 Support for iOS v20.1.0 The Now Support for iOS v20.1.0 release, updated on July 10, 2025, addresses several issues within the application, enhancing performance and user experience. Users can download the latest version from the Apple App Store and explore the Mobile Agent through a demo account. Show full answer Show less ## Key Features * Fixes for file attachment issues with Unicode filenames. * Resolves problems with uploading catalog items with 'Variable' type attachments. * Addresses data visualization issues on iOS dashboards. * Corrects WebView reloads when transitioning from background to foreground. * Ensures deep links open within the app rather than in external browsers. * Fixes Quick Links functionality to prevent 'Invalid URL' errors. * Enhances actionable notifications for users logged into multiple instances. * Improves mobile UX analytics data collection. * Adds missing seat number labels on indoor maps. * Resolves UI rule visibility issues on record refresh. ## Key Outcomes With this update, users can expect improved functionality in file handling, better performance in dashboards, and enhanced notification features. These fixes contribute to a smoother and more efficient user experience on iOS devices, allowing for effective task management and improved accessibility of app features. The iOS v20.1.0 release provides fixes for the application. ## Download the latest mobile app version {#nowsupport-ios-v20-1-0__szp_lzn_1tb} To download the latest release, visit the [Apple App Store](https://apps.apple.com/us/app/servicenow-agent/id1446951408). 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 {#nowsupport-ios-v20-1-0__xnx_lzn_1tb} {#nowsupport-ios-v20-1-0__AllOtherFixes__entry__4} | 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. {#nowsupport-ios-v20-1-0__ol_x2d_g2j_xfc} 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 ReservationSee All. 2. Select DeskBrowse All. 3. Fill all details. 4. Choose a Floor and uncheck All day, then select NextLocationSubmit. 5. Select Get Directions on the created record. {#nowsupport-ios-v20-1-0__ol_uqv_l2j_xfc} 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. {#nowsupport-ios-v20-1-0__ol_tq1_v2j_xfc} Observe that the previously hidden UI element is now visible. | [ ] {#nowsupport-ios-v20-1-0__AllOtherFixes} This version also includes other minor bug fixes and performance improvements. *[\>]: and then