It has to be done, but it’s sometimes a pain. Updating the SDK libraries for your ad networks. As I discussed earlier, sometimes things go awry and can take a little time. Usually, however, it’s not a big deal and can be resolved with a little tinkering (and maybe some web searching).
A big plus, however, is that there may be bug fixes and more importantly feature updates. I just integrated 3.0 version of the MobFox SDK, and was pleasantly surprised that they removed another permission, the WiFi state access.
I also updated MobClix to 3.1.1, but I don’t recall any significant changes in this round.
Removing permissions is a good thing. I’d prefer my apps to be as trim as possible, and users do too. Excess permissions can scare off users, particularly if they don’t know why your app is requesting it. So, I’m always glad to see ad vendors shed permissions that they don’t really need.
When installing the MobFox 3.0 SDK (which interestingly includes the 1.2 jar), I noted that the instructions don’t require as many permissions any more. The following were removed from their list of required permissions:
I already use the network state myself to make sure I don’t access the network when it’s not connected, but the WiFi state permission can now be removed from my apps. That’s a good thing!
Well, obviously I’m going to indicate the removal of the permission in my release notes. Beyond that, I’m reviewing my manifests again to make sure they’re up to date.
How about you? If you have any fun (or not so fun) update stories or warnings with ad vendor SDK updates, let us know in the comments section.