We can't say we weren't expecting that. Last year Safari started the process of deprecating the traditional extensions, and we covered it in our Blog article. But you still could install the old style extensions and enable them manually.
The release of long awaited new AdGuard for Mac is getting nearer. And today we are one step closer as we start the alpha testing. There are a lot of changes awaiting, but we won't spoil all the fun by listing all updates of v2.0. We will mention only the most remarkable ones instead.
If you are on macOS Sierra or High Sierra, you must have received a notification about available Safari update (when Mojave rolls out, Safari 12 will be mandatory). No doubt that there's a lot of cool stuff inside, but we will save the praise for others and instead focus on one change that seriously concerns all AdGuard Browser Extension users: new Safari is breaking all directly downloaded
.safariextz extensions. And this is bad news.
Every time I write an article about an AdGuard for Mac update, I check how long ago the previous one was released — we used to have a nasty habit of taking our time with new Mac versions. This time, we are actually on schedule, partly because the release is not the biggest one you've seen. Let's get to it!
Today we want to try something different — combine two release announcements in one blog post. Main reason is, both new Mac and extension updates, while being important, are rather technical and do not provide a lot of topics to talk about without descending into using lots of developer lingo. Let's have a quick look at AdGuard for Mac v1.5.6 and AG Browser Extension v2.9.2.