This is a technical update aimed to increase the app stability and fix minor bugs.

The app now runs more smoothly thanks to this minor update, which fixes a number of bugs.

The app now runs more smoothly thanks to this minor update, which fixes a number of bugs.

This update focuses on what matters most: privacy and filtering quality. We’ve added post-quantum cryptography support to DNS (for DoH, DoT, and DoQ) and updated SafariConverterLib to unlock new filtering capabilities and improve rule handling behind the scenes.

“Dear developers, can we get a bugfix pronto?” Of course you can! Right after the release, we serve you a hotfix with a resolved problem and fine-tuned operation.

A small bug has crept into the release. That’s why we’re publishing a hotfix today: so you can enjoy the service, and we can get on with some bigger tasks.

This release brings an updated SafariConverterLib. Rules now load in Safari up to five times faster, and advanced rules are applied more efficiently. Converting rules and enabling filters are now quicker and smoother than ever.

This version improves filtering speed and compatibility with the latest filtering rules, delivering more precise and reliable ad blocking. We’ve also adapted to recent changes on YouTube, so you can once again watch streams ad-free in AdGuard’s video browser.

This is a technical update aimed to increase the app stability and fix minor bugs.

This is a technical update aimed to increase the app stability and fix minor bugs.

This update is just a chill guy that makes the app up to 30x faster. We did some work on Safari Converter, so now AdGuard filtering rules are converted to Safari rules in just 0.5–2 seconds instead of 10–30. You will notice the difference especially when updating, enabling, or disabling filters and turning protection on.

Ad-free YouTube has returned: we have fixed an issue on iOS 18 that prevented videos from being shared to AdGuard’s internal ad-free browser.

This update brings a bit of style: iOS 18 introduced customizable app icons, so now they’re available for the AdGuard app as well. To stay true to the branding, we added our own versions for Light, Dark, and Tinted icons instead of just relying on iOS-generated ones.

With Apple fixing its iOS 17 bug that was limiting the number of Safari content-blocking rules, we removed our temporary workaround for that problem. In short, that means you can finally enable a large number of filters without them crashing, thanks to the fact that all of the 900K rules are available again. Please note that for this fix to work you need to update to the latest iOS (but if you are using iOS 16 and below, this bug doesn’t affect you). Also, we updated Scriptlets — one of the essential libraries needed for the app’s performance.

The app now runs more smoothly thanks to this minor update, which fixes a number of bugs.

Important improvements for the DNS protection feature: no more DNS leaks and connection instability when changing networks. Updated libraries that are essential for the app’s performance: DnsLibs, TSUrlFilter and Scriptlets. > Starting with this version, AdGuard for iOS supports only iOS 13 or later.

In this version, we’ve added HTTP basic authentication for DNS-over-HTTPS. This is useful if you have your own DNS server and don’t want someone else to use it. There is a nuance, though: there are not many DNS servers that support this feature right now. But soon they’ll become available in AdGuard Home and AdGuard DNS, so stay tuned! Besides, we’ve fixed minor bugs and updated DnsLibs and Scriptlets.

Fixed an issue on iOS 17 where filters would just update endlessly without actually updating. While we were trying to get to the root of the problem we discovered that it was caused by a bug in iOS itself (content blocker’s crash). It took us a lot of time and effort, but we managed to find a workaround and fix the problem — you can learn more about our solution from AdGuard blog. Also, we updated the dependencies of three components that are essential for efficient blocking: SafariConverterLib, Scriptlets, and TSUrlFilter. Lastly, we reworked DnsLibs (our DNS filtering engine), which significantly improved DNS-over-HTTPS/3 stability, and implemented some other fixes for the app’s better performance.

This is a technical update aimed to increase the app stability and fix minor bugs.

Spring is the time for renewal, and AdGuard products are no exception. We've updated all the libraries used in the app and improved the UI, so now AdGuard for iOS runs smoother and is more user-friendly. Advanced blocking rules acceleration The Advanced Protection feature is something we're proud of and what sets us apart from other content blockers on iOS. With this module, AdGuard for iOS can apply advanced filtering rules that supplement standard Safari content blocking rules and help effectively tackle complex and encrypted ads. However, due to the peculiarities of iOS, the *Advanced Protection* feature’s operation was always limited compared to other versions of AdGuard. For example, some rules applied noticeably later than page load. Sometimes this led to ad "flickering" as it was only hidden after page loading. In other cases, this even prevented certain ads from being blocked. When preparing the new version of AdGuard for iOS, we put in a lot of effort into speeding up the implementation of advanced blocking rules which directly improved the overall app performance. We hope you'll notice the difference. Native support for the :has() pseudo-class With Safari v16.4, content blockers gained the capability to select elements for hiding using the :has() pseudo-class. While this might sound complex and confusing, it's essential to know that this feature is incredibly important to us. It allows for the selection of ad blocks based on their content. Until AdGuard v4.4.6 for iOS, support for the :has() pseudo-class was implemented as part of the Advanced Protection module, available only in paid version. Now, this functionality is available to all AdGuard for iOS users!

In this version we've significantly updated our DNS filtering library — DnsLibs — so it consumes less resources and runs faster. Besides, the DNS-over-QUIC protocol implementation now supports RFC 9250 (proposed standard), and the experimental status was removed from DoQ support. Finally, we've updated our Safari rules engine and fixed a couple of bugs.

In this version we’ve updated the filter libraries and fixed the YouTube player on iOS 16. Now you can watch videos ad-free right in the AdGuard app. To do this, tap “Share” in the YouTube app, tap “More”, and select “Block ads on YouTube (by AdGuard)“.

This version brings the updated rule converter library and some important improvements to the Advanced protection module. > Please note that if you're updating from v4.4.0 you may need to re-enable AdGuard content blockers in Safari settings and check for filter updates in the app.

This is the first update AdGuard for iOS gets since changing the developer account. Please note that you may need to re-enable AdGuard content blockers in Safari settings and check for filter updates in the app.

Meet AdGuard v4.4.0 for iOS! In this release we have fixed only one, but incredibly annoying issue with AdGuard DNS filtering module handling network changes. Now everything works without glitches and we can finally relax (for a while). Hope you will enjoy the new version.