--- 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 --- # Mobile Onboarding for iOS v11.3.1 # Mobile Onboarding for iOS v11.3.1 {#ariaid-title1} Release version: Mobile Updated January 25, 2021 ![](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 Mobile Onboarding for iOS v11.3.1 The iOS v11.3.1 release enhances the Mobile Onboarding application with important fixes and performance improvements. Users can download the latest version from the Apple App Store and can also explore a demo version of the app. Show full answer Show less ## Key Features * **Bug Fixes:** The release addresses multiple issues, including crashes, notification errors, and input problems, ensuring a smoother user experience. * **Accessibility Improvements:** Several accessibility-related issues have been resolved to enhance usability for all users. * **Compatibility:** This version is compatible with Quebec Early Availability instances. ## Key Outcomes By updating to this version, customers can expect improved app stability and functionality, including: * Resolution of the 'Clear All' function issue in Notifications. * Fixes for app crashes on launch and errors related to user authentication. * Improved handling of dependent fields and comment input, including support for Kanji and Korean characters. * Enhanced performance and minor bug fixes that contribute to an overall better onboarding experience. The iOS v11.3.1 release provides fixes for the application. ## Download the latest mobile app version {#onboarding-ios-v11-3-1__fl3_zvw_wmb} To download the latest release, visit the [Apple App Store](https://apps.apple.com/us/app/servicenow-onboarding/id1472486882). Users can launch a demo to try the Mobile Onboarding app. You can use a demo account from the initial post-download screen or the instance list screen. ## Fixed in this release {#onboarding-ios-v11-3-1__nl3_zvw_wmb} {#onboarding-ios-v11-3-1__table_rbw_2jr_2jb__entry__4} | Problem | Short description | Description | Steps to reproduce | |-|-|-|-| | Mobile iOS (non-classic) PRB1449993 | Issue with the 'Clear All' function within the Notification section | | | | Mobile iOS (non-classic) PRB1459475 | The app crashes when launching | | | | Mobile iOS (non-classic) PRB1416381 | Dependency field issue with choices | The dependent field is not clearing out if the choice is changed when the action item type is set to 'Script'. | | | Mobile iOS (non-classic) PRB1454492 [KB0868589](https://support.servicenow.com/kb_view.do?sysparm_article=KB0868589) | The error 'User Not Authenticated' appears when navigating in the app | Users are getting the following error when navigating in the app: "error":{"message":"User Not Authenticated","detail":"Required to provide Auth information"},"status":"failure". | Refer to the listed KB article for details. | | Mobile iOS (non-classic) PRB1454452 | The 'Assigned to' field is not cleared out after the 'Assignment group' field is changed | | | | Mobile iOS (non-classic) PRB1453396 | When scrolling down on the list, the text jumps to the right of the screen | | | | Mobile iOS (non-classic) PRB1452364 | The notification records under the 'Notifications' screen are displayed twice for the assigned incident when users upgrade the app | | 1. Install an older version of the mobile app and log in as the ITIL user. 2. On the platform, search for Incident in the Filter Navigator. 3. Select All, and then assign 1 or 2 incidents to the ITIL user and wait for the push notification to be received on the device. Note: Do not tap to open these notifications, else the issue cannot be reproduced. Also make sure this notification is received while the app is in the background. 4. Upgrade the app to the latest release version. 5. Open the app to navigate to the Notifications screen and verify that there should be a single record for each incident assigned. Notice that there are 2 entries for each assigned incident. | | Mobile iOS (non-classic) PRB1451090 | The system property glide. security.csrf_previous.allow needs to be set to 'True' in order to upload images in VA | | 1. In the instance, start a new Virtual Agent chat. 2. Select the topic 'ACME File Upload' and select 'Take a picture'.Notice that the image will be stuck at 'uploading...'. Expected behavior: When the system property glide. security.csrf_previous.allow is 'False', Virtual Agent should still be allowed to upload images. Actual behavior: When the system property glide. security.csrf_previous.allow is 'False', the image will be stuck at 'uploading...' when uploading the image in VA. | | Mobile iOS (non-classic) PRB1448917 | Can't input Kanji Japanese characters in comments on iOS devices | | 1. Add the Japanese language to the keyboard on an iOS device. 2. Log in to the instance on the mobile app. 3. Open any incident record. 4. Try to add comments by changing the keyboard to Kanji Japanese language. 5. Try typing 'sa-basaikidou' for example. Expected behavior: As users type 'sa-basaikidou', the characters should get auto translated to Kanji Japanese language. Actual behavior: The characters are not translated to Kanji Japanese language. | | Mobile iOS (non-classic) PRB1444878 | The iOS mobile app does not have auto-correct | | 1. Navigate to the mobile app on iOS. 2. Open an incident through any applet. 3. Open the Add comment function from the top three-dot menu. Notice that typing the work note and additional comments does not prompt the suggestions. | | Mobile iOS (non-classic) PRB1420536 | The dashboard preview is not clickable until the chart screen is loaded | | | | Mobile iOS (non-classic) PRB1456900 | The last Korean character is broken on mobile apps | | Type the content in Korean and submit. Notice that the last consonant or vowel entered is separated from the previous character. Note: It appears that the issue occurs when you type and there is no space after the text. | [ ] {#onboarding-ios-v11-3-1__table_rbw_2jr_2jb} This version also contains fixes for several accessibility-related issues and UI issues with iOS 14, as well as other performance improvements and minor bug fixes. Note: This version is compatible with Quebec Early Availability instances.