Spok Mobile Release Notes 4.4.x

Corrected Issues

• Saving an integration could reduce contact search performance in some cases.
• When using Spok Console, messages sent from a Spok Mobile client to any user in an On-call group would be delivered only to the first user that was added to the On-call group, instead of to the intended recipient.
• Fixed a memory leak associated with AmcomServiceAppPool that consumed to much RAM over time.
• Improved the Devices page's load time.
• After successfully wiping the messages on a Zebra device, a "Message wipe failed" alert incorrectly appeared and could not be closed.
• Fixed an issue in which Spok Mobile Server sometimes did not pass Queued and Accepted statuses to the Contact Center when using Smart Suite with MXPP.
• When the system experienced very high message volume, message delivery performance degraded over time. Restarting the Spok Mobile Service temporarily improved performance.
• Previous security hotfixes are now integrated into this release.
• When using Smart Suite, available on-call groups would incorrectly display as unavailable in the Spok Mobile app, even though pages could be still be sent to them successfully.
• When searching for a user in the Spok Mobile app, Smart Suite returned many results, even though the app was designed to only display 25. The extra records returned from Smart Suite negatively impacted search performance.

Corrected Issues

• Fixed an issue where there was a long response time to search a contact.

• Delivered status on iOS is now working as intended for customers that upgrade from Spok Mobile Server 4.4.2. This means the timestamps of when "Delivered" is shown are once again highly accurate for customers upgrading from 4.4.2.

Corrected Issues

• Fixed an issue that occasionally caused messages to appear out of order in recipients' message threads.

• Fixed an issue that caused the app to crash when a user tapped on a notification from the Spok Mobile with a Pager environment. This issue is resolved for users if they upgrade to a 4.4.3 or newer Spok Mobile for iOS app.

Corrected Issues

• DE26685:Fixed an issue causing delays in contact search. The fix improves search times when users perform a search.

  For the above fix to work properly with Smart Suite versions 5.5 or 5.7, patch DE26020_DE26077_with_SpokMobile must be applied. This patch can be found in the standard patch location for the Smart Suite product. Smart Suite 7.0 and higher already contain the patch; no action is necessary for these versions.

• Fixed an issue causing iOS devices to not properly update the status of a message. Note that this fix does not work for devices running iOS 9, as this version of iOS is missing the notification framework that allows the Delivered status to be sent back to the sender after a notification is received.

• Fixed an issue where the Assets Directory could not be saved when Spok Mobile Server and Care Connect Server have joined the network domain and the application pool is running with a local account.

• Fixed an issue causing an error message to appear during installation (for Alerting and Mobile). The fix involved ensuring generated scripts now include the necessary default values in place to correctly apply them.

Corrected Issues

• Fixed an issue that caused removed/unregistered sites to continue to appear in the site list in the app's drawer.
• Fixed an issue that while receiving a message with the app open, a short sound plays when Spok Mobile is set to Vibrate Only and the device is set to vibrate.
• Fixed an issue with received message attachments that was encountered on Samsung devices running Android 7.0.
• Fixed an issue where the app would crash when a user tapped a notification for an incoming alert-style message on a locked screen when the user's device had fingerprint unlocking capabilities enabled.
• Fixed an issue that sent users to their device home screen after tapping a notification on a locked screen and entering a Spok Mobile access code. This was encountered on Samsung devices running Android 7.0 only.
• Fixed an issue that caused alert tones to be interrupted and not repeat if the device is locked and the user has a Spok Mobile access code set.

Known Issues

• Android users who want to update their profile image may be temporarily unable to tap Edit in the Profile page. This occurs when the user's profile is synchronizing with the Spok Mobile server at the same time they open the Profile page. After synchronization is complete, Edit can be tapped.

New Features and Enhancements

Corrected Issues

• Fixed a chat-style messaging issue for iOS 10 users:
  • When recipients exited the app, the badge count would be correct at first, but as soon as another message was received, the count would include any messages that were received while the recipient was viewing a thread.
  • This issue also caused messages received while both sender and recipient were viewing a message thread to show the Delivered status on the sender's device, rather than Read.
  • With the fix, the correct status is displayed:
    • The sender sees the Read status
    • The recipient sees the expected badge count
• Fixed an issue that caused alerts to continue beeping once the app was opened. With the fix, the app stops beeping once the user opens the app.
• Fixed an issue that caused the message to cover up the To field when a long message was composed. With the fix, writing or forwarding long messages no longer overlaps the To field.
• Fixed an infrequently encountered issue that caused the Access Code screen to be bypassed if the app was closed and re-opened. With the fix, the Access Code screen appears every time it should.

Known Issues

