|Operating Systems||Windows XP SP3, Vista, 7, 8, 8.1, 10|
|Web Browsers||Microsoft Edge, Internet Explorer, Google Chrome, Opera, Yandex Browser, Mozilla Firefox and other|
|Free Disk Space||50mb|
|Operating Systems||macOS 10.10 (64 bit) +|
|Web Browsers||Safari, Google Chrome, Opera, Yandex browser, Mozilla Firefox and other|
|Free Disk Space||60mb|
|Compatibility||Requires iOS 9.0 or later. Compatible with iPhone 5s, iPhone 6, iPhone 6 Plus, iPhone 6s, iPhone 6s Plus, iPad Air, iPad Air Wi-Fi + Cellular, iPad mini 2, iPad mini 2 Wi-Fi + Cellular, iPad Air 2, iPad Air 2 Wi-Fi + Cellular, iPad mini 3, iPad mini 3 Wi-Fi + Cellular, iPad mini 4, iPad mini 4 Wi-Fi + Cellular, iPad Pro, iPad Pro Wi-Fi + Cellular, and iPod touch (6th generation).|
|Free Disk Space||24.4mb|
This is a small update which has fixed minor issues slipped through unnoticed. Hint how to add DNS server manually were clarified and widget is now greydout when PRO status turned off.
[Fixed] Sometimes tunnel does not restart correctly when the network changes #470
An important issue was found in the previous version. If network type was changed, it requires the tunnel mode to be restarted. Sometimes it didn't happen. We have completely reworked the tunnel's “behavior” when changing the connection - now, if a connection type is changed, the tunnel does not restart, and the connection to the network is not lost.
[Added] Adguard for iOS (Pro) widget #312
Now it is possible to quickly enable or disable DNS filtering directly from the Today view screen.
[Added] Support custom ports in the custom DNS settings #412
And the last important change - it is possible to manually add ports in the DNS settings. This can be useful in cases where an ISP intercepts DNS traffic and redirects it to its servers. It turns out that technically AdGuard works, but there is no filtering. In this case, one should specify the address in the DNS settings, for example - 220.127.116.11:5353 or [ff:fa::1]:5353.
Recently, Apple has announced that according to their policy, they "have never allowed apps on the App Store that are designed to interfere with the performance or capabilities of other apps". This means that the only ad blocking solution permitted in iOS are content blocking extensions for Safari browser, and Adguard Pro has to rethink its features. Sadly, the system-wide ad blocking has to go, but we keep the custom DNS functionality and look forward to developing it even more in the future.
We have also removed 'Adguard DNS' and 'Adguard Family protection' from the default DNS setups, you will need to manually add our DNS addresses to use them (although, if you have already had one of these modes selected, it will remain). Another option to keep the filtering in apps is to add our Simplified domain names filter to the blacklist as a whole.
But, aside from this sad news, we have something to tell about the new version. It features a new setting that lets you choose between the more stable work and compatibility with other VPN apps. Plus, as usual, more fixes, UI changes and what not.
[Added] New 'Tunnel mode' setting #404
We decided to introduce this setting as a response to some cases of iOS bypassing the Adguard (due to bad connectivity). What does this mean in practice? The new setting lets you choose between two modes: split-tunnel and full-tunnel. While in split-tunnel mode (the default one), Adguard will be compatible with some other VPN apps (full list here) but can be bypassed by the system. On the contrary, in full-tunnel mode, you can't run other VPN apps alongside Adguard, but iOS won't be able to bypass it, regardless of the connection quality.