Skip to content

2.4
Compare
Choose a tag to compare
@adgkart adgkart released this 28 May 14:51
· 20 commits to master since this release
v2.4
3b37fd9
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

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.

Here comes AdGuard for Mac 2.4! Two betas served as cornerstones for this new version and we are glad to present it to you five months after the previous release.

The biggest thing that has changed here is the new Assistant. CoreLibs has traditionally been updated, too, which enhanced filtering quality. In other aspects, 2.4 is more of a bugfix release. We cleaned it from the recurrent problems of the previous versions, polished it up, so it works nice and smooth.

[Enhancement] The old Assistant has been replaced with a native Assistant browser extension #669, #670

AdGuard Browser Assistant is a new browser extension that simultaneously takes over the roles of the old Assistant and of the integration mode. We definitely support the functional approach, so we thought: why distribute workload between two old tools when one new extension can handle it better? Now let us tell you what AdGuard Browser Assistant is capable of.

What can you do with the help of the Assistant? Enable/disable filtering on the current webpage, manually block any element on the page, reporting the website if something goes wrong or view the filtering log. Now you have all these features without the limitations that appeared in the integration mode or in the old Assistant.

When you install AdGuard for Mac for the first time (or update it to the new version), the Safari Assistant will be installed automatically. If you use another browser, you can download the Assistant at this link. Or, you can install the Assistant for your default browser via app settings or during the onboarding process.

Changelog

  • [Fixed] Incorrect information about QUIC connections is displayed in the filtering log #532
  • [Fixed] Filtering in Microsoft Edge Beta doesn't turn off when removing the browser from filtered applications #663
  • [Fixed] AdGuard does not preserve the Whitelist #674
  • [Fixed] Fast user switching might corrupt certificate database #675
  • [Fixed] AdGuard doesn’t work in Brave Beta 1.7.64 #689
  • [Enhancement] Different build configurations for beta/release/nightly #615
  • [Enhancement] "What's new" screen now shows up after major app updates #671
  • [Other] New localizations: Croatian, Persian, Romanian, Thai #678

CoreLibs has been updated to 1.5.269

  • [Fixed] Incorrect extended CSS rule causes problems with JS rules’ work * #1147
  • [Fixed] Rules with :style() are converted incorrectly #1149
  • [Fixed] Issue with LINE extension #1280
  • [Fixed] Rules with restricted domains do not match requests without referer #1286
  • [Fixed] Stealth mode error #1290
  • [Fixed] Cosmetic rules can be used as CSS rules #1293
  • [Fixed] Basic rules with wilcard in top level domains are not working #1298
  • [Enhancement] “Proceed anyway” option doesn’t work correctly if a website is blocked by a rule with $all modifier #1267
  • [Enhancement] New rule selection algorithm for the cases when HTTPS filtering is disabled #1291
Assets 4
Loading