iOS 11 currently has a defect that causes apostrophes to appear as question marks in Spok Mobile messages composed on devices running iOS 11. Until Apple provides a fix for this, users can disable the Smart Punctuation feature on their personal device: Settings > General > Keyboards > Smart Punctuation toggle OFF.

• With iOS 11, phone number punctuation does not appear in the prompt that asks users to confirm whether they want to dial the number. For example, (555) 123-4567 appears as 5551234567. This causes no issues with dialing the number.
• The Spok Mobile for iOS app crashes when a user taps on a notification from the Spok Mobile with a Pager environment.
• Notifications from the Spok Mobile with a Pager environment sometimes cause inaccurate app badge counts in the Spok Mobile for iOS app.

New Features and Enhancements

Known Issues

New Features and Enhancements

Corrected Issues

• Updated message status behavior for to better align with user expectations. In 4.4.0, there were certain scenarios in which the Failed message status displayed on a sender’s device when the message had not encountered a system error.
• In a message to multiple recipients, the correct profile picture appears next to the sender.
• High priority alert messages appear over lower priority alert messages when messages are received simultaneously.
• Spok Mobile no longer requires some users who installed or upgraded to version 4.4 to access their device using fingerprint authentication. 

Known Issues

• With Android, users who want to update their profile image may be temporarily unable to tap Edit in the Profile page. This occurs when the user's profile is synchronizing with the Spok Mobile server at the same time they open the Profile page. After synchronization is complete, Edit can be tapped.
• Users with Samsung devices running Android 7.0 may be unable to download received message attachments. If users encounter this problem, they can remediate it by enabling the "Auto Load Attachments" setting in the Spok Mobile app.

New Features and Enhancements

Corrected Issues

• Updated message status behavior for to better align with user expectations. In 4.4.0, there were certain scenarios in which the Failed message status displayed on a sender’s device when the message had not encountered a system error.

• Fixed an issue that caused text to "bounce" while users were composing messages.
• In a message to multiple recipients, the correct profile picture appears next to the sender.
• When a new user logs into Spok Mobile on an iOS device, any messages associated with a different user previously logged into Spok Mobile on the same device do not appear.

New Features and Enhancements 

Many enhancements are available to users simply by having the 4.4 app. Users get even more when their 4.4 app is supported by the 4.4 server environment.

Spok Mobile 4.4 with Care Connect Suite 1.8 provides users with:

• Single-step registration (new users will also use single-step registration during enrollment)
• Enhanced message status
• Support for Medicall updates (status and profile)
• Improvements to secure messaging and search performance

Corrected Issues

• Fixed an issue where settings did not clear when a registration was removed. Now that the issue is fixed, all registration data and device settings are removed when a registration is removed.

• Fixed an issue that caused messages to be improperly logged.

• Fixed an issue where registration emails were not received after SMTP configuration. 

• Fixed an issue that caused an error message to appear when attempting to delete tenants. Before this issue was fixed, users could not delete tenants, even if the tenant had no registrations associated with them. Now that the issue is fixed, tenants can be deleted successfully. 

• Fixed an issue that caused the Registration Information method to return to the "Unable to retrieve registration information" response when registration exists. Now that the issue is fixed, Registration Information is returned properly.

• Fixed an issue that where the "acknowledged" message status didn't reach the contact center after the message changed from "ignored" to "acknowledged." Now that the issue is fixed, the proper status will be sent back to the contact center.

• Fixed an issue where an error message appeared after clicking Save in the settings of the Hosted configuration page. 

• Fixed an issue that caused problems with the threadpool size when running the Spok Mobile server on a single core system. Now that the issue is fixed, the correct threadpool size runs on single core systems.

• Fixed an issue where Spok Mobile Adapter service was disabled following upgrade. Now during install/upgrade, adapter windows service is configured with "Startup Type" set to "Auto." 

• Fixed an issue where the ExtTenantName updated with a site name instead of the tenant name, causing the license file's upload to crash. Before the defect fix, if the site name is longer than 50 characters, the license file's upload would fail because ExtTenantName only allows 50 characters. Now that the issue is fixed, any records that exist that are longer than 50 characters are truncated to fit.

• Fixed an issue that caused the server to ignore time zone and language changes made in Hosted when user re-uploads licenses on the server. Now that the issue is fixed, time zone and language changes will show in the Spok Mobile server. 

• Fixed an issue that caused registrations to add successfully when the LocalDeviceID and UserID are different. Now that the issue is fixed, the registration will not be added when the LocalDeviceID and UserID are different.

• Fixed an issue that caused a redirect loop when the web application encounters an error during installation. Now that the issue is fixed, the screen will display an error message when the web application encounters an error during installations. 

• Fixed an issue where a registration can be added using a UserID that does not have a corresponding user in the host system. Now that the issue is fixed, the app does not allow registrations using UserIDs without a corresponding user in the host system.

