Or, perhaps they're rejects apps that allow you to create a Dropbox account. That would cover all versions of the Dropbox SDK.
The specific reasons they gave are:
- "This app contains a link that takes the user to Dropbox via Safari".
- "The concern with this app is that the user is taken to Dropbox's website, if they do not have Dropbox installed on their device, where they have the option to purchase additional storage space."
How would you read that? They seem to suggest that you can't link to any page on dropbox.com.
The problem is that neither Dropbox's login page nor their create-account page provide any links for purchasing anything, nor do they provide links to Dropbox's main site. http://rfc64k.files.wordpress.com/2012/05/dj-xhtrivxl.png
So it seems that merely because the login page is hosted at Dropbox.com, it is forbidden because Dropbox.com can be used for purchasing things. That would rule out all forms of OAUTH.
Their proposed solution was to remove the "Create Account" link, but it's not at all clear whether that was the original problem, or whether it solves anything.
The bottom line is that if your app currently uses any version of the Dropbox SDK or the Dropbox OAUTH API your app may be rejected and you're now in a state of limbo.
This is on Dropbox to fix, not Apple.
Imagine you provide a marketplace, and you curate that marketplace. And you say to customers who come to that marketplace "Don't worry, we're going to do everything we can to protect you from bad purchases". Then you say to sellers, "No deals behind closed doors. You want access to the marketplace? Sell out in public." Every time you use the iOS in app purchase API, Apple has a way to track the payment. Lets say the customer pays for a service inside of an app that never gets rendered. The customer can then contact Apple who can verify if the payment was processed, and can go about returning the customer's money while policing the marketplace. But if the purchase for a service rendered inside the app happens outside the app, then customers will have a much more difficult time getting recourse for making payments to a service provider (app maker) whose app doesn't work properly or doesn't provide the services that the user payed for.
Having said all that, Dropbox provided this API to developers. They should have built it to work inside these rules. They could let users create Dropbox accounts, they just would not be allowed to charge users from outside of an app for services that would then be rendered inside the app. It sucks, I know, but it's an important part of ensuring the quality of Apple's marketplace.
Users who are directed to Dropbox via my app are not asked to purchase anything. They are not made aware that there is anything to purchase. They are only told that "Dropbox is a free service that lets you transfer files". They create an account and it just works, and they never have to think about Dropbox or their Dropbox account again.
I don't totally agree with their stance on this but I can see why it was rejected.
It's well known that you cannot link the user to make a purchase outside of the iOS ecosystem. It was a huge issue with the eBook apps last years.
I'm not saying I agree with Apple's stance on that but they are not rejecting apps which use Dropbox because they don't like Dropbox. Dropbox is breaking the rules and as soon as they fix that (it seems they already have) there will be no more problems.