Dropbox fixes app rejection issue, complies with Apple's rules
Applications using the Dropbox development kit for iOS are no longer being rejected from the App Store by Apple after links to an external purchase option were removed. — Filip Radelic, developer of the Cambox application for iPhone …
Context & Ripple Effects
The rejection wave began on May 1, 2012, when The Next Web reported that apps built with Dropbox's iOS kit were being pulled from the App Store over links to an external purchase option — a violation of Apple's in-app purchase rules that caught both Dropbox and its developer ecosystem off guard. By May 2, Dropbox said it was working directly with Apple on a fix.
Today's resolution closes the loop: Dropbox stripped the offending external purchase links from the SDK, and Apple's review process is once again approving apps that embed it. iPhone developer Filip Radelic, whose Cambox app was among those affected, confirms submissions are going through — meaning an entire class of third-party apps was blocked for roughly ten days on a dependency none of them controlled.
First-order effects
- Developers using the Dropbox iOS SDK — like Filip Radelic with Cambox — can resume shipping updates and new apps after being frozen out of App Store approval since early May.
- Dropbox removes external purchase links from its own SDK, trading a referral path for guaranteed distribution of every app that integrates its storage.
Second-order effects
- Other SDK vendors embedding purchase or subscription links in iOS kits face pressure to audit their code proactively, since Apple demonstrated it will reject downstream apps — punishing thousands of developers — rather than just the SDK owner.
- App-dependent businesses learn that a single third-party dependency can halt their release pipeline without warning, raising the cost calculus of building on outside SDKs inside Apple's walled garden.
Third-order effects
- If enforcement stays at this level, iOS development structurally consolidates around SDKs that treat Apple's payment rules as a hard constraint at design time, not a patch-after-rejection fix — a governance gap between what platforms ship and what app stores permit.
- Apple's willingness to block entire ecosystems over individual rule breaches reinforces the App Store as the de facto regulator of mobile software economics, with third-party platforms absorbing the compliance burden.
The trend: Mobile platform gatekeeping is shifting from policing individual apps to governing the SDK layer beneath them, forcing infrastructure providers to build to app-store rules or freeze their downstream ecosystems.