I have an iPhone app that also features autorenewable products as an in-app purchase. The products are subscriptions to our service for up to 1 year in the future. We wanted to remove the whole in-app-purchase and autorenewable product from our app in the next version.
To accomplish this, we removed the signup option inside our app, so no new user should be able to sign up. Now we would like to disable the automatic renewal for all existing users.
How can I accomplish this? Is it sufficient to remove the in-app-products for our app inside iTunes Connect? Do the users get notified about this?
According to Apple (see WWDC 2011 Session 510, In App Purchases for iOS and OS X, at the 48:55 mark), the only things you can do as a developer to prevent subscriptions from auto-renewing are:
Raise the price.
Remove the auto-renewing IAP product from iTunes connect.
In both cases, notification emails are sent to subscribers, though not immediately. The talk says Apple checks 10 days before a (yearly) subscription renewal and sends email at that time. It's not documented anywhere, though, so I'd treat that as an implementation detail.
I've done the latter (removing the product) several times with my own (monthly) apps, and it seems to work as advertised.
One important note: if your app is a Newsstand app, it must have at least one auto-renewing subscription available. If you remove the last one, the app will be removed form the App Store. Users who have already purchased it will still be able to use it, and will be able to download copies from the "previously purchased" section of the app store, but no new copies will show up for purchase in the App Store proper.
It will depend on how you've implemented your system. Do you check receipts (and provide data/service) from your own server, or do it all within the app directly with Apple's servers?
In iTunes Connect you can remove a product from sale, effective immediately or at a future date. I suspect that's enough to stop a renewing subscription. (Remember you can test this with shortened timescales in the Sandbox.) But if not:
If you use your own server to validate receipts, go and give it an incorrect shared secret so that the verification step fails. That means the subscription validity will return as false (although for the 'wrong' reason) so your customers won't be able to renew.
If you do it within the app, generate a new shared secret so the one within your existing structures is incorrect. Then, as above.
If you can, I suggest sending a notification to your current users notifying them of the change, suggesting that they change, and letting them know it will 'fail' in the future but that's ok.
I got my application approved on app store.
But due to some change in the feed I am using my app is crashing now. What am I supposed to do now?
Giving an update will take 7 days for apple to approve and I will get bad reviews if any one downloads it in between.
What am I supposed to do now?
You could:
Fix the feed.
Remove the app from sale until you fixed the bug and the update is approved.
Remove the app from sale until you fixed the bug and the update is approved and request a speedy review.
To remove a App from sale, go to the Rights and Pricing of that app in iTunnesConnect and set the Availability Date in the future. this will remove the app from sale. Just put the date back to now to make it available again.
You can ask for an expedited review (http://developer.apple.com/appstore/contact/appreviewteam/), if you haven't abused of it yet and have real reasons (as it seems) to ask for it, they will review your App in between 1 and 3 days... :)
If you want to stop selling your App while it is happening, you can go to the Pricing menu in iTunes Connect and remove all the countries available...
You need to submit an expedited review request. From my personal experience I've generally pushed these out within 24 hours. Usually Apple does these as a one time exception, and is supposed to be used once in a great while. I've done 4 total in 2 years. Anyhow, since there is contact information on the website, if users download and contact you reply back that there are pending updates, and will be out shortly.
You could go through pausing delivery of app until ready, etc, etc. Availability can be changed and automated via dates. You can remove from countries available.
Here is link for expedited review. You'll need your App ID and Name, etc.
http://developer.apple.com/appstore/contact/appreviewteam/
I have an application that we are building to be delivered to our users for free. However, the business wants to be able to sell this application to anyone else who might want it. Is there anyway we can do this?
The suggestions and concerns we've come up with are:
Submit app with price and deliver free download codes to users, but I believe that we only get something like 50 free download codes and we have more than 50 users.
Submit app for free, but make content an in-app purchase and have some mechanisim for allowing our users to validate and get the content free. We think that Apple will hate this since the application isn't functional without the content.
Submit application twice, one free and one paid and just direct our users to the free one. This means that our free version can be found and used by anyone cutting into the revenue stream.
Any suggestions/advice/hints/rants welcome.
Have you considered Software as a Service? The app is an extension of the service. Make the app free to anyone, but to get anything useful out of the app, require username/password or some other validation. You'd be hard pressed to find an app today that doesn't require some sort of signup process.
There are plenty of options you can go with.
In-App Purchase
Free/Lite version of App
Paid version of App
Just a matter of what you and your customers want. Good luck.
Why not have a very basic version of the app available for free (so that Apple is happy) and then have the rest of the app "unlocked" when the user either:
Registers their copy of the app back with your servers (covers giving it to some for free)
Makes an in-app purchase to unlock the rest of the functionality
This keeps Apple happy, gives you the functions you want, and is only minimal effort.
You can pay for and gift paid apps to iTunes account holders. Making the app appear to be "Free" to those recipients. If it's your own app, Apple will keep (only) 30% of the price you pay, so add that on to your cost of doing business.
OK so have a problem with the whole in-app purchase review process and hope someone can shed some light/experience on it.
We have a project which is a magazine for the ipad. Each issue requires an in-app purchase before it is downloaded. The issues are served from an XML feed when a new one is published.
The problem is, how can we have Apple review an in-app purchase without displaying the new issue. They wont be able to see it in the live binary. If we publish the issue we have to say "unavailable", which looks extremely unprofessional to the customer, until the in-app purchase is reviewed.
We dont want to have to publish a new binary each time a new issue is published as thats a pointless exercise for the customer
Thanks, any suggestions apart from change message to "coming soon" would be apprciated. The only other thought we had is a flag in the app settings which displays "unavailable issues"
If you login to your iOS developer account, you'll find this Getting Started with in App Purchase pdf file, which has information that you'll need in your setting up with your iAP item.
Specifically, I think what you need is an item belongs to the category named Subscriptions. This should solve your problem.
You can use consumable purchases, i.e. right to download 1 article. 5 purchases - 5 articles.
Or, give a user subscription for month or so.
You could always just keep some kind of "sample" issue available for the purposes of the user demoing the software.
That, or a few select pages from the active issue could be specified as "demo pages", as in they would be viewable from a demo version of the software.
My team and I have an app which we're going to be submitting to the store pretty soon, but we know that we'll be selling the app to another company in the near future. Does anyone have any experience with moving an app's ownership to another account?
Specifically, when I sell an app to another company...
How do we move the app to their account (what's the mechanism)?
Can my users still get updates (released by the new owner) without having to re-buy/re-download the app?
Starting June 11, 2013 this has officially become possible.
Here's the official note:
Dear developer,
Apps can now be transferred from one developer to another within iTunes Connect, for example after an acquisition or when a distribution deal expires. Transferring the ownership of an app does not affect the app’s availability on the App Store. All ratings and reviews will be transferred and your customers will continue to have access to all available app updates.
To transfer an app, go to the app’s App Summary page in the Manage Your Applications module on iTunes Connect and click Transfer App. Make sure that:
• Your account is active
• You have accepted the most current version of your contracts
• Your app has at least one approved version
• Your app is in the Ready for Sale, Invalid Binary, Rejected, Developer Rejected, or Developer Removed from Sale state
• Any associated In-App Purchases are in the Ready to Submit, Ready for Sale, Rejected, Developer Removed from Sale, or Approved state
• You know the Apple ID of the recipient’s Team Agent and their Team ID.
For more information on app transfer, see the video tutorial on iTunes Connect. To find answers to common questions about app transfer, see the FAQ on iTunes Connect.
Regards,
The App Store team
UPDATE: THIS ANSWER IS OUT OF DATE. IT APPEARS TO HAVE BEEN CORRECT AT THE TIME IT WAS WRITTEN. THERE IS NO NEED TO DOWNVOTE IT, BUT DON'T BELIEVE IT EITHER!
Official answer is No. From the iTunes Connect FAQ:
I sold my app to another developer and can no longer distribute on the
App Store. Can I transfer the app to
the new developer's iTunes Connect
account?
At this time, apps cannot be
transferred to another developer
account. If you would like the app to
be sold through another developer
account, you will need to remove the
app from sale in the current iTunes
Connect account and upload the app
under the new iTunes Connect account.
Uploading the app to a new iTunes
Connect account will disable current
customers from receiving automatic and
free updates of your application. All
customer reviews, rating and ranking
information will also be reset.
Additional resources that confirm this, from FutureTap developer Ortwin Gentz, back when he purchased WhereTo? from Sophiestication Software:
transferring an iphone app last episode
carved in stone transferring an iphone app
Follow Up: After all: it is possible (as of late March 2010).
I haven't read all comments or other threads about this issue, so this might be obsolete, but it seems it's basically related to the iTunes-related structure of the appStore.
You can't be part of the Beatles and the Rolling Stones Bands...
Anyway, eventually, a colleague managed to get things sorted out, and we got our App (which was running under my private, single Dev account) running under a new, enterprise account. We kept our ratings, our #1 place in our category in the appstore, and all in all it went smooth (after several hours of phone-calls with apple).
As far as I can recall, the main problem was those help-desk folks were knowing things were going to change, but they didn't know by when and how. Probably due to iPad coming and related timelines involved). Anyway. It's possible, and it's pretty easy. Send your request, wait a couple of weeks (might be days by now), and you'll have the transfer. One issue though: They may have some bug in their migration code, because apple mixes firstname and lastname of the dev / master account after migration. well, who cares.
I had my own experience with this, and the answer I got from Apple Developer Relations (Although it took a month to get an email response and 6 weeks for the follow up phone call) was (in short) that they currently don't offer any way to transfer individual applications from one developer account to another.
He did so by saying that there was a single "Option" for doing this sort of transfer, which is to delete the app from the account that it is currently on, and then resubmit to the Apple store from the new account under the same name (but it would have a new appstore id). I pointed out (and he acknowledged) that this would delete any existing user reviews, ruin the upgrade path for existing users, break iAds, in-app purchases, and game center integration. So it really isn't a solution at all.
He also said that it isn't possible to transfer ownership of all your apps to another existing account (they seem to lack the granularity to move individual apps). However if I wanted to give up all my apps to another individual it could be possible by creating a corporation (probably S-Corp, although he didn't advise), transferring ownership of my account to the S-Corp (which would be allowed if I were a part owner), and then selling the s-corp to the new owner. (Yikes right?)
The method I plan to go with is the following (I'll update with my success), In my specific case I have a paid application that (.99) that I'm trying to transfer to another owner:
I will create a lightweight application using the same AppID that is designed to inform users that the Application has changed owners, and provide a link to the app store where they can download the new application. When launched will upload a hashed form of their UDID to a server (which I will now have to maintain) listing them as a previous customer.
I will upload this new lightweight app to my existing account as an upgrade to the other existing application (so that when users update, they will instead be marked as an existing customer, be presented with a message explaining the situation, and a link to the new app)
I will convert my paid app to being a light application that has some functionality, but requires an in-app purchase of .99 to get the full functionality. Additionally, this new app will check with my server to see if the UDID is in the existing customers database, and if so give them full functionality (without having to do the in-app purchase).
... ARGHH! :) It's an ugly experience for the customers and a whole hell of a lot of work for the developer... but the only option provided by Apple. (Although, I'm not sure that it will even work, as it's entirely possible that they will reject my lightweight "update" application from the store, and thereby prevent the hack upgrade path as well)
UPDATE: Too much work for the person that I was trying to give the application to. Ended up not proceeding with the plan. Think that it could probably still work, and would love to hear from anyone who tries it or pulls it off :)
iTunesConnect now allows App Transfers given certain app restrictions (no iCloud or Push Notifications apps are allowed currently. Local Notifications are ok, of course.)
See the iTunesConnect FAQ on App Transfers... https://itunesconnect.apple.com/WebObjects/iTunesConnect.woa/wo/10.0.0.9.1.0.9.1.5.10.1
You can only initiate or accept a transfer if your iTunesConnect login has the "Legal" role permissions.
AFTER THE TRANSFER:
The teamId and bundleID will not change at all. Nor will any of the in-app purchase Ids.
In my company's developer account, I now see an app with EXACTLY THE SAME TeamID.BundleID as I saw in the source code that was purchased from the other company (and that source code was delivered separately, not via Apple)...
ex. BundleID = com.<some-other-company>.<purchased-app-name>
This bundleId is now listed among my other apps listed in iTunesConnect's Provisioning Profiles. I simply created new Development and Distribution/AdHoc provisioning profiles for my newly purchased app. Then I downloaded the new provisioning profiles into Xcode, just like for any of your own apps.
Quite painless. Thank you Apple.
What Lou Franco said.
Where To example is really good to consider, as they eventually had to settle for the fact that all existing customers need to buy the app again. Apple simply does not have the background infrastructure to change ownership.
Another bad consequence of the inherited made-for-music-sale-machine that iTunes originally was. Songs apparently don't change owners.
See here, for Where to resolution: transferring an iphone app last episode
Since now, this is now possible using iTunesConnect.
Apps can now be transferred from one developer to another within
iTunes Connect, for example after an acquisition or when a
distribution deal expires. Transferring the ownership of an app does
not affect the app’s availability on the App Store. All ratings and
reviews will be transferred and your customers will continue to have
access to all available app updates. To transfer an app, go to the
app’s App Summary page in the Manage Your Applications module on
iTunes Connect and click Transfer App. Make sure that:
Your account is active
You have accepted the most current version of your contracts
Your app has at least one approved version
Your app is in the Ready for Sale, Invalid Binary, Rejected, Developer Rejected, or Developer Removed from Sale state Any
associated
In-App Purchases are in the Ready to Submit, Ready for Sale, Rejected, Developer Removed from Sale, or Approved state
You know the Apple ID of the recipient’s Team Agent and their Team ID.
From what I understand, this can be done, but it requires manual intervention by the iTunes Store team, can take months to go through, and may involve some periods when your app is not on sale under either account. If you know who your customer is going to be, just put it under their account to begin with. If not, remember for the future that flipping apps is not an easy thing to do, and adjust your business model accordingly.
It is possible since June, 2013. You can transfer an app to another developer very easy - here is an official FAQ from Apple (available for registered developers).
Besides the already mentioned things I recognized, that certain issues may arise which are nowhere mentioned in the AppStore Guidelines or the documentation.
I found out several issues with apps having subscriptions (which are as of Jan 2015 not transferrable). After trying to transfer an app I found out via the FAQ in the iTC Developer Support Center aka Help Section the following things (Link to FAQ section)...
You cannot transfer apps that contain or use:
iCloud entitlements in any version of the app
Passbook entitlements in any version of the app
A SKU that matches the SKU of one of the recipient's apps, including previously-removed SKUs
In-App Purchase product IDs that match the In-App Purchase product ID of one of the recipient's apps, including previously-removed In-App Purchases
Approved auto-renewable, non-renewing, or free subscription In-App Purchases, including previously-removed In-App Purchase subscriptions Sandboxed Mac apps that share the Application Group Container Directory with other Mac apps also cannot be transferred.
To transfer any of these types of apps, the recipient must create the app as a new app. Current customers, ratings, and reviews cannot be transferred to the new app.
Also the usual requirements are:
To transfer an app, make sure that:
The transferor and the recipient have active developer accounts and accepted the most current version of all master agreements that are currently in effect
The app has at least one approved version
The app is in the Ready for Sale, Invalid Binary, Rejected, Developer Rejected, or Developer Removed from Sale state
Any associated In-App Purchases are in the Ready to Submit, Ready for Sale, Rejected, Developer Removed from Sale, or Approved state
You know the Apple ID of the recipient’s Team Agent and their Team ID If the app uses iAd, the transferor and the recipient must have accepted the most current version of all iAd contracts.
Hope that helps avoid mishaps before you try to transfer an app.
As ownership transfer is currently not-supported and an "exception process", it makes sense not to count on it as your mode of operation.
The big problem you're facing is: the app is tied to a developer account and you want to keep YOUR developer account after you transfer the app.
Hence, why not set up a NEW developer account, the sole purpose of which is to be the holder of this one app and, when you sell the app, you can just transfer the developer-account credentials to the new owner.
At that point, they can update the name, address, company name, bank info, etc.
Of course, your transfer contract will have some verbiage explaining how, in the interim, any moneys you get from Apple will be fwded to the new owner (put a time limit -- like 90 days -- on this so they don't take forever to update the info.)
I've not tried this, but it seems like a viable solution. Again, the problem is that the app is tied to developer account and you don't want to transfer yours. Hence, this Just Makes Sense™.
Recent update from iTunes Connect:
I sold my app to another developer and can no longer distribute it on the App Store. Can I transfer the app to the new developer's iTunes
Connect account?
No, you can’t transfer the app to another developer account on iTunes
Connect. To add the app to another account, remove the app from the
current account and upload it to the new iTunes Connect account.
Note that uploading the app to a new iTunes Connect account will
disable current customers from receiving automatic and free updates of
your application. All customer reviews, rating, and ranking
information will be reset. You will not be able to reuse the app name
and SKU in the old account. If you have uploaded a binary or used the
app with the iAd Network, your Bundle ID will not be reusable either.
Guess I'm late to the party but Apple just added a button to iTunes Connect to do just this. Sign into your iTunes Connect account, go to 'Manage Apps' and click on the app you want to transfer. In the section on the top right, there's a button to transfer your app now.
Cheers!
As far as I know there is no way to transfer apps to a different user/company. I think the app should be in your customers account from the beginning. Otherwise you probably have payment problems too (people paying you instead of your customer).
Why not just sell the app to a customer before releasing it. If they want to see it running before it is released, just sent them a version built with an ad-hoc certificate.
The are additional considerations:
If you just can switch ownership of the Application behind the scenes, thus changing the contract, but not the application itself, you might be fine.
But if you're just going to transfer your source code, the future owner of the app will have to sign it with his own certificate, which will basically render the app as a "new" one.
Users will lose their settings (if your app did some configuration persistence) and they'll lose the app history in the appstore (ranking, etc.).
As per a new announcement from Apple today (just after iOS 7 release) this has become possible .
It says "Apps can now be transferred from one developer to another within iTunes Connect, for example after an acquisition or when a distribution deal expires. Transferring the ownership of an app does not affect the app’s availability on the App Store. All ratings and reviews will be transferred and your customers will continue to have access to all available app updates."
Something helpful:
Apple site documentation with new itunesconnect UI released in Sep,5,2014
Transfer code using github
Note: Use agent role account, and maybe you should click "Agreements, Tax, and Banking" to request Contracts first.
I don't believe that you can transfer ownership to another account. But a simple solution would be to add URL schemes to your app to allow data to be transferred from your app to a new app that your customer would release with the same source.
The new app would have to be free though (maybe the lite version?), so your old customers wouldn't be forced into buying it again. The only real downside I can see of this is that the new app would basically be starting over again from a marketing perspective, which is no minor thing of course!
Mobile Orchard had an article on data migration from Lite to Paid versions of an application that may be of interest:
Lite-to-paid iPhone application data migrations with custom URL handlers