• Fixed an issue that caused Contact Search to run slowly when many users are members in a group. Now that the issue is fixed, search results display in a timely manner.

• Fixed an issue where orphaned records in some tables are left after removing registrations related to Medicall. Now that the issue is fixed, the records in the tables are removed.

• Fixed an issue where the welcome email's buttons for downloading the Spok Mobile app for Spheres were missing their URL's. The buttons now direct users to the iOS App Store and Google Play Store.

• Fixed an issue that caused an invalid error message to appear in Spheres when messages were sent between devices. Before the issue was fixed, the Core Service would not process the status updates of the messages and would show an error message even when messaging was working. Now that the issue is fixed, the error message will not appear.

Known Issues

• IIS must be restarted following installations of Spok Mobile Server 4.4/1.7.
• For upgrades to the 4.4/1.7 server, the Test Connection function in the Care Connect Suite Installer's Database Configuration dialog does not test for the mirror server.
• At the end of new installations of Spok Mobile Services, a browser opens with two tabs of the Configuration Service URL page. This is a defect that will be fixed in a future release. For now, the Platform Server Name or IP field should be updated in both tabs. The duplicate happens because the Care Connect Suite Installer opens the Configuration Service URL page and the Spok Mobile installation automatically opens the Spok Enterprise Administration page. The Spok Enterprise Administration page first opens to the Configuration Service URL page. 
• In Smart Suite-integrated environments, un-secure contacts with DPE profiles (from Device Preferences) may be displayed as secure in contact search results. 

New Features and Enhancements

Corrected Issues

• Fixed an issue that caused Spok Mobile to close when the user tapped the device's back button while the Spok Mobile drawer was open. Now that the issue is fixed, when the back button is pressed, the drawer closes. 
• Fixed an issue that caused the app to crash when the user received messages. 
• Fixed an issue that caused the "Select from Box" button to go missing from the profile screen or overlap with the "Remove" button. Now that the defect is fixed, both buttons display properly. 
• Fixed an issue where users could not register with an access code that had been enabled but had not yet been added to the user. Before this issue was fixed, the page would keep spinning after the user entered the access code until the user closed the app. When the app was re-opened, the registration screen would appear again. Now that the issue is fixed, users can register with an enabled access code. 
• Fixed an issue that caused the app to crash when the user visits the Profile page multiple times. Before the defect fix, the memory in Activities was leaking, causing the "Out of Memory Message" message to appear. Now that the issue is fixed, the user may visit the Profile screen without error. 
• Fixed an issue that caused clients to need to re-authenticate their registration. This issue is not a problem with upgrades from 3.5 to 4.2. 
• Fixed an issue that caused the placeholder for the profile picture to display as square instead of round. This issue was caused by the wrong image being set as the default for user contacts. Now that the issue is fixed, the profile picture placeholder is round. 
• Fixed an issue with the app time not reflecting changes from the 12-hour to 24-hour format. The reason for this issue was the app did not take the time format setting from the device and was showing the 12-hour format despite changes made through the device. Now that the issue is fixed, the app takes time format settings from the device and the appropriate format displays. 
• Fixed an issue that caused the "Select file type" dialog (used to attach a file to a message) to remain on the screen over the Messages screen. 
• Fixed an issue that caused the app to prompt the user to enter the access code when returning to the app from the "Share to Box" option in chat view. Now that the issue is fixed, the app does not prompt the user to enter the access code. 
• Fixed an issue where the profile pictures inside the Spok Welcome Messages to be empty. This was because creating the contact for the Welcome Messages also created a duplicate contact without a profile picture. Now that the issue is fixed, the welcome message does not use the duplicate contact so the profile picture displays in the Welcome Message avatar. 
• Fixed an issue that caused message status updates to not work in certain conditions. Before the defect fix, message status updates did not show when the Profile ID in WebXchange contains upper case letters. The reason for this issue was that all the values from the message status update command were lower case. Now that the issue is fixed, the command is not case sensitive and shows all status updates. 
• Fixed an issue that caused the app to crash after the device fell asleep in Contact Search. The reason for this issue was that the OnFocusListener was triggered and caused the app to crash. Now that the issue is fixed, the app will stay stable after falling asleep in Contact Search. 
• Fixed an issue where notifications on the lock screen were not dismissed after clicking Accept/Decline. The tone also continued to sound until the App was opened. A new service was created to handle the acknowledge/ignore/reply actions from the notifications and close the notification. The projections and settings update process, call back number action, android phone permission, and Samsung notification actions were also fixed. Tapping Accept or Decline now dismisses the notification and stops the beeping. 
• Fixed a problem where the Fingerprint capability was still enabled on a Samsung device after it had been disabled. The App now remembers the user's setting and the Fingerprint capability performs according to the settings selected by the user. 

