Back

El Capitan’s ATS: what’s in it for OS X developers

by Daryl, DevMate Octopus on

This year during Apple Keynote there was one thing on the minds of OS X developers worldwide — the El Capitan release date. All because of the new Application Transport Security (ATS) requirements. Since the changes, there’s a good deal to be done and tested by the September 30th set release date.

El Capitan’s ATS

If you still haven’t heard about what ATS is, we’ll try to explain briefly. Now, if your application tries to connect to your server using the HTTP protocol, and your server doesn’t support the latest SSL, TLSv.1.2, the connection will be dropped. The request will be changed automatically from ‘http://’ to ‘https://’, so, if your server doesn’t support secure connections, nothing happens. Sure, you can find some tips on how to avoid such a problem, but it’s easier and more effective to apply the necessary changes to your Mac apps and adopt ATS. Apple is not trying to make developers’ lives harder, but to increase the security of customer’s data.

DevMateKit 1.3

As for us, we’ve been watching Keynote with no worries, because DevMate is ready for El Capitan. We’ve just published the new version of DevMateKit 1.3, which completely meets all the ATS requirements. All of our servers used for updating applications, gathering statistics, issue reports, feedback messages and license management support secure connections as well.

As a DevMate SDK user, all you need to do is update DevMateKit to the latest version. Simply replace the older version with the new one (see Knowledge Base if you need a reminder on how to do that).

In addition, DevMateKit v.1.3 contains some other improvements, the biggest one being the new version of Sparkle’s update core. Now it fully supports silent update installation and relaunch, so if your customers opt in for automatic updates, the app will update without the need for any additional user actions. Other significant changes are in the delta unarchiver, which is more stable now; and a double-check of the app’s code signature after installation, which makes updates more secure.

Also, when sending feedback or an issue report fails, the user’s message will be restored when the window reopens. Finally, we fixed trial behavior in case of application deactivation and improved app activation on virtual machines. Make sure your customers are happy with the new OS X and update your DevMate kit to 1.3 version.


Share this story