We have recently released version 1.0.0 of our application and have sent out numerous promo codes in the past couple of days. I was just wondering whether they will still be valid for the 1.0.1 update which we have just submitted?
Yes.
Promo codes apply to your app no matter the version (only the version currently available on the store), and no matter the price (even if it's free a code should work.)
Here is the text from the apple promotional website:
Select an application and enter the number of codes you are requesting. You are given 50 codes for each version of an application. They are for non-commercial use and will expire four weeks after they are requested. These codes can only be used in the U.S. iTunes Store.
From this text, it is clear that you can issue brand new codes for new versions of your app. It is not clear whether your codes from 1.0.0 will still be valid for the 1.0.1 version of your app. I would think that they would still be valid, but that's just a guess.
Related
So I applied for an expedited review on the 8th of december and it was approved, processed and ready for sale on the 9th of December.
I have version 2.0.1 on my phone, and the version 2.0.2 is not showing up as an "Update" in app store. When going to app store it will show me the date I upgraded to 2.0.1 and shows that is the newest one.
If i then click on the cell to show more info, it takes me to my page listing 2.0.2 and all the correct details.
If I search my app on the store, it shows correct info 2.0.1, it is just everyone who already has my app, is not being promoted to update.
It has been 6 days, and Ive contacted ItunesConnect support, they tell me everything is fine on their end and if I have users who are having problems, to instruct them to call Store Support. So I told them its all 50,000 users who are having the issue, and they instructed me to inform 50,000 people to contact Store support.
So at this point Im all out of ideas.
iTunes connect called me back after a few hours, they had spoken to Store support and there is an active bug they are trying to fix. They said this is a not a wide spread issue, but it is affecting many Devs.
They told me to sit and wait.
Edit
They never were able to fix it, after 7 days of error, I uploaded a new build, submitted for review, once approved, it kick started the process again, and was pushed correctly to the iTunes Servers.
My employer has a free iOS app in iTunesConnect that was originally released a couple of years ago and has received various updates over time. They now wish to stop supporting older versions of the application (1.x) and disable these older versions of the app.
My questions are:
Can we stop users from re-installing old versions of the app? If yes, how?
How do we disable/remove old versions of the app in iTunesConnect?
What is Apple's policy regarding disabling/removing old versions of applications?
I'm not an iOS developer and am unfamiliar with the whole Apple application development process. I have searched the web as well as the Apple developer centre and I've read through the Apple Developer Program Terms and Conditions but I haven't been able to find answers to any of my questions.
I have managed to find information about removing an application from sale but this removes the entire application, rather than just specific versions. (Deleting a free app from iTunesConnect)
David Smith's article (http://david-smith.org/blog/2012/06/20/hacking-paid-upgrades/) on Paid Upgrades mentions the ability to provide fixes for previous versions if they're not deleted from iTunesConnect. When I log into iTunesConnect, I only see the current version of the app listed so I'm assuming prior versions have been deleted already. I would, however, like to confirm that users can no longer download old versions of the app.
This article mentions users being able to download old versions of apps from iCloud (http://www.macrumors.com/2011/06/09/icloud-supports-re-downloading-some-discontinued-apps/) - can we prevent this? One option would be to mark the the version as having a "legal issue" but what ramifications does this have? and if I can't see the app in iTunesConnect then how do I do it?
I found a post asking about how to force a user to upgrade the application every time a new version is released but this doesn't answer my questions either. We want the users to upgrade but we're not wanting to force it programmatically. (Can I force an iPhone user to upgrade an application?)
I've also found lots of posts asking how to revert to previous versions of an app in the app store but again, this is not what we're wanting to do. We're wanting to disable older versions of the app but leave the most recent versions alone.
Before the flame wars begin:
Users that are unable to update to the latest version of the app for whatever reason are able to use a mobile website in place of the app. The website has the exact same functionality.
Can answers please be kept on-topic rather than getting into great debates over whether one should/shouldn't maintain legacy versions.
Thanks in advance :)
Users can typically only ever download the latest version of an application. There are a few ways I think they can get around that but in general only the latest version is available to users via the normal means.
If, however, you absolutely must prevent the old versions from being released you can do so when submitting a new update. Right after you say "Ready for Upload" you will be asked a question about if this update was for a 'legal reason' if you click YES then you will be given the opportunity to disable old versions of the app from download.
As to Apple's policy on this...I have no idea. But I can't think of any policy that would require you to support older versions moving forward.
Is there a chance of app getting rejected if the iPhone app update is submitted with wrong version number? For instance i had given the version number 1.6 instead of 1.5. The app which exists in app store is of version 1.4. Will my app update get rejected?
The version number just has to agree with the version number you specify in your Info.plist. Apple does not care about he numeric value, so nothing to worry about.
It doesn't matter. Apple doesn't have a version number naming scheme. As long as your app-version matches the version given in your itunes its not an issue. Also any error related to incorrect versions are reported during submission itself.
So naming scheme is totally dependent on the developer.
No it doesn`t matter.
i have submitted an app with version number 1.3 instead of 1.2 and it was approved.
so don`t worry..
I have client with an app in the app store that was at version 4.05 and they accidentally submitted a new build as version 5.06 when they meant to submit it as 4.06. They aren't ready yet for a full version number increase. Long story.
Is it possible to submit the next version as 4.06 to get it back on track? Or is not allowed to upload a lower version to iTunes Connect?
Yes. The version numbers only need be distinct.
From the Developer Guide:
A Version Number The unique version
number of the app. Keep the following
in mind:
Use typical software versioning conventions (for example, “1.0 or
1.0.1 or
1.1”).
Do not include words such as “build” , “version” or “beta” in your version
number. This will appear next to your
application icon on the app product
page.
Can someone provide concrete info on how the app upgrade process works on iOS as far as the developer is concerned? I've been rummaging through Stackoverflow only to find hand-waving explanations and no links to official documentation. Google search results only led to Cisco's IOS and the end-user upgrade process. I'd like to know the following:
How does the App Store know when you've provided a new version? Do I have to implement something in my app, which the App Store pings? Or do I set things up stuff through the Apple Developer website? I've been waiting 2 months for developer approval and have no idea what's going on behind those doors because I get access-denied messages when trying to read official articles.
Is there any Objective-C code I need to write for an upgrade to be possible? Any plist I need to edit?
How is payment affected when version 1 of the app is free, then version 2 is paid or version 1 is paid and version 2 changes its price.
Does Apple allow me to do forced upgrades? All the answers on Stackoverflow have been, "I think this is bad business logic" or "I think Apple forbids this, but I don't have the official documentation to prove it." At a certain point, very old versions will be too time consuming to support. You don't see Microsoft still supporting Windows 95, do you?
You just submit the new version to Apple. When it's approved, it will appear in the App Store.
Same as above, Apple pretty much does it all for you.
If you transition from free to paid, everyone that has downloaded the app for free will not have to pay to upgrade to the paid version.
IIRC you cannot force users to upgrade, but you can display a notification within the app to alert users that an update is available. To implement this, I would just have the app request a file on your server that tells the app what the current version number is. You do not need to support users on old version, if they have problems with an old version, it's fine to tell them to upgrade.