1. Home
  2. Announcements
  3. Release Notes
  4. SNAPmobile Release Notes – v3.1

SNAPmobile Release Notes – v3.1

This article outlines the new features, improvements and bug fixes for SNAPmobile 3.1.

Main Features

  • Upon entering a user login, the keyboard for the password text field will now include a “Use Saved Password” button that will allow the user to authenticate and login using biometrics/passcode.
  • Improved SNAPmobile iOS handling of received chat notifications. All notifications from a single chat conversation will be removed once the app has been opened and the conversation has been viewed.


  • Removed the ability for SNAPmobile iOS to use its dark mode on the application’s login page. Changed to prevent an odd display issue caused by branded applications that do not use an application logo image with a transparent background.
  • Added an improvement where chat push notifications will now include an image preview for chat messages that contain an image.
  • Add a persistent notification to SNAPmobile iOS to inform the user when the app loses internet connectivity.
  • Added a feature where pulling down on a chat notification will allow the user to select a quick reply option to reply to the message directly from the notification without having to open the app.
  • Resolved a condition where SNAPmobile iOS could crash if too many contact presence or chat availability updates were received simultaneously.
  • Added improvement to disable the Start Call button until the applications SIP client is fully registered, preventing outbound calling issues.
  • The application now tries to restore the previous Google SSO login after the application’s API access token and refresh tokens have expired.
  • Added support for dark mode in SNAPmobile iOS.
  • SNAPmobile iOS will now show custom contact labels in iPhone contacts such as ‚”Work” or ‚”DID” when viewing contacts saved to a user’s phone.
  • When selecting “All” from the contacts drop-down filter, ‚”iPhone” contacts are included/displayed.

Bug Fixes

  • Fixed an issue where expanding multiple rows of greetings would jumble up the user interfaces.
  • Fixed an issue where a user receives call notifications after they have logged out. Attempts to answer or end incoming calls resulted in a crash.
  • Fixed an issue where a user was unable to scroll through a long list of available SMS numbers when starting a new conversation.
  • Resolved an issue where MFA-enabled users would encounter app performance issues when their API access/refresh tokens expired.
  • Resolved a condition that could cause a voicemail to display an incorrect duration.
  • Cleaned up a segment of code that did not correctly URL encode Click-to-Call API requests. If allowed server-side, this allows a callback number to be prefixed with a “+” sign.
  • Changed the code to allow the user to change the audio source/destination during call setup. Previously, the audio source/destination could only be changed once the call had connected.
  • Improved logic in the application related to the handling of expired API access and refresh tokens. To better support customers with non-default access token expiration times, SNAPmobile iOS will now check for an expired warning header in HTTP replies from the API and will more efficiently handle obtaining new tokens with saved user access credentials.
  • Made improvements to the app registration process when terminating the app and then receiving an incoming call push notification.
  • Improved code used to create a Group Chats unique session identifier. Prevents a condition that could cause one conversation to appear as two separate conversations.
  • SNAPmobile iOS will now hide the ‚”Call using Mobile Phone” option in the application if the user has not already set their mobile number.
  • Fixed an issue where some chat messages were not being shown due to a timezone mismatch.
  • Resolved a crash condition edge-case that could occur if multiple presence updates were received by SNAPmobile iOS at the same time.
  • Added an extra check to prevent messages received redundantly from being added to a conversation.
  • Resolved a condition that could cause all SMS messages in a conversation to appear as messages sent by the user.
  • Fixed an issue where SNAPmobile Web was not receiving all messages sent from SNAPmobile iOS due to a timestamp error.
  • Added functionality to CallKit’s add call button which will open up SNAPmobile to add another call.
  • Improved application code to continually sort the list of chat conversations such that conversations will now always appear in the order of their last received message.
  • SNAPmobile iOS will now correctly failover to the next available server if a SIP 503 is received.
  • Various clients reported issues with logging out of SNAPmobile but still receiving Push notifications for the logged-out User.  This issue has been resolved and ensures a clean logout occurs and explicitly clears user data and authorization tokens.
Updated on June 2, 2021

Was this article helpful?

Related Articles

Need Support?
Can't find the answer you're looking for?
Contact Support