Skip to content

@zzebrum zzebrum released this Aug 14, 2019

Disclaimer Adguard for Mac is not an open source project. We use GitHub as an open bug tracker for users to see what developers are working on.

This update will not blow you away, unless you are really, really into bugfixes and under the hood improvements. But those we have aplenty, especially when it comes to CoreLibs filtering engine. As a result, the new Mac version works faster and blocks ads better than its predecessor, but lacks bit in the wow-factor: the only new feature is, admittedly, rather tame.

[Added] Automatic filter subscriptions detection #279

Most filters have “subscribe” buttons on their homepages or in other places. From now on, AdGuard will be able to intercept click on such links and offer you to add these filters to the app. It’s not much perhaps, but it’s a nice thing to have and it certainly won’t hurt anyone 🙂

[Improved] CoreLibs has been updated to v1.4

There are over 50 bugfixes and improvements in this new CoreLibs version. Some notable examples:

  • AdGuard doesn't unnecessarily reset cookies anymore. Previously it could lead to such problems as spontaneous sign outs, which was especially irritating for websites like Twitch or YouTube.
  • Protection restart doesn't require closing connections anymore. Before v2.1, protection restarts could sometimes cause the interruption of your ongoing downloads, issues with online games etc.
  • Several issues with upload speed have been resolved.

Overall, AdGuard for Mac is now faster and much more stable than it used to be.

  • [Fixed] No internet connection with custom DNS in DNSCrypt #528
  • [Fixed] adguard-tcpkill process constantly crashes on macOS Catalina #530
  • [Fixed] “Reset Settings” option hangs the app #543
  • [Fixed] iTunes Store access issue #552
  • [Fixed] Compatibility issues
  • [Improved] Algorithm for automatic language filters activation #513
  • [Improved] Automatic detection of certificate issues in Firefox #472
  • [Improved] New settings reconfiguration method does not require closing active connections #542
  • [Improved] The new icon implemented across the app #561
  • [Improved] The protocol to add filter subscriptions #559
  • [Improved] Localizations have been updated
Assets 3
Pre-release
Pre-release

@zzebrum zzebrum released this Aug 8, 2019 · 1 commit to master since this release

Disclaimer Adguard for Mac is not an open source project. We use GitHub as an open bug tracker for users to see what developers are working on.

We’re approaching the next release, and the betas are becoming less saturated with changes but more focused. In this one, the main attention is drawn to CoreLibs. After some tweaks made to the filtering engine, now connections will not be reset as often: only in rare cases when filter updates or changes in configuration require it. Few other improvements:

  • [Fixed] iTunes Store access issue #552
  • [Fixed] Chromium 78 is not filtered by AdGuard #574
  • [Improved] The new icon implemented across the app #561
  • [Improved] The protocol to add filter subscriptions #559
Assets 3
Pre-release
Pre-release

@zzebrum zzebrum released this Jul 18, 2019 · 3 commits to master since this release

Disclaimer Adguard for Mac is not an open source project. We use GitHub as an open bug tracker for users to see what developers are working on.

In the first beta version after v2.0 release, we mostly concentrate our efforts on fixing various compatibility issues and other bugs. We also added automatic filters detection.

[Changed] Upgrade to CoreLibs v1.4

Over 50 bugfixes and improvements in this new CoreLibs version. Overall, AdGuard for Mac is now faster and much more stable than it was.

[Added] Automatic filter subscriptions detection #279

Most filters have “subscribe” buttons on their homepages or in other places. From now on, AdGuard will be able to intercept click on such links and offer you to add these filters to the app. It’s not much perhaps, but it’s a nice thing to have and it certainly won’t hurt anyone 🙂

  • [Fixed] No internet connection with custom DNS in DNSCrypt #528
  • [Fixed] adguard-tcpkill process constantly crashes on macOS Catalina #530
  • [Fixed] “Reset Settings” option hangs the app #543
  • [Fixed] Compatibility issues
  • [Improved] Algorithm for automatic language filters activation #513
  • [Improved] Automatic detection of certificate issues in Firefox #472
  • [Improved] New settings reconfiguration method does not require closing active connections #542
  • [Improved] Localizations have been updated
