Bright Pattern Mobile App Version 3.2 Release Notes
New Features
Multi-Factor Authentication Support
The Mobile App now supports Multi-Factor Authentication (MFA). Mobile users are subject to the same MFA policy configured for your contact center in Contact Center Administrator > Security > Security Policy. One-time passwords (OTP) via email and time-based one-time passwords (TOTP) from an RFC 6238 compliant authenticator app are both supported as a second factor.
A TOTP secret can be set up either by scanning a QR code, as in the browser-based Agent Desktop, when the authenticator app is on a different device, or by launching the device's default authenticator app directly when it is on the same device as the Mobile App.
Initial TOTP setup, TOTP setup grace periods, and administrative TOTP resets all behave the same for mobile users as for desktop users.
Behavior Change
Updated Login Flow
The login screen has been changed slightly; the contact center domain is now entered on the initial page, and the user credentials (username and password) are entered on the next page. Android and iOS password managers can be used to auto-fill credentials.
After the username and password are accepted, users for whom MFA is enabled are presented with the MFA challenge.
This login flow displays only if your contact center uses the new authentication service, otherwise you will continue to see the legacy flow.
Compatibility
This version of the Mobile App requires:
- Bright Pattern Contact Center 5.36 or later
- Users Authentication 1.4 or later
iOS
- Any iPhone model running iOS 16 through iOS 26, except the following:
- iPhone 6s
- iPhone 6s Plus
- iPhone SE (1st generation)
Android
- Stock Android 14 to 17 (for example, Google Pixel 8a)
- Samsung Galaxy with One UI 6 or later
- Xiaomi with HyperOS 2
- Zebra TC52 with Android 14
Known Issues
| Issue ID | Summary | Detail |
|---|---|---|
| 47921 | Trust this browser has no effect in the Mobile App | When Enable trusting a browser as a second factor in MFA is enabled, selecting Trust this browser in the Mobile App does not suppress the MFA challenge on subsequent logins. |
| 47679 | Internal chat with Agent Desktop 2.0 users does not work | Internal chat messages between a Mobile App user and a user on Agent Desktop 2.0 are not delivered in either direction, and no notifications are raised. |
| 47667 | Android: "Unknown messenger type" system message after sending a picture or file | On Android, after an agent sends a picture or a file in a web chat, an extra system message reading "Unknown messenger type" appears in the chat. The picture or file itself is sent and received correctly. |