---
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 Classic iOS v4.1

# Mobile Classic iOS v4.1 {#ariaid-title1}

Release version: Mobile  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
The Mobile Classic iOS v4.1
release provides problem fixes.

## Download the latest Mobile Classic version {#classic-ios-v4-1__section_nqy_3vr_nsb}

To download the latest release, visit the [Apple App Store](https://itunes.apple.com/us/app/servicenow/id1044428492?mt=8).  
Important:  
There are several new ServiceNow mobile apps, including Mobile Agent, Now Mobile, Mobile Onboarding, and Now Support. Check out these new apps for the latest features and capabilities.

## Fixed in this release

{#classic-ios-v4-1__tbl_AllFixes__entry__4}

| Problem | Short description | Description | Steps to reproduce |
|-|-|-|-|
| Mobile PRB714483 | Authentications fails using SSO when the property 'glide.security.csrf.strict.validation.mode' is set to 'true' | When the Multi-Provider SSO and OAuth plugins are enabled, and a user attempts to authenticate with the iOS app, they receive the following error message: "Error Completing OAuth Flow - Request failed with response code: 401". | 1. Configure SSO with the multi-provider plugin enabled. 2. Follow [these steps](https://support.servicenow.com/kb_view.do?sysparm_article=KB0564232) to configure SSO for the iOS app. 3. Set the property 'glide.security.csrf.strict.validation.mode' to true. 4. Attempt to authenticate via SSO IDP with the iOS app. Note that you receive the error message: "Error Completing OAuth Flow - Request failed with response code: 401". |
| Mobile PRB732741 | Actionable push notifications did not show error message | This issue occurs when the action failed if it was due to an invalid session. |   |
| Mobile PRB733630 | Scorecard target color scheme is calculated incorrectly for maximizing indicators | When using Performance Analytics in the iOS app, the target color scheme is not being properly applied to maximizing indicators. | 1. Favorite some maximizing indicators. 2. Compare the color scheme on the platform and the iOS app. |
| Mobile PRB734880 | Users cannot be removed when creating a new chat conversation | When user A creates a new chat and adds user B to the conversation, user A cannot remove user B from the chat. | 1. Start a new Connect conversation. 2. Add a user by typing in their name. 3. Attempt to remove that user. Expected result: You should be able to remove the user. Actual result: You cannot remove a user once you have selected the user. |
| Mobile PRB736838 | Native mobile apps should support "Accept / Decline" push notification buttons |   |   |
| Mobile PRB737193 | The fill gradient below iOS charts is incorrect | This issue occurs when using Performance Analytics in the iOS app. By default, iOS charts apply a fill gradient to the surface area of each individual dataset between the value line and the 0-line of the x-axis. This works as expected if all values are positive, but it becomes strange if there are negative values involved. When negative values are present, the fill gradient is below the value line for the positive values and above the value line for negative values. Users expect the fill gradient to always fill the surface below the value line, regardless if the values are positive or negative. | View an indicator that has negative values. |
| Mobile PRB737651 | Gap, gap percentage and gap color should respect direction and negative targets | When using Performance Analytics in the iOS app,The gap, gap percentage, and gap color should respect the indicator direction. |   |
| Mobile PRB738454 | Actionable push notifications should navigate to the record/web path if the action is a foreground action |   | 1. Receive a foreground actionable push notification (e.g. approve_reject_foreground). 2. Tap an action (e.g.Approve). Expected result: App should launch and navigate to the record. Actual result: App launches and does not navigate to the record. |
[ ]

{#classic-ios-v4-1__tbl_AllFixes}