This update for Adguard Pro gives users more options for fine-tuning the filtering, improves app's stability and makes it more friendly towards blind users and users with a visual impairment. Find all the details below.
NOTE: for app to update correctly it is strongly recommended to disable DNS filtering before starting the update.
[Added] Option to block domains with user filter rules #161
With new update it is possible to make your own rules for DNS blocking, so you don't have to rely 100% on our filters. If you want any particular domain blocked on DNS level, just add a rule like this to User filter:
and it will be blocked from now on (example.com in this case). As an alternative way, you can enable DNS log, visit the website in question, then find the respective request in the log and block the domain in request details.
It is important to note that in the next update there will be an option to block ads on the DNS requests level but without actually using Adguard DNS.
[Improved] New filters server is now used instead of AG backend #200
You might not notice this change right away, but it is secretly one of the most important ones. Now HTTPS protocol is used to update filters instead of HTTP, which will result in fixing several problems, especially the background filters update problem.
[Fixed] DNS filtering can't be turned on using Voice Over screen reader #170
We continue to improve our app in terms of accessibility to blind users and users with a visual impairment. It used to be impossible to enable DNS filtering using Voiceover - now this problem is fixed.
Other
[Fixed] Adguard does not validate filter text #154
[Fixed] App crashes if you try to add incompatible rules to User filter #193, #285
[Improved] Rules converter updated to the latest version #275
All the details can be found in our GitHub repository.
You can download Adguard Pro on iTunes.
NOTE: for app to update correctly it is strongly recommended to disable DNS filtering before starting the update.
[Added] Option to block domains with user filter rules #161
With new update it is possible to make your own rules for DNS blocking, so you don't have to rely 100% on our filters. If you want any particular domain blocked on DNS level, just add a rule like this to User filter:
Code:
||example.com^It is important to note that in the next update there will be an option to block ads on the DNS requests level but without actually using Adguard DNS.
[Improved] New filters server is now used instead of AG backend #200
You might not notice this change right away, but it is secretly one of the most important ones. Now HTTPS protocol is used to update filters instead of HTTP, which will result in fixing several problems, especially the background filters update problem.
[Fixed] DNS filtering can't be turned on using Voice Over screen reader #170
We continue to improve our app in terms of accessibility to blind users and users with a visual impairment. It used to be impossible to enable DNS filtering using Voiceover - now this problem is fixed.
Other
[Fixed] Adguard does not validate filter text #154
[Fixed] App crashes if you try to add incompatible rules to User filter #193, #285
[Improved] Rules converter updated to the latest version #275
All the details can be found in our GitHub repository.
You can download Adguard Pro on iTunes.
Last edited: