Mobile Classic iOS v2.0.1

  • Release version: Mobile
  • Updated June 11, 2026
  • 1 minute to read

    • The Mobile Classic iOS v2.0.1 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

    PRB654843

    		 App cannot connect to a server with the glide.security.csrf.strict.validation.mode property set to true Enabling glide.security.csrf.strict.validation.mode renders an instance incompatible with the iOS app.
    1. Enable glide.security.csrf.strict.validation.mode.
    2. Attempt to log in.
    Note the 401 error.

    Mobile

    PRB654847

    		 AMB occasionally fails after backgrounding the app After backgrounding the app, it is possible that an AMB/Bayuex Connect message will fail. The 'in flight' connect message is not cleared out in this scenario, and AMB does not reconnect.

    Mobile

    PRB655491

    		 Pins are not showing on map modules To set up the server:
    1. Navigate to a map page record from the cmn_map_page table.
    2. Copy the sys_id for the record.
    3. Navigate to a mobile app record from the sys_ui_application table.
    4. On the sys_ui_module table, add a new module to this app.
    5. Set the path to map/id where the ID is the sys_id of the map record from the cmn_map_page table.
    Steps to reproduce:
    1. Log into a Geneva instance.
    2. Navigate to the new map module via the Navigator screen (Maps > All Locations).
    Note that the pins are not showing on the map.

    Mobile

    PRB656174

    		 If no primary IDP is set for an instance, login fails
    1. Configure SSO on an instance.
    2. Via the glide.authenticate.sso.redirect.idp system property, verify that there no primary identity provider is set.
    3. Add the instance in the mobile application.
    4. Enter in a username.
    5. Tap on the Use External Login link.
    Note that instead of being redirected to the external IDP that was set up for the user, the following error occurs: 'No external identity provider found for the username: admin'