Known Issues

• When a Spok Mobile user changes their name, if they send a message to someone that has already received messages from them using their original name, the new message banner shows their new name, but the message appears in the chat area with their original name.
• Notifications remain on the screen after being acknowledged on Xperia Tablet. If a user deletes the alert in the background, and then taps on the alert notification during the window of time while the overlay view is still displaying the notification, the app gets confused because they are attempting to take action on an alert that no longer exists. This causes the app to crash. Xperia tablets are designed to display notifications in an overlay view which can persist for several seconds, even after a notification has been acknowledged. This is the way these tablets are designed to work. Users should acknowledge the Spok Mobile alert notification and then wait for the notification to automatically go away.

• In certain scenarios, the Failed message status will display on a sender's device when the message has not encountered a system error. In such a scenario, the message may have been delivered or still be on its way to the recipient's device.

• There is an issue seen in both Spok Mobile for iOS and Spok Mobile for Android where unavailable message recipients appear as available to the other user in a message thread. If User A is viewing the conversation and User B sets their device to an unavailable status, User A continues to see User B as available, and can compose and send messages to User B that show a Sent status. User A will see the "Contact not available" warning only after they leave the conversation and return to it.

New Features and Enhancements

Corrected Issues

• Fixed an issue where the Enterprise site was not visible when registering with a multi-site registration. Now that the issue is fixed, Enterprise is available when every tenant of a multi-tenant collection is used.

• Fixed an issue that caused an error message to appear if the user included an ampersand in the search field. With the fix, a custom URL encoding method now allows ampersands to appear in search query.

• Fixed an issue where if the search query contained a plus sign, the plus sign was ignored and not sent to the DataRepositoryService. Now that this problem is fixed, the search query returns results for the plus sign.

• Fixed an issue that caused function type contacts of a person type to appear as (null) (null) on the "Recent" screen. This issue happened because checks for server data availability were incomplete. Now that the issue is fixed, the screen shows the default string "Unknown" if data is unavailable.

• Fixed a thumbnail attachment issue. Now that the issue is fixed, the thumbnail is created after the asset is uploaded. 

• Fixed an issue where the iOS Date header did not include the day of the week. Now that the issue is fixed, both iOS and Android devices use day of the week in the Date header.

• Fixed an issue that caused part of the date to contain information from the Japanese calendar after changing the Japanese calendar to the Gregorian calendar. Now that the issue is fixed, the date automatically updates and the message times update when the app receives significant time changes.

• Fixed an issue with the app bypassing the Access Code and Touch ID security. Now that the issue is fixed, the app does not bypass the Access Code and Touch ID security. 

• Fixed an issue where iOS Messages screen were listed in reverse order by date. 

Known Issues 

• A Spok Mobile user (User1) logs into a Spok Mobile device, sends and receives messages, and then logs out on the device; then, another user (User2) logs into Spok Mobile on the same device, the messages for User1 remain visible on the device. 

• Users cannot attach a file that contains spaces in the filename.

• When a Spok Mobile user changes their name, if they send a message to someone that has already received messages from them using their original name, the new message banner shows their new name, but the message appears in the chat area with their original name.

• For iOS versions prior to iOS 10: The Spok Mobile Tone Settings on a device specify Tone, Interval, and Number of Repeats. These settings dictate the sound that plays (Tone), how frequently the sound plays (Interval), and how many times the sound is repeated (Number of Repeats) when a notification for an incoming Spok Mobile message is received on the device. For iOS versions prior to iOS 10, when a tone is repeated for a message notification, a duplicate notification may appear for the same message. This duplicate notification does not appear for devices on iOS 10 or above.
  For more information about Spok Mobile tone settings, refer to Tone Settings.

• In certain scenarios, the Failed message status will display on a sender's device when the message has not encountered a system error. In such a scenario, the message may have been delivered or still be on its way to the recipient's device.

• There is an issue seen in both Spok Mobile for iOS and Spok Mobile for Android where unavailable message recipients appear as available to the other user in a message thread. If User A is viewing the conversation and User B sets their device to an unavailable status, User A continues to see User B as available, and can compose and send messages to User B that show a Sent status. User A will see the "Contact not available" warning only after they leave the conversation and return to it.

Android Support 

Spok Mobile 4.4 works with Android 5.0 (Lollipop) and higher.

iOS Support

Spok Mobile 4.4 works with iOS 8 and higher.

Cisco Devices Not Supported

Beginning with the 4.4 release, Spok Mobile no longer supports Cisco devices. Supported versions of Spok Mobile Server (4.2 and below) will continue to support Cisco devices.

Limited Support for BlackBerry Devices

Beginning with Spok Mobile 4.4, there is limited support for BlackBerry devices based on the device type and software version.