[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 - 176.103.130.130:5353 or [ff:fa::1]:5353.

Other

• [Fixed] Adguard is not working with System default DNS server in Tunnel mode #457
• [Fixed] Unable to check "System Default" in the app #461
• [Added] Need to show the disabled dns status on the main settings screen #452
• [Added] Automatically enable PRO mode when user selects any custom DNS server #464
• [Improved] DNS Naming Bug — Adguard Pro 1.3.0 (100) #453
• [Other] iOS Assistant is incorrectlty placed on the site #463
• [Other] tieba.baidu.com - Adguard toolbar is missing #416

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.

UI

• [Added] Build number on the "About" screen #406
• [Added] "Filter rules syntax" link to the User filter #375
• [Changed] Gray out "DNS settings" when PRO status is disabled #374
• [Fixed] Typos #408
• [Fixed] Filter search doesn't work #388
• [Fixed] When app is started, "Pro" button state is "disabled" for a second #371
• [Fixed] Incorrect warning message on the main screen about the filters conversion error #414
• [Improved] New Persian localization, other localizations have been updated #427

Other

• [Fixed] Adguard pro crashes #429
• [Fixed] Compatibility with iOS9 #384
• [Fixed] Can't connect to iTunes when VPN is active #385
• [Fixed] Sometimes Adguard сrashes when you open advanced settings #451
• [Improved] Logging process has been improved #430
, #373