Apple particularly is claiming these apps violate point 4.2.one of the Application Store Developer Guidelines, which claims that “Apps should use APIs and frameworks for his or her intended purposes and indicate that integration within their application description”.
While Apple has technically had these policies in position for a while, the organization has formerly been lenient with regards to enforcing them, which has permitted a multitude of blocking apps to the Store along with a boom within their recognition. Since Cupertino has made the decision to hack lower on enforcing the following tips, the creators of popular apps like Adblock and Weblock won’t have the ability to upload updates towards the App Store, although existing versions have to date not been removed.
Some ad-blocking will be fine
Apple’s apparent problem with these ad-blocking apps is the “VPN-based” operation, which installs certificates around the device to be able to block advertisements across all iOS browsers- including third-party choices like Chrome along with the Apple-owned Safari.
Formally, the only real types of blocking apps allowed in iOS are the ones that utilise the state Safari Content Blocker API which, as suggested by its name, only creates Apple’s native browser, Safari.
Whether deliberate or otherwise, this appears to become one other way for Apple to enforce using its native internet browser on its iOS. Competing browsers already have to adhere to utilizing the same iOS WebKit as Safari (policy point 2.5.6), effectively coming to a other browser a “wrap” of Apple’s own, which frequently has got the unfortunate results of poorer optimization and gratifaction.
At the moment, iPhone and iPad users can keep using any affected ad-blocking apps within their current condition, although given their lack of ability to update, they’ll likely soon become incompatible with iOS and also the browsers they are equipped for.
Maybe this will be patched up when Google integrates ad-blocking directly into Chrome.