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.
Related
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
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 3 years ago.
Improve this question
When my iPhone application start, I want to notify the user if there is a new updates / version released on App store.
Does anybody have any ideas or has anybody else achieved anything similar?
Thanks
Use Nick Lockwood's iVersion library. It's whole purpose is to notify the user when new updates are available.
iVersion is a library for dynamically checking for updates to Mac/iPhone App Store apps from within the application and notifying users about the new release. It can also notify users about new features in the app the first time they launch after an upgrade.
Purpose:
The Mac and iOS App Store update mechanism is somewhat cumbersome and disconnected from the apps themselves. Users often fail to notice when new versions of an app are released, and if they do notice, the App Store's "download all" option means that users often won't see the release notes for the new versions of each of their apps.
Whilst it is not permitted to update an App Store app from within the app itself, there is no reason why an app should not inform the user that the new release is ready, and direct them to the App Store to download the update.
And if your app is not on the App Store, either because it's an in-house/enterprise iOS app, or a Mac app delivered to customers outside of the store, you can't use the App Store update mechanism anyway.
iVersion is a simple, zero-config class to allow iPhone and Mac App Store apps to automatically check for updates and inform the user about new features.
iVersion automatically detects when the new version of an app is released on the App Store and informs the user with a helpful alert that links them directly to the app download page.
Or if your app is not on the store, iVersion lets you specify a remote plist file to check for new releases, and a download URL where users can get the latest release.
iVersion has an additional function, which is to tell users about important new features when they first run an app after downloading a new version.
These excerpts were taken from the Github page here, where you can download it. There is also a comprehensive tutorial on installing and configuring iVersion, so I recommend that you check it out.
Hope this helps!
To give a comprehensive answer. There are basically two ways you can go here. Depends on where you want to put the responsibility.
App checks for new versions on server
Using this approach, you would add a method to your app that is being called on every launch to compare the current version of the app (wherever you want to save that) with the version stored on the server. To achieve this, the server must implement a small web service that returns the latest version as a string or something else very simple. No rocket science there.
Server pushes new version information to app
This way you implement more code on the server-side to do a Push Notification to your app which informs the app about the new version. Advantage here is: Less client-side code and less effort to check, because the version check does not happen every time the app is started but instead only once the new version is actually released.
you can do a call to your server when the app starts.
and that way check for a news item in your database, for example.
When the server gives you something. show it in an alert.
On the other hand, when there is an update in the appstore, doesn't the iphone give a warning?
APNS - Apple Push Notification System
Try it and google for ready server solutions.
Update: Okay, lets get it longer -
APNS is the best way to inform user about something new. It works with every state of the app - even when app closed - and it helps to avoid unnecessary requests to server.
But you will need server to send pushes - if you can write it by yourself - it's nice, but the are some services to create backend for your app (no links - no ads, just google it).
To find out how to start with APNS on the client side and how to create all needed certificates and keys read this one
Just check the latest version by communicating with your server and compare with the current version of app when the app starts up, if there is a newer version, notify the user.
Apologies in advance for the plug - but I think a service I built extending the concept from my experience building many apps solves this problem. Look at CleverStork - an Update Manager for Apps
There is something known as Silent notifications from iOS 7 and above, you can use that for
this
I want to reserve an app name that I intend to build out over the next 90 days, how do I do this in apple's web developer portal?
Update 2015:
The limit of 180 days is now gone, Apple dropped the cap this year -
You can read the full licence here, gone.
Also, you may have noticed that the app name expiring topic is gone from the contact us question tree in iTunes Connect.
That being said, as you can see in the declaration:
You will not, directly or indirectly, commit ... (e.g., submitting
fraudulent reviews of Your own Application or any third party
application, choosing a name for Your Application that is
substantially similar to the name of a third party application in
order to create consumer confusion, or squatting on application names
to prevent legitimate third party use.
This lets us suppose that if you haven't updated your binary for a looong time and someone wants to use the same name, chances are that if they ask for it, they will get it, but yeah, technically speaking, you don't need to worry about this anymore.
Update 2014:
As stated in the iOS Developer Library, the limit is now 180 days:
Note: After you create your app and assign it a name, you have 180
days to deliver a binary or else your app will be deleted from iTunes
Connect so that the app name is free for use by the developer
community. Per section 3.2 of the iOS Developer Program License
Agreement, squatting on an app name to prevent legitimate third-party
use is prohibited. For information about email alerts you will receive
to remind you of this policy, see “App Name Expiry.”
90 days you say? This wouldn't be the first project that was supposed to take 90 days but needed more.
Once you fill in the information in itunes connect you have 120 days. After these 120 days your app name will become available for other developers. Yes, others, you can't take it again.
So you better make sure that you have your app ready for sale in 120 days.
You should read the itunes connect developer guide. It explains the process in detail. It's too complicated to answer this in a 5 minute stackoverflow answer. But the others outlined it, and I just wanted to mention = the 120 day limit. Happy squatting.
You don't do it in the Developer Portal, you do it in iTunes Connect.
Log in using your developer credentials
Click Manage Applications
Click Add New Application
Complete the basic information, including the app name
This resources implies that app names no longer expire.
TUTORIAL: RESERVE YOUR APP NAME FOREVER
Log in to https://itunesconnect.apple.com
Click Manage Your Apps
Click Add New Application
Complete the basic information, including the app name
Upload temporary icons and screenshots (for iPhone 4 & iPhone 5)
Change the app status to “Waiting for Upload”
Create a very simple app and use the new bundle ID
Submit the App to the App Store for Review (as you normally would)
After the status has changed to “Waiting for Review” go into iTunes Connect
Click Manage Your Apps > View Details > Binary Details
Click Reject this Binary
This will set the status of your application to “Developer Rejected”. Since you have successfully submitted a binary and had a “Waiting for Review” status it can sit in that status forever, therefore your app name is parked forever! Apple considers it a “real” app since it was officially submitted. So now sit on your great app name until you’re ready to finish development.
(Source 1, Source 2)
In iTunes Connect, go to Manage Your Apps and then Add New App. You can choose a name and enter other relevant information, but not upload binaries at this point. You'll also be able to set a release date in the future.
Go to iTunes Connect, then Manage Your Apps, then Add New App.
Create an App with placeholder data (you'll need screenshots, real or temporary).
If you don't upload an associated production [App Store] distribution App within 90 days, you'll lose the right to use that name forever.
Cyber-squatting on an App name you don't make use of is bad form.
If you decide you don't want to use the name, please delete it and free it up to someone who will.
You can add the application as suggested above. And about app name reservation here is my answer.
After creating your app and it is in the state Prepare For Upload or Waiting For Upload, you have 180 days (6 months) from your creation date in iTunes Connect to deliver a binary to Apple. If you do not deliver a binary before the 180-day deadline, your app is deleted from iTunes Connect. As a result of this deletion, your app name can be used by another developer and you cannot reuse the app name, SKU or bundle ID.
I got this information from apple documentation and the link is
http://developer.apple.com/library/ios/#documentation/LanguagesUtilities/Conceptual/iTunesConnect_Guide/8_AddingNewApps/AddingNewApps.html#//apple_ref/doc/uid/TP40011225-CH13-SW1
Search for "App Name Expiry" and it leads you to the required page.
I hope this helps all of us.
I've submitted my application to the app store and had it approved. I'd set the release date to a few months in the future, but in the meantime have added a lot of extra functionality to the product.
I still want my app to be listed as a 'new release' when it comes out (the release data hasn't been reached yet) so should I replace the binary, or do I have to remove the old app completely and start a new app?
Obviously, the previously approved app hasn't been released so I don't want the new code to be counted as an update.
Cheers,
Bryn
I asked the question here mainly because there is much more active iPhone community here, coupled with the huge amount of questions regarding iStore submission/code signing etc.
For anyone still wanting an answer to this:
If the application has not ever been released, reject the binary and create a new application altogether. If you want to keep the same name as the app you'll have problems since Apple won't allow you to completely remove the old application and you can't have two with the same name. In this case, email them directly explaining the situation and they should rename the old application to an arbitrary name, freeing up the name for the new app
This question already has answers here:
Can I force an iPhone user to upgrade an application?
(16 answers)
Closed 5 years ago.
I am about to upload my Iphone application to the apple store, however I intend to release more versions in the near future. Is there anyway to make my application auto update once I upload a new version to the apple store?. That is as I am about to upload version 1.0, once i upload version 1.x, can the user be notified of this or can the application be auto-updated?. Can anyone point me in the right direction?. Any help will be greatly appreciated. Thank you.
-Oscar
No, this functionality is not available on the iPhone. The AppStore provides updates through the store only, and Cydia provides updates through Cydia only.
The direction i've seen many applications take is at start, check an XML file that you host for information on newer versions, and typically display a message to the user (preferably in a news ticker or non-obstructive manor) about a new version being released, and why they should upgrade.
You can't auto-update, however as far as I'm aware nothing prevents you from notifying the user that a new version is available, within your app. For example you could contact a web server to find out what the latest version is, and compare that to a build number in your app bundle, then display an appropriate alert/notification to the user. Or, you could get fancy and use the 3.0 push notifications for this.
In theory the appstore app/itunes will do this anyway, but it's clear that a lot of users don't see that.
Another thing you can do using the method I outlined (that the app store won't do) is tell the users that a new version is available, what it does, and that it's waiting for apple.
Even simpler is just to embed an 'announcements' channel in your app somewhere. That lets you talk to your users without waiting for apple - you can tell them there is a new version on the way, etc. I do this with an app I'm beta testing - a button on the main screen shows announcements, which I pull from my server.
Maybe if enough app developers did this, apple would start turning the approvals around quicker. Or change the legalese to prevent it [assuming it doesn't already] :-)
This is functionality provided by the app store. When you submit new versions, after apple has approved them, they will become available through the app store as updates to users that already have the app installed.
User will see new available updates to apps he owns in iTunes. User can then choose to get the update.
I'm not sure about updates via iPhone but if you pay for data downloads you would prefer to download apps/updates over iTunes on your Mac and then sync to iPhone. It's cheaper that way.
My guess is automatic version updating is intentionally left out. Think about it: what kind of strain will they have on their server if everyone on the planet with an iPhone downloaded An update to Fruit Ninja at the same time? I think their passive notification to the users via the red circle and white number allows them to spread out/stagger the update downloads and reduce server load.