20210312: 3.7.14. iOS Voalte One Application® Incorrect APNS Token

3/12/21

Purpose.

The purpose of this bulletin is to inform all hospital leaders and staff responsible for the support of devices running iOS Voalte One 3.7.14 connected to a pre 3.7.10 server about an uncovered issue with failed APNS pushes.

Background.

In rare occurrences, the iOS Voalte One 3.7.14 clients are sending the wrong APNS token to the server. This leads to failed APNS pushes. If a Voalte One client is both force quit and the wrong APNS token is sent to the server, then the user will miss their incoming notifications and will only see the notifications once the application is launched and reconnects to the server.

Note: This does not affect iOS Voalte Me^® Application.

Note: This only occurs on iOS Voalte One 3.7.14 clients that are connected to a pre 3.7.10 server. If you are connected to a 3.7.10+ server running iOS Voalte One 3.7.14, the issue does not occur.

Workaround.

The current workaround for this issue is to have a Voalte representative disable the battery_pack_req field within Voalte^® Mobile Admin. Please reply to confirm you would like to have this setting disabled. In order for the change to take effect on the clients, users will need to force quit and relaunch the Voalte One application. Users do not need to log out and back in. However, if a user forgets to force quit the application, the setting will be applied upon the next logout/login.

Note: There is no end-user impact to make this change or downtime required.

Note: With this setting disabled, you cannot see the battery level of Voalte One users within the Voalte Messenger^TM Client.

Next steps.

The Voalte Engineering team is currently investigating this issue and is working on providing a permanent fix by next week.

Please contact your Voalte CSM/account rep or Voalte Support team at [email protected] for any questions or to request release notes.