I provided a new binary for a new version of my first iphone app. The new version is ready for sale today. However, when I check the app store notifications, no notification has come to me to update this app. The store version reflects the new version. Did I have to do something specific to let apple know that this needs to be pushed to the current users as an update??:(
If your new version is listed as being ready for sale, (which it is) then you're done. Apple do the notifications to users that have installed your app and when they have web access - they'll see a +1 badge on their app store icon.
It will take some time for app to propagate trough app store.. usually an hour or a two after it reaches "ready for sale state" so the best thing is to wait a little bit...
Related
I have an iPhone app that was accepted in the App Store almost a month ago. Now i have updated my app with some new features and added iOS 7 support etc.
This is actually the first very first time i am going to submit a new version of the same app to the App Store.
As far as it seems, i have to go to iTunes Connect > Manage Your Apps, select the app and then click on "Add Version" and add the version number and whats changed in the new version. Go back and add the updated screenshots and then using Xcode, i can submit it for the approval.
The question is that is there anything else that i am missing and that i should do in order to submit the new version of the app? As i said i am doing it for the very first time. Thanks!
Things you may wan't to consider:
submitting any new in-app purchases with the new version of the app
make sure your app version and short app version is higher than the one in the version currently in the app store, otherwise you will not pass validation
run validation before submitting so you can see if you get any warnings, sometimes there may be collision with Apple private apis. If they are in your code, I'd suggest to rename your methods
The only thing you need to do now is to update the version number and the build number in your Xcode application, archive your app and submit on the AppStore.
On iTunes Connect you set the new version number :
We have built an inhouse version of an iPhone application that is to replace another that is already available from another developer.
I was wondering if you think we can use "app transfer" from the previous developer and in turn replace it with our own app. Previous developer has agreed for the transfer (ofcouse excluding his code). Therefore our question is if we can transfer his app to our development name and then replace the app with our own. Our goal is that the current users of this app will receive ours as an update to what they already have and not as a different app.
In short, transfer and replace so users get our app as an update.
Note:
Please note that as we were unaware of this "transfer" we submitted yesterday our version of the app with a slightly different name. Should we cancel submition (as it is still pending for validation) and follow some route you may suggest in your replies, or stay as it is now?
If you keep the Appidentifier the same between the original version and the new version you will submit, this should work as expected. (But nobody has much know-ho of the new "transfer" option yet)
So, you process would be as follows:
Hand the old developer your TeamID and your Apple ID
The old developer transfers the current App over to your team
Once done (no clue how long that takes), you have the app in your itunes connect
Now you add a new version of the App to itunes connect and mark it as ready to upload
You upload your newly coded app that meets these criteria:
Application Bundle Identifier is the same as with the App you're updating
Your new App is signed with a correct certifcate/provisioning profile (just correct for the appid, doesn't have to be the same one)
The BundelVersion and BundleShortVersionString are at higher than those of the already submitted applications.
So basically, it will work just like a regular update.
My company had outsourced an iOS app to another company, and they published the app on the App Store using their Apple ID. The app have been available for download for a few months and has a number of users. Now my company developed a slightly newer version of the app and would like to distribute the app using our own Apple ID. What's the correct way to do it? The major concerns we have are:
Should we submit the newer version using our ID before or after we take the old app down from the App Store. Would it happen that the newer app get rejected because Apple feel the two apps are too similar? (Actually they are quite similar, for that the update is slim.)
Is there a graceful way to notify the currently online app's users that they should switch to the newer app? And How to coordinate it, since the newer app may take a certain amount of time to get approved.
Thanks.
There are some different scenarios here, I am going to try to address some of them to see which one helps you the most:
1-)You have a current application that contains no use of push notification and no use of in app purchase. This is the easiest one. Basically, It does not matter what version the user has had before. You can remove the old one from the previous developer account and add it to the new developer account. By completely removing the previous application (not just from the app store listing, but from the developer account), you can reuse the bundle ID. When the user reinstall the app, the user will be able to replace the old application with the new application (note that the new application will not appear on the user's update list).
2-)You have push notification. Here, you will have to keep the old application if you wish to maintain the push notification certificates, so, the new application will have to use a new bundle ID, which means that the app will appear on the user as a new application, and the user will be able to have both app simultaneously.
3-)You have in app purchase and subscriptions. You will need to remove the old in app purchase entries from the old developer account, and add it to the new account (if you wish to reuse the product id, if not, you will have to create it either way).
I am not sure what kind of measure you need to take if you are using iCloud and/or other services. Best course of action is to contact Apple developer support. They will give you some guidance on what to do with your specific case. Also, when submitting, make sure to point to the reviewer that you are trying to move the application from one company to another. I think they can access review notes from the review to the previous submission(instead of reviewing it as a new app), and speed up the process.
Edit: You can not transfer apps between companies using iTunes connect. More information here: link
i just released a new Version for my App in the App Store.
On a second device where i had already the old Version running, i was checking for updates. It was not available. So i had to install the app again.
Someone with the same issue? Could not find something about this in google!
First thing check that, your new version is approved by Apple and it's live on App Store.
If the app is approved and new version is live on App Store, then check that it's region. For example, inside your device, you account is belongs to India, and your app is not available for that store then it will not display.
Please check it and let me know in case of any query.
Cheers.
Is there some way to implement an auto-upgrade for an iPad app.
I would like to be able to have my app check for updates, and then upgrade itself.
As far as I am concerned the app can retrieve the update from the app-store, but:
I would like the interface to be app internal: User should just have to press an OK button for the upgrade to start (all this time staying within the app)
Is this possible at all?
It is possible to have display a notification to inform an update is available on you app and you can redirect the user to the AppStore, but an update can only be download from the AppStore.
This will reinstall the new version of your app. So you can't stay in the app to update (You need to go to the appStore and qui the app during the update).
Internally, you can only update some content for you app (not add new native code) but not with a real AppStore update.
Apple does not allow apps to download, install, or execute code that is not included in the original app submitted to Apple. The App store upgrade cannot be automatically started.
the best you can do is determine if the app store has a newer update, then prompt the user to install it by linking directly to the app page in the app store. They will still have to click the correct buttons to start the process.
Even if it were possible, it's not allowed by Apple. Your app will be rejected.
Unless you only update contents of your app, e.g. cooking receipts.