![]() ![]() If everything goes according to our plans, AdGuard and AdGuard Pro will eventually become closer and closer to each other: we will add system-wide filtering to our regular app and then we’ll update AdGuard Pro to match it in features. ![]() Let’s start by looking at what we have: AdGuard for iOS that’s much better at blocking ads in Safari but lacks system-wide filtering, and for AdGuard Pro it’s the other way around. What are we going to do now when all these new possibilities have dawned on us? What do we do with two different but similar apps? I'll try to give you answers to these and other questions. Perhaps now you understand why this measly little update means so much to us. And finally, on this blessed day, AdGuard Pro for iOS was approved. No, seriously, repeat a couple times more. Long story short, the update was rejected, we resubmitted it again, it was rejected again, rinse and repeat. Our iOS developers immediately dusted off the AdGuard Pro code and submitted the same exact update that had been meant to come out a year before. This API is exactly what was needed to be able to filter other apps' traffic. The new AppStore review Guidelines were published on June 4th, stating that:Ĭertain types of apps - such as those for parental control, content blocking, and security - from approved providers may use the NEVPNManager API. Just like their sudden policy changes first crippled, and then practically killed AdGuard Pro, one day they effectively resurrected it from the dead.ĪdGuard Pro is a content blocking app, so it looks like this should apply to us. New beginningĪs it often happens with Apple, everything comes out of the blue. ![]() And what do you know, literally a week before the scheduled release date, we got more news from a certain fruit-related company. It was definitely something, and under the new rules it didn't really seem feasible to achieve much more. Obviously, it was lacking some key features compared to the Pro app, but it more than made up for it with drastically improved Safari content blocking. As a result of many months of hard work, we managed to partially recover some of the AdGuard Pro functionality in AdGuard 3.0 for iOS. We had to choose a different path, so we concentrated our efforts on developing the free AdGuard for iOS app. For almost a year, AdGuard Pro went into a deep slumber. AdGuard Pro wasn't the sole victim, either: lots of other apps suffered the same fate. We would have had to abandon every network-level feature to make any further changes to it, and it just wasn't worth it. AdGuard Pro looked like it was done for we were forced to freeze development. When Apple makes up its mind, you can throw yourself against the wall as much as you want, but it won't matter. We could argue that our app wasn't even doing any of that by default, but it didn't matter. Your app uses a VPN profile or root certificate to block ads or other content in a third-party app, which is not allowed on the App Store. We were trying to push a small run-of-the-mill AdGuard Pro update, and the app was rejected because: For a long time, everything was going more or less normally: AdGuard Pro was getting regular updates and was becoming better at doing its job - that is, until one day Apple decided it was not going to be that way anymore. ![]() AdGuard Pro (in beta stage at the time) was positioned as an app that could block ads outside of Safari, something that no other app could have done before. Why? To explain that, we need to go back in time and look at AdGuard Pro's bumpy road to where it is today. It looks very unassuming at first glance, but it means a whole lot. Basically, we just updated localizations and one or two random bug fixes. Recently, AdGuard Pro for iOS received a very small update. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |