Mobile Classic iOS v4.0

  • 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 v4.0 Release

    The Mobile Classic iOS v4.0 release focuses on resolving key issues identified in prior versions of the ServiceNow Mobile Classic app for iOS. It is designed to improve app stability and functionality, particularly around image attachments, query displays, attachment access, and single sign-on (SSO) login flows.

    Show full answer Show less

    ServiceNow customers are encouraged to download this latest version from the Apple App Store. Additionally, customers should consider exploring newer ServiceNow mobile apps—Mobile Agent, Now Mobile, Mobile Onboarding, and Now Support—for enhanced features and capabilities beyond Mobile Classic.

    Fixed Issues and Practical Impact

    • Live Feed Attachment Issue (PRB709271): Previously, attaching images via the live feed’s paperclip icon caused the app to return to the home page without allowing image selection. This release fixes that behavior, ensuring users can successfully attach images from the camera, photo library, or iCloud within the live feed.
    • Related List Query Breadcrumb Rendering (PRB709786): On iPhone, related list query breadcrumbs were incorrectly displayed as empty spaces, causing confusion. The update ensures breadcrumbs now display meaningful information such as "Related List condition," improving navigation clarity in filtered record lists.
    • Attachment Access on Fuji Instances (PRB712207): Users running Fuji instances faced issues accessing or downloading attachments on the iPhone app. This release restores the ability to interact with attachments in incidents, ensuring seamless file access.
    • SSO Flow Session Timeout Handling (PRB713927): The app now correctly ignores instance session timeout URLs during the SSO login flow. This resolves login failures when redirects to local session timeout pages previously interrupted the SSO process, allowing users to complete authentication successfully via their external identity providers.

    What Customers Can Expect

    • Improved user experience when attaching images in live feeds without unexpected app navigation.
    • Clear and accurate display of related list query filters on iPhone, enhancing usability of filtered record modules.
    • Reliable access and download of attachments on iPhone, including instances running Fuji releases.
    • Smoother and more robust single sign-on login flows that handle session timeouts gracefully, reducing login errors.

    By updating to Mobile Classic iOS v4.0, ServiceNow customers will benefit from these targeted fixes, resulting in a more stable and functional mobile experience aligned with core ServiceNow workflows.

    The Mobile Classic iOS v4.0 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

    PRB709271

    		 Attachment option in Live Feed does not work in the native iOS app When clicking the paper clip icon in live feed to attach an image from the camera, photo library, or iCloud, the app returns to the homepage without giving the option to attach an image.

    In the iOS app:

    1. Open Live Feed.
    2. Click the red circle in the lower right to create a new live feed or comment in an existing feed.
    3. Click the paperclip icon to attach something.
    4. Click any of the options that pop up (e.g. Camera, Photo Library, or iCloud).

    Expected result: The user should get the option to attach an image, or bring up the camera interface to take an image.

    Actual result: The user is directed back to the home page. No option to select an image is shown. This seems to work as expected using Connect, but not in Live Feed.

    Mobile

    PRB709786

    		 In the iPhone app, related list query breadcrumbs are rendered as empty space, which looks like an error Instead of blank space, the iOS app should contain information such as 'Related List condition.'
    1. In the desktop interface, create a module that displays a list of records, filtered by a related list query and at least one other condition. For example, create a module of the Problem list and add the following query to the Arguments field: state=1^assigned_toISNOTEMPTY^RLQUERY incident.problem_id,>=1^ENDRLQUERY
    2. Add the module to your favorites so you can access it from the mobile UI.
    3. In the iPhone app, open the module.

    Note that the query breadcrumbs display as ', Assigned to, State'.

    Mobile

    PRB712207

    		 In Fuji, users are unable to access or download attachments on the iPhone mobile app In Fuji, attachments cannot be accessed or downloaded in the iPhone mobile app.

    In the iOS app:

    1. Access a Fuji instance.
    2. Navigate to any incident that contains an attachment (e.g. INC0000055).
    3. Attempt to interact with the attachment.

    Expected result: The attachment is accessed or downloaded.

    Actual result: Nothing happens.

    Mobile

    PRB713927

    		 Native iOS app should ignore instance session timeout URLs during the SSO flow The native iOS app should ignore instance session timeout URLs during the SSO flow. This will fix an issue where SSO would not work if the SSO flow redirected to a local session timeout page during the SSO log in flow.
    1. Attempt to log in via SSO.
    2. Get redirected to an external IDP, then to a local session timeout page, then back to the external IDP.

    Expected result: App should land on the external IDP page, and the user should be allowed to complete log in.

    Actual result: App fails to land on external IDP page, and the user is unable to log in.