AdGuard v3.6.3 for Android: Android 12 compatibility and more

If you happen to read the release notes of AdGuard for Android on GitHub, you might giggle at the fact that the coming release of v4.0 has become sort of a local meme.

We've been waiting for it passionately and, at times when the release data was delayed, rushed things saying "Well, now it’s definitely the latest version before the Big Release".

But the dawning of a new era as we call it does not rule out the necessity of the intermediate builds and certainly does not invalidate the changes made and all the scope of work done. The changes in the recent v3.6.3 are abundant but they all are ‘under the hood’, so to say. We used to consider such tasks difficult to comprehend and not interesting for a regular user, but truth be told, they are the core of our product.

One thing that's easy enough to understand is Android 12 compatibility. We've tested the new version extensively on the new OS and happy to say that they are 100% compatible. Feel free to try it yourself if you're one of the early testers for the Android 12.

And if you'd like to get into the thick of things, here are some more changes that were introduced in the v3.6.3 update. In this version we focused on updating CoreLibs. Namely, we dealt with the priority of existing modifiers and added several new ones: $denyallow, $redirect-rule, $removeheader, and $specifichide. It might be of interest to users who'd like to create their own ad filters. Besides, we've made userscript exclusions work properly and fixed all issues found.

Update the AdGuard app and share your impressions with us! We know you are waiting for v4.0, so are we. Trust us, it's worth it.