Mobile Classic iOS v2.0.2

  • Release version: Mobile
  • Updated June 16, 2026
  • 2 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 Mobile Classic iOS v2.0.2 Release

    The Mobile Classic iOS v2.0.2 release focuses on resolving several issues identified in previous versions of the app. It is designed to improve stability and user experience for ServiceNow customers using the Mobile Classic iOS app. Customers are encouraged to download the latest version from the Apple App Store to benefit from these fixes. Additionally, ServiceNow offers newer mobile apps such as Mobile Agent, Now Mobile, Mobile Onboarding, and Now Support, which provide enhanced features and capabilities.

    Show full answer Show less

    Key Fixes in This Release

    • Web Session Persistence Between Logins: Fixed an issue where web session information was incorrectly retained between different user logins, causing data such as incident state updates to show changes made by the previous user.
    • Attachment Visibility on Extended sysuser Tables: Resolved a problem where attachments added via the mobile app on tables extended from sysuser were not visible in the desktop UI, and vice versa. Attachments now correctly associate with the extended table.
    • Participant Selection Loading Issue: Addressed a bug where selecting a participant without access rights caused the screen to load indefinitely, improving user navigation and error handling.
    • Record Navigation Behavior: Updated the app to direct users first to the record’s activity stream before the form view, ensuring related lists remain accessible even if the activity stream was previously skipped.
    • Push Notification Functionality: Enhanced push notifications to support actionable links that can simultaneously direct users to specific web paths.
    • Support for Initial Form Values from Query Strings: Corrected the app to properly forward query values provided by form UI actions, enabling more dynamic form behavior based on URL parameters.
    • OAuth Token Refresh for SSO Users: Fixed an issue preventing the app from saving the Client Secret during Single Sign-On authentication, allowing the app to refresh expired OAuth tokens automatically.

    What Customers Can Expect

    By updating to Mobile Classic iOS v2.0.2, ServiceNow customers will experience improved reliability when switching users, better data consistency between mobile and desktop interfaces for attachments, and smoother participant and record navigation. The enhanced push notification capabilities and OAuth token handling improve overall user engagement and authentication security. Customers should consider exploring the newer mobile apps for access to the latest ServiceNow mobile features beyond this release.

    The Mobile Classic iOS v2.0.2 release provides problem fixes.

    Download the latest Mobile Classic version

    To download the latest release, visit the Apple App Store.

    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

    Problem Short description Description Steps to reproduce

    Mobile

    PRB655317

    Web session information is being retained between logins
    1. Log in as admin.
    2. Navigate to an existing form for an incident.
    3. Log out.
    4. Log in as itil.
    5. Navigate to a form for an incident
    6. Change the state on the incident.
    7. Navigate back to the task detail page.
    Note that admin updated the state (instead of itil).

    Mobile

    PRB664865

    On tables extended form sys_user, attachments made in the new mobile app appear only when viewing the record in the mobile app When an attachment is added to a record on a table extended from sys_user using the new mobile app, the attachment is not visible when viewing the same record in the desktop UI. The also happens in the reverse, meaning attachments made in the desktop UI are not visible in the mobile app. This does not appear to happen for other extended tables, we were only able to reproduce this issue extending from sys_user.

    When looking at sys_attachment records, it appears that the attachment is attached to the sys_user table table rather than the extended.

    1. Create a new table extended from the sys_user table. You will need to update the table record for sys_user to make this extendable.
    2. Create a new record on the extended table.
    3. Open the record created in step 2 in the Mobile App.
    4. Using the mobile app, attach a file to the record.
    5. Back in the desktop UI, view the same record. Note that the attachment is not visible.
    6. Open sys_attachment list and look for the attachment (it should be the most recently created one).
    Note that it shows sys_user as the table rather than the extended table.

    Mobile

    PRB666692

    When a user selects a participant that they do not have access to, the screen shows loading indefinitely
    1. Log in as a customer with incidents.
    2. Navigate to an incident.
    3. Open participants.
    4. Select one that you do not have access to.
    Notice that the page never loads.

    Mobile

    PRB667105

    Mobile app should go to the record activity stream before going to the form for all lists Related lists are not shown: if a user skipped showing the activity stream for a record, there would be no way to view related lists for that record.

    Mobile

    PRB667570

    Push notifications should be able to be actionable and support linking to a web path Push notifications for users cannot be actionable and support linking to a web path simultaneously.

    Mobile

    PRB668492

    Native app should support initial form values from query The iOS app does not forward query values provided by form UI actions.

    Mobile

    PRB668615

    Mobile app should be able to refresh expired OAuth tokens for SSO users The Client Secret is not being saved during the SSO authentication flow.