Release Notes

In the middle of February version 3.1 of our SafeMail product was released. The release includes automatically picking up when a student account is moved from one OU to another, enchancements to how can subscribe and unsubscribe to emailed reports, security enhancements and numerous bugfixes. 

Account Syncing

With the 3.1 release, we have made updates to support the latest version of the Office SDK. With this update, SafeMail will now perform a daily scan to pick up any accounts that have been moved from one OU to another in Office365. Google accounts were already syncing automatically so the sync for Google has not changed with this release. 

Report Subscriptions Enhanced

You are now able subscribe to be emailed reports from within the Customer Help Portal. Each of these emailed reports will also contain an unsubscribe link to make it easy to unsubscribe from the reports at any time. 

Security Enhancements

The 3.1 release now forces users accessing the SafeMail Customer portal to use HTTPS even if the user types in HTTP in the address bar. 

BugFixes

The 3.1 release also included various fixes for a number of bugs including issues with handling duplicate file names, notifications for Google Drive files that have been shared between multiple users and sending out emails for password reset requests. 

Version 4.26 of our Custom Mobile App was recently released. This release was primarily focused on updates to the Custom Mobile App to keep it inline with recent changes to the Google Play store. The release also included some minor accessiblity enhancements and application bugfixes.

Application Updates

The main focus of the 4.26 update was making required changes to our Custom Mobile App to keep up with changes being made with Google Play and the Android Ecosystem. 

Both Apple and Google are constantly evolving the way they interact with applications like the Custom Mobile App. As such, a good chunk of our time is often devoted to ensuring that the Custom App Application is kept up to date with these changes so that your application will continue to work with Apple and Google. Such was the case with this most recent update as we made changes so our product would continue working after changes that Google is rolling out.

Accessiblity Update

The 4.26 release makes changes to the channel icons so that the icons are more accessible. To take advantage of these changes, please contact our support team to request your application be rebuilt.

Important: If you have not yet created developer accounts, you will need to do so in order for your application to be rebuilt. For information on setting up your accounts, click here. The iOS and Google Play stores require each client to have a developer account in order to deploy new versions of your application into their stores. 

BugFixes

The 4.26 release included various fixes for a number of bugs. One of these fixes requires your application to be rebuilt. 

If you are experiencing the following issue, please contact our support team to request your application be rebuilt: 

• No sound for push notifications send to iOS devices 

Important: If you have not yet created developer accounts, you will need to do so in order for your application to be rebuilt. For information on setting up your accounts, click here. The iOS and Google Play stores require each client to have a developer account in order to deploy new versions of your application into their stores. 

At the end of September, 2019 version 4.25 of our Custom Mobile App was released. The release includes numerous bugfixes and a major change to the way statistics are gathered about application usage.

Major Change in Stats Tracking

Google is retiring their traditional Google Analytics for mobile applications and replacing it with Google Analytics for Firebase. Because of this, the traditional Google Analytics tracking will stop working after October 31st, 2019. In the 4.25 release, we added support for the new Firebase tracking method. 

If you already have gone through the process of creating developer accounts, our team will have already become work on rebuilding your application to enable support for the new analytics. 

Once your application has been updated to support Firebase, our support team will set your Firebase Anayltics to On.

Important: If you have not yet created developer accounts, you will need to do so if you want to be able to keep tracking usage data after October 31st, 2019. For information on setting up your accounts, click here. The iOS and Google Play stores require each client to have a developer account in order to deploy new versions of your application into their stores. 

BugFixes

The 4.25 release also included various fixes for a number of bugs. Some of these fixes require your application to be rebuilt. 

If you are experiencing one of the following issues, please contact our support team to request your application be rebuilt. 

• Unable to add event location to device calendar.
• Some images that use HTTPS URLs are not loading. 
• News story images that are being pulled from Presence are not loading. 

Important: If you have not yet created developer accounts, you will need to do so in order for your application to be rebuilt. For information on setting up your accounts, click here. The iOS and Google Play stores require each client to have a developer account in order to deploy new versions of your application into their stores.