Posts tagged private api
Apple Removing Wi-Fi Scanning Apps from App Store
Mar 4th

Cult of Mac reports that Apple has begun removing apps from the iTunes App Store that scan for Wi-Fi access points. It looks like these apps are being removed due to their use of private APIs, which is prohibited by the iPhone SDK agreement. This would make it similar to the recent removal of apps that misused the iPhone camera DCIM folder to store and exchange documents.
There’s been some suggestion, however, that list reflects a policy change from Apple closer to the recent removal of sex-based apps.
Our speculation is that Apple has either added the Wi-Fi private APIs to their static analysis tool, or has just finally gotten around to checking for them. That would make it appear like a new policy when it’s actually the originally agreement finally being enforced.
Some developers believe long term lack of action by Apple equals tacit approval for private API use. Those beliefs likely have to start changing. When Apple makes an API public, they’re guaranteeing that developers can use them and have faith Apple won’t break them (and the apps built on them) in a future update. Private APIs are the opposite — Apple can and will change them at any point, breaking apps that try to use them when they shouldn’t. In some cases Apple is working on public versions of private APIs and will release them in future versions of the iPhone OS. In other cases they aren’t — sometimes for security, other times just for proprietary reasons.
In either case, this isn’t the first and likely won’t be last set of rejections. While we feel for developers, we feel more for users who may have come to depend on the functionality of these apps.
If you’re a developer who’s dealing with this and have a better take on the situation, please let us know!
[Thanks to everyone who sent this in!]
Apple Removing Wi-Fi Scanning Apps from App Store is a story by TiPb. This feed is sponsored by The iPhone Blog Store.
TiPb – The #1 iPhone, iPad, and iPod touch Blog
TiPb Presents: iPhone Live! #76 — Game On!
Nov 21st

Join Rene, Chad, and Precentral.net’s Keith Newman for Apple gaming, profit share, OnLive, private API, Facebook fallout, Verizon attack ads and AT&T strikes back, gPhone cometh, Palm Pixi, and all the news, plus your questions answered! Listen in!
Credits
Thanks to the the iPhone Blog Store for sponsoring the podcast, and to everyone who showed up for the live chat!
Our music comes from the following sources:
This is a story by the iPhone Blog. This feed is sponsored by The iPhone Blog Store.
TiPb Presents: iPhone Live! #76 — Game On!
Three20 Framework and More on App Store Screening for Private APIs
Nov 20th

A little while ago we posted about Apple’s new use of a static analysis tool to find private API calls and reject the apps that make them. Rather than Storm8 or Unity this time, however, it’s former Facebook developer Joe Hewitt’s pioneering Three20 framework that’s getting caught.
Daring Fireball has some details:
One popular open source framework, Joe Hewitt’s Three20 (linked here on DF back in March), played a bit fast and loose with private APIs, and so now there are numerous developers with apps getting flagged for private API calls made from the Three20 framework. This Google Groups thread [link] covers the problem and the work that’s being done to create a branch of Three20 that’s free of private API calls.
Gruber also links to RogueSheep, whose Postage app has gotten caught via Three20, and has some suggestions to help them help Apple help them avoid getting rejected for unintended private API calls in the future:
Making the static analysis tool available to developers would indeed be helpful. But I suspect it wouldn’t work in terms of game theory. Honest developers could make good use of having access to the tool, to help ensure their projects are free of private API violations. But dishonest developers would use the tool to figure out ways to slip private API calls past the checker. Parrish’s second request, for Apple to run the tool against submissions far sooner in the review process, strikes me as a good and reasonable one.
Us as well.
This is a story by the iPhone Blog. This feed is sponsored by The iPhone Blog Store.
Three20 Framework and More on App Store Screening for Private APIs