November 2025 - Build 1.4.1

Prev Next

Changes to the Mobile Apps Login Process

Starting January 20, 2026, both the Mobile Payments and Mobile Check-in apps may require new users to activate their devices during the Salesforce login process. The Salesforce article, “Device Activation for Salesforce Orgs,” explains the device activation process.

Whether a new user needs to activate their device will be determined by the customer’s org settings. Additional information can be found here: “Changes to Device Activation for Single Sign-On (SSO) Logins.”

Important Changes to the Blackthorn | Events (Lite User) Permission Set

  • The Blackthorn | Events (Lite User) permission set now only includes Read access for the Event object. If you are using the latest version of the Mobile Check-in app, please review the permissions for existing users to confirm they still have Edit access to the Event object.

  • Read-only permissions were added to the Blackthorn | Events (Lite User) permission set for the following objects:

    • Account

    • Contact

    • Badge Printing Configuration (conference360_Badge_Printing_Configuration_c)

  • Read-only permissions were added for the following fields:

    • Object: Badge Printing Configuration

      • Length Unit (conference360_Length_Unit_c)

      • Orientation (conference360_Orientation_c)

      • Page Height (conference360_Page_Height_c)

      • Page Width (conference360_Page_Width_c)

    • Object: Contact

      • Email (Email)

  • Additional permissions for the Blackthorn | Events (Lite User) permission set were added to the Mobile Check In Submission (conference360_Mobile_Check_In_Submission_c) object and fields.

    • Create and edit permissions were added for the Mobile Check In Submission object.

    • The following fields now have edit permissions:

      • Attendees JSON (conference360_Attendees_JSON_c)

      • Errors (conference360_Errors_c)

      • Status (conference360_Status_c)

Bug Fixes

  • Log-in Session: If a current Mobile Check-in app session expires, the app will prompt the user to log in again, allowing them to refresh the app’s lists with data from Salesforce. Previously, the app didn’t prompt the user to log in again, which prevented the sync feature from working and caused the app to use only cached data.

  • Permission Sets: Users who have the Blackthorn | Events (Lite User) permission set but do not have a Salesforce admin profile can log in successfully to the Mobile Check-in app.  Previously, those users received an OAuth error when attempting to authorize the Mobile Check-in app. (Known Issue: 000005042)

  • Badge Printing: If the QR Badge Print pop-up is enabled, it will appear as expected after checking in an Attendee. Previously, the app bypassed the badge printing pop-up after scanning a QR code to check in an Attendee and went directly to the Attendee details page, even though the app’s "QR Badge Print Popup" setting was set to “Enable.”

Android Only

  • Android device users can now use the “Login with Biometric” feature to log into the Mobile Check-in app. Previously, the pop-up to enable biometric authentication was not shown to Android users after they successfully logged in to the app.

Permission Set Requirements

If you are using the latest version of the Mobile Check-in app, please review any new permission set requirements introduced in this release.

Enhancements

  • Offline Mode: If a Mobile Check-in app user scans an Attendee’s QR code when their internet connection isn’t working, they will see a “Connection error while fetching contact” message instead of “Contact not found.”

Custom Fields

  • On the Attendee Details page, users will see the following information:

    • Custom fields associated with the Attendee, such as Dietary Preference and Table Number

    • Values from the custom fields, such as “vegetarian” and “7”

Attendee Group Management

  • An Attendee Group check-in page has been added to the app, allowing users to bulk check in/check out Attendees in an Attendee Group.

  • Users can access the Attendee Group page by clicking the View Group button on the Attendee Details page of an Attendee in the Attendee Group.

  • Users will see the following information on the Attendee Group Details page:

    • Custom fields associated with the Attendee Group

    • Custom fields related to each Attendee in the Attendee Group

  • Clicking an Attendee’s name will take the user to that Attendee’s information, where the user can view any custom fields and the Attendee’s check-in status.

Badge Printing

  • On the Attendee Details page, users can click the Print Badge button to print a badge for the specified Attendee. The badge will include the Attendee’s details, including information in custom fields.

Offline Mode Enhancements

  • A yellow status bar at the top of the app indicates when offline mode is active.

  • If the app is in offline mode, the Turn Off Offline Mode button will appear when internet connectivity is restored.

  • Attendees who are checked in/checked out when the device is offline will be saved to the device until the device goes back online. At that point, the saved changes are synced with Salesforce.

  • If a user tries to sync a change while the device is offline, they will have the option to remain offline or click the Turn Off Offline Mode button.

Swift Mode

  • If a user’s mobile device is offline and they click the Send Changes button after checking in Attendees with Swift Mode Check-in, they will see the following message: “No internet connection. Please check your network and try again.”

  • When using Swift Mode’s Continuous Scan mode, a 1.5-second delay occurs after the Event Staff scan each QR code to prevent a single QR code from being scanned multiple times.

  • When checking in/out Attendees from the Attendee list screen, users only need to swipe the Attendee’s name left or right. Previously, users had to swipe the name and click a button to complete the step.

Android Only

  • The Mobile Check-in app is compliant with the Google Play Photo and Video Permissions policy regarding the use of READ_MEDIA_IMAGES and/or READ_MEDIA_VIDEO permissions. Now, when a user is on the Attendee Details Badge tab, the app will only use the CAMERA permissions for taking photos instead of using the READ_MEDIA_IMAGES and/or READ_MEDIA_VIDEO permissions.