Assets 3

@zzebrum zzebrum released this Jun 13, 2019 · 14 commits to master since this release

WARNING: for the app to work properly you might need to restart the system.

NOTE: if you currently have AdGuard installed to any folder except for /Applications, the old version will launch after the update anyway. In this case, you need to close and uninstall the old AdGuard. Users who have AdGuard installed to /Applications already can update as usual.

Its a common situation when a release is followed by a hotfix, taking care of all unnoticed bugs. The bigger the release, the more bugfixes there usually are in the hotfix. All things considered, v2.0 can be considered a success, seeing how few serious issues we had to resolve in this update.

Ad blocking

  • [Fixed] Status of the "Trusted" checkbox isn't saved for custom filters #519

Network

  • [Fixed] Pages don't load when two system user accounts are in use #509

UI

  • [Fixed] Incorrect statistics after system restart #517
  • [Fixed] AdGuard doesn't detect some system locales #502
  • [Fixed] Userscripts are not translated into Traditional Chinese #503

Other

  • [Fixed] AdGuard installer does not work in MacOS Catalina beta #526
  • [Improved] CoreLibs engine has been updated #522
Assets 3
Pre-release
Pre-release

@aspasskaya aspasskaya released this Jun 11, 2019 · 15 commits to master since this release

WARNING: for the app to work properly you might need to restart the system.

NOTE: if you currently have AdGuard installed to any folder except for /Applications, the old version will launch after the update anyway. In this case, you need to close and uninstall the old AdGuard. Users who have AdGuard installed to /Applications already can update as usual.

A small beta to fix some of the more unpleasant bugs and improve filtering quality.

Ad blocking

  • [Fixed] Status of the "Trusted" checkbox isn't saved for custom filters #519

Network

  • [Fixed] Pages don't load when two system user accounts are in use #509

UI

  • [Fixed] Incorrect statistics after system restart #517
  • [Fixed] AdGuard doesn't detect some system locales #502
  • [Fixed] Userscripts are not translated into Traditional Chinese #503

Other

  • [Improved] CoreLibs engine has been updated #522
Assets 3

@aspasskaya aspasskaya released this May 30, 2019 · 16 commits to master since this release

Disclaimer Adguard for Mac is not an open source project. We use GitHub as an open bug tracker for users to see what developers are working on.

This is one of the biggest updates in the history of AdGuard for Mac. It introduces the long-due Stealth Mode, an updated UI (including the improved Assistant), integration with CoreLibs — the new enhanced filtering engine — and much more. Give it a try and you'll immediately notice the difference.

[Added] CoreLibs integration #232

This is the first AdGuard for Mac that introduces CoreLibs — the new filtering engine that lies at the core of the filtering process. It is not random that we put this before such huge news as Stealth Mode or new design. The effects of this change will be both big and long lasting.
CoreLibs significantly enhances both ad blocking quality and performance, in comparison to the latest stable version. And since CoreLibs is a cross-platform filtering engine, in addition to these obvious improvements it allows to implement more new features that previously were only available in other AdGuard products.
Worth mentioning that AdGuard for Mac becomes the second AdGuard product to receive the «CoreLibs treatment» after Adguard for Android.

[Added] Stealth Mode #12

Stealth Mode is a special module which sole purpose is to protect your online privacy. It went a long way from an obscure, Windows-exclusive feature, to the centerpiece of almost any AdGuard product in the very near future. This is a logical flow of things as the value of privacy has been rising to the sky for some time now, and the need to protect it becomes apparent.
If you had a chance to use AdGuard for Windows, you will find inside all familiar options. We’ll not clog up the changelog by describing every single one, they are all explained in the tooltips next to them.

[Improved] New UI #346

Finally, we get to the new UI. You may be baffled why it was left until the very end of the changelog, the explanation is very simple: the changes are modest. Both the main screen and the settings menu look different enough, but you won’t have to re-familiarize yourself with the app. Think new, prettier icons, honed styles and so on.
One thing that stands out is the new Assistant, it is miles ahead of the old version in terms of convenience, and allows you to access the web reporter for any filter-related issues on the web pages.
Oh, and another treat, exclusively for Mojave users who prefer dark themes. AdGuard now supports the dark theme, so if you switch to it in your Mac settings, AdGuard will no longer be a black sheep among your applications, pun not intended.

New users will also be greeted with redesigned onboarding screens. They are made more informative and help make first steps and adjust AdGuard according to your needs.

[Added] AdGuard Extra extension #492

In some complicated cases the usual approach with filtering rules just doesn’t work. In particular, in some cases of ad blocker circumvention/ad reinjection. So we came up with an alternative solution — a userscript. For those unfamiliar, userscripts are basically mini programs that modify web pages and augment browsing.

AdGuard Extra does it in a way that makes it harder for websites to employ the circumvention/reinjection techniques. AdGuard for Mac is the first AdGuard product to get this addition, we are thrilled to see it in action and read your feedback on it.

[Changed] Developer ID has been changed #460

Application’s Developer ID has been changed to Adguard Software Limited. This shouldn’t concern you much, but if you are curious why it’s because of the problem we ran into on Mojave. Basically, all new and updated apps on Mojave now have to be notarized. In the future, this will be mandatory for all applications. And part of the notarization process for us was changing the Developer ID.

NOTE: if you currently have AdGuard installed to any folder except for /Applications, the old version will launch after the update anyway. In this case, you need to close and uninstall the old AdGuard. Users who have AdGuard installed to /Applications already can update as usual.

Ad blocking

  • [Added] An indicator for modified cookies in the Filtering Log #386
  • [Changed] Filtering rules limitations #393
  • [Changed] Handling of multiple $replace rules #338
  • [Fixed] "Proceed anyway" button does not work #369
  • [Fixed] "Rule" is missing from the Filtering Log item details #404
  • [Fixed] AdGuard crashes after editing the User filter #436
  • [Fixed] Compatibility problems
  • [Fixed] Microsoft Edge browser is not filtered #487
  • [Fixed] Receiving "Filter activated automatically" notification for already activated filters #366
  • [Fixed] Records with empty URL in the filtering log #342
  • [Fixed] Some filters become enabled after every app update #437
  • [Fixed] Vivaldi browser is not filtered #475
  • [Fixed] Whitelist shows comments from User Filter after update #452

Network

  • [Added] Stealth Mode parameters to the web reporter link #388
  • [Fixed] Stealth Mode actions aren't showed in the Filtering Log #355

UI

  • [Added] A description in the Filtering Log for some types of Stealth Mode events #421
  • [Added] Indicate that filter is trusted or recommended #445
  • [Added] New AdGuard for Mac icon #450
  • [Fixed] Blocked 'WebRTC, location API, push API' doesn't show in modified request in filtering log #449
  • [Fixed] Two notifications appear after using the manual ad blocking tool #419

Other

  • [Added] «Application» column to the Filtering Log #341
  • [Added] «Export logs and system info...» option #395
  • [Changed] Exception rules created via Assistant now have $document,~extension modifiers #333
  • [Changed] Localizations has been updated
  • [Changed] The list of apps filtered by default has been updated
  • [Changed] Users with an active subscription will not be notified anymore that their license key is soon to expire #329
  • [Fixed] adguard-tcpkilldoes not work with the new Chrome version #427
  • [Fixed] AdGuard doesn’t start automatically on the system startup #480
  • [Fixed] Changes to the filtered apps and extensions are not applied until the protection is restarted manually #354
  • [Fixed] Description for “Strip tracking parameters” option #398
  • [Fixed] Filtering Log issues #430
  • [Fixed] Forwarder applied properly to all links in the app #389
  • [Fixed] High CPU usage due to a sync XHR request made by the Assistant #315
  • [Fixed] Kext status check does not work properly on macOS 10.14 #337
  • [Fixed] Statistics is not counted properly #334
  • [Fixed] The app hanged on exit #462
  • [Fixed] The list of filtered apps gets reset after an update #473
  • [Fixed] Website report is now sent properly via the Assistant #361
  • [Improved] Enhanced app accessibility #406
  • [Improved] New onboarding screens #385, #407
  • [Improved] Refactoring «Launch at Login» #415
Assets 3
Pre-release
Pre-release

@zzebrum zzebrum released this May 28, 2019 · 18 commits to master since this release

Disclaimer Adguard for Mac is not an open source project. We use GitHub as an open bug tracker for users to see what developers are working on.

CoreLibs is the centerpiece of the upcoming AdGuard 2.0 for Mac update, and we've just discovered some minor problems with it. Nonetheless, we consider them important enough to release one more beta to fix these problems before unleashing the new stable version into the world. We've also made a few localization updates.

Assets 3
Pre-release
Pre-release

@zzebrum zzebrum released this May 24, 2019 · 19 commits to master since this release

Disclaimer Adguard for Mac is not an open source project. We use GitHub as an open bug tracker for users to see what developers are working on.

Welcome the first AdGuard 2.0 for Mac release candidate! The changes are minimal compared to the recent beta, but there’s one that’s worth your attention: the introduction of AdGuard Extra userscript. By the way, we plan to transition this version into a stable one if everything goes well.

[Added] AdGuard Extra extension #492

In some complicated cases, the usual approach with filtering rules just doesn’t work. In particular, in some cases of ad blocker circumvention/ad reinjection. So we came up with an alternative solution — a userscript. For those unfamiliar, userscripts are basically mini programs that modify web pages and augment browsing.

AdGuard Extra does it in a way that makes it harder for websites to employ the circumvention/reinjection techniques. AdGuard for Mac is the first AdGuard product to get this addition, we are thrilled to see it in action and read your feedback on it.

  • [Fixed] Description for “Strip tracking parameters” option #398
  • [Fixed] The list of filtered apps gets reset after an update #473
  • [Fixed] Vivaldi browser is not filtered #475
  • [Fixed] Microsoft Edge browser is not filtered #487
  • [Fixed] AdGuard doesn’t start automatically on the system startup #480
Assets 3
Pre-release
Pre-release

@aspasskaya aspasskaya released this Apr 30, 2019 · 20 commits to master since this release

Disclaimer Adguard for Mac is not an open source project. We use GitHub as an open bug tracker for users to see what developers are working on.

When it comes to AdGuard for Mac, we prefer a steady, even methodical approach. Eliminate all bugs, make sure nothing is left unnoticed. This is one of those betas where we clean everything up: fix bugs, improve some of the features and so on. We’ll let it run for a while, monitor it for anything that resembles a missed bug, and if is all is good, we’ll stick a “2.0 stable” label on it.

[Changed] Developer ID has been changed #460

Application’s Developer ID has been changed to Adguard Software Limited. This shouldn’t concern you much, but if you are curious why it’s because of the problem we ran into on Mojave. Basically, all new and updated apps on Mojave now have to be notarized. In the future, this will be mandatory for all applications. And part of the notarization process for us was changing the Developer ID.

NOTE: if you currently have AdGuard installed to any folder except for /Applications, the old version will launch after the update anyway. In this case, you need to close and uninstall the old AdGuard. Users who have AdGuard installed to /Applications already can update as usual.

Ad blocking

  • [Added] An indicator for modified cookies in the Filtering Log #386
  • [Fixed] "Proceed anyway" button does not work #369
  • [Fixed] "Rule" is missing from the Filtering Log item details #404
  • [Fixed] AdGuard crashes after editing the User filter #436
  • [Fixed] Receiving "Filter activated automatically" notification for already activated filters #366
  • [Fixed] Records with empty URL in the filtering log #342
  • [Fixed] Some filters become enabled after every app update #437
  • [Fixed] Whitelist shows comments from User Filter after update #452
  • [Fixed] Compatibility problems

Network

  • [Added] Stealth Mode parameters to the web reporter link #388
  • [Fixed] Stealth Mode actions aren't showed in the Filtering Log #355

UI

  • [Added] A description in the Filtering Log for some types of Stealth Mode events #421
  • [Added] Trusted filter notification #445
  • [Added] New AdGuard for Mac icon #450
  • [Fixed] Blocked 'WebRTC, location API, push API' events aren't shown in modified requests in Filtering log #449
  • [Fixed] Two notifications appear after using the manual ad blocking tool #419

Other

  • [Changed] Users with an active subscription will not be notified anymore that their license key is soon to expire #329
  • [Changed] Localizations has been updated
  • [Fixed] adguard-tcpkill does not work with the new Chrome version #427
  • [Fixed] Changes to the filtered apps and extensions are not applied until the protection is restarted manually #354
  • [Fixed] Forwarder applied properly to all links in the app #389
  • [Fixed] The app hanged on exit #462
  • [Fixed] Filtering Log issues #430
  • [Improved] Enhanced app accessibility #406
Assets 3
Pre-release
Pre-release

@zzebrum zzebrum released this Mar 12, 2019 · 21 commits to master since this release

Disclaimer Adguard for Mac is not an open source project. We use GitHub as an open bug tracker for users to see what developers are working on.

AdGuard for Mac traditionally doesn’t receive frequent updates, but when it does, it is usually something big. This beta is not an exception, we present to you not one, not two, but three big changes, each one of them would normally be enough to justify a beta update on its own. These changes are CoreLibs integration, new UI and the introduction of Stealth Mode. Let’s jump inside and look at them more closely.

[Added] CoreLibs integration #232

This is the first AdGuard for Mac beta that introduces CoreLibs — the new filtering engine that lies at the core of the filtering process. It is not random that we put this before such huge news as Stealth Mode or new design. The effects of this change will be both big and long lasting.

CoreLibs significantly enhances both ad blocking quality and performance, in comparison to the latest stable version. And since CoreLibs is a cross-platform filtering engine, in addition to these obvious improvements it allows to implement more new features that previously were only available in other AdGuard products.

Worth mentioning that AdGuard for Mac becomes the second AdGuard product to receive the «CoreLibs treatment» after Adguard for Android.

[Added] Stealth Mode #12

Stealth Mode is a special module which sole purpose is to protect your online privacy. It went a long way from an obscure, Windows-exclusive feature, to the centerpiece of almost any AdGuard product in the very near future. This is a logical flow of things as the value of privacy has been rising to the sky for some time now, and the need to protect it becomes apparent.

If you had a chance to use AdGuard for Windows, you will find inside all familiar options. We’ll not clog up the changelog by describing every single one, they are all explained in the tooltips next to them.

image

[Improved] New UI #346

Finally, we get to the new UI. You may be baffled why it was left until the very end of the changelog, the explanation is very simple: the changes are modest. Both the main screen and the settings menu look different enough, but you won’t have to re-familiarize yourself with the app. Think new, prettier icons, honed styles and so on.

One thing that stands out is the new Assistant, it is miles ahead of the old version in terms of convenience, and allows you to access the web reporter for any filter-related issues on the web pages.

Oh, and another treat, exclusively for Mojave users who prefer dark themes. AdGuard now supports the dark theme, so if you switch to it in your Mac settings, AdGuard will no longer be a black sheep among your applications, pun not intended.

New users will also be greeted with redesigned onboarding screens. They are made more informative and help make first steps and adjust AdGuard according to your needs.

Ad blocking

[Changed] Filtering rules limitations #393
[Changed] Handling of multiple $replace rules #338

Other

[Added] «Application» column to the Filtering Log #341
[Added] «Export logs and system info...» option #395
[Changed] Users with an active subscription will not be notified anymore that their license key is soon to expire #329
[Changed] Exception rules created via Assistant now have $document,~extension modifiers #333
[Fixed] High CPU usage due to a sync XHR request made by the Assistant #315
[Fixed] Statistics is not counted properly #334
[Fixed] Kext status check does not work properly on macOS 10.14 #337
[Fixed] Website report is now sent properly via the Assistant #361
[Improved] Refactoring «Launch at Login» #415
[Improved] New onboarding screens #385, #407

Assets 3
You can’t perform that action at this time.