We have an app targeting iOS 5 that uses UIDevice.uniqueIdentifier to get an ID for the device.
On iOS 6 and later we're replacing this with UIDevice.identifierForVendor.
When we submitted however, the app got rejected for using UIDevice.uniqueIdentifier - which we need on iOS 5 since it doesn't support UIDevice.identifierForVendor.
Does this simply mean we can no longer support iOS 5 - since we can no longer submit an app that has a way to get a device ID?
Related
We currently have an iOS 7 App in the AppStore that works on iOS 7 and iOS 8 devices. Now we implemented some iOS 8 only features and will publish this App as an update for the current iOS 7 App. I know that iOS 7 devices will not update to the new version but:
Will iOS 7 users still find and be able to install the older iOS 7 App?
Yes, iOS 7 user will be prompted that they can't update to this latest version but can download a pervious version of your app.
But there is still the question way not detect whether or not the user can use the new iOS 8 only feature and make it optional in the app. This way iOS 7 user can still enjoy a big part of the app, just not the part for iOS 8.
Yes, but this comes with a tradeoff:
There are only 3 possibilities to install the old iOS 7 app on an iOS 7 device:
You already own the app and can install the old app on your iOS 7 device.
If you don’t own the app you have to download it once on an iOS 8 device. After this, the app will be available on your iOS 7 device (assumed you use the same account).
If you don’t own the app you can use iTunes to download/buy the app. After this, the app will be available on the iOS 7 device (assumed you use the same account).
Unfortunately the most common usecase to just download the app in the iOS AppStore for the first time will not work.
How long after iOS 6 comes out that developers HAVE to submit using iOS6?
My concern is that migrating my app to iOS6 will take a long time, and I would rather push out a new build right now with the partial features I implemented.
Thanks for your help!
Somewhat after iOS 4 can out, the minimum Deployment Target requirements for submission were raised to 3.0. Reportedly these requirements are or will rise to iOS 4.3 after iOS 6 comes out. So developers likely won't be required to submit apps using an iOS 6 minimum Deployment Target until after iOS 7 or 8 comes out (unless Apple changes their mind, which is always possible).
I'm considering submitting an app that will only support iOS 5. When iOS 4 users peruse the App Store, will they be able to see my app? If so, what happens if they try to install the app?
Yes, it will in fact be visible to all iOS users. If the user tries to download the app, an error message will pop up stating:
This application requires iOS 5.0. You must update to iOS 5.0 in order to download and use this application.
I have updated my app in the apple store and I have put that it is available for iOS 5 and later.
Can I modify it and make it available to iOS 4 and later ?
If I reject the new app, can my users download the old one ?
thank for your response,
You can only have one app available (per name, per application id) for sale on the store at one time. The app store can't sell one app that works only with iOS 5 & newer (i.e. with Storyboards) AND an older one that works with iOS 4 & newer. So you need to decide which iOS versions you want to support and then submit your update.
Here's a related question that might offer some helpful hints for you:
Minimum iOS target version that Apple accepts in AppStore?
I've been using MKStoreKit to enable in-app purchases in my apps. The latest binary I submitted using this method was rejected because nothing happens when the user clicks on the purchase button when the reviewer tested it on iOS 5. Is this an iOS 5 issues, or has something else gone wonky? It works fine when I test it on iOS 4.
My iPod is too old to upgrade to iOS 5 and I've started saving up to buy a new one, but I'd like to get this app on the store before then. Also, it means that several of my other apps will be broken and I would like to fix those as well.
There is nothing special in MKStoreKit that could probably break on iOS 5. I've used it in many apps running iOS 4 and 5 without any issues. Can you test it on a real device and post what happens?