It will, but only for Safari. We need full content blocking capabilities for this, DNS is just not enough.
[AdGuard PRO for iOS] v1.0 beta
- Thread starter vasily_bagirov
- Start date
-
- Tags
- adguard pro beta version
- Status
Andrew Peplow
Beta Tester
TestFlight is showing an update but its stuck in middle of updating.
Andrew Peplow
Beta Tester
I just deleted Adguard and reinstalled it to new version
Edit: The update tells you to turn off DNS in submenu before updating.
Edit: The update tells you to turn off DNS in submenu before updating.
Yes, as we mentioned in testing instructions.
SlowMemory
Beta Tester
This app https://www.adblockios.com/ claims that it is using fake VPN to do some DNS based filtering without connecting to the remote server, it this method what is going to be used in full-scaled on device filtering? Doesn't this mean that full scale ad blocking in iOS is approved by Apple?
Last edited:
@SlowMemory we are using the same approach with fake VPN and DNS blocking in Adguard Pro to block ads in apps throughout the device.
No we don't.
The method we use involves VPN, but it is very different. I suppose the word VPN is the only thing in common here.
Let me elaborate a bit.
What they do
They install a VPN profile, which contains a list of rules controlling when iOS should try to use it. Each rule looks like "access domain example.org through the VPN". VPN points to a blackhole, so instead of accessing example.org, the rule actually blocks access. This is a very simple approach, but there was nothing better until network extensions were introduced.
What we do
We use iOS network extensions API. The downside is that this is much more complicated than building an XML file and involves some low-level coding. On the other side, this API allows us to control the filtering process. For instance, the showing you the DNS requests log would be impossible to implement with the old approach. Also what we did in the first version is just a small part of what we are planning (and able) to do.
What they do
They install a VPN profile, which contains a list of rules controlling when iOS should try to use it. Each rule looks like "access domain example.org through the VPN". VPN points to a blackhole, so instead of accessing example.org, the rule actually blocks access. This is a very simple approach, but there was nothing better until network extensions were introduced.
What we do
We use iOS network extensions API. The downside is that this is much more complicated than building an XML file and involves some low-level coding. On the other side, this API allows us to control the filtering process. For instance, the showing you the DNS requests log would be impossible to implement with the old approach. Also what we did in the first version is just a small part of what we are planning (and able) to do.
Last edited:
Noticed.
New beta version is available.
- Status