Im so confuse and tired about my app compatibility
My problem is :
I got an app on Appstore . But my app compatibility is iOS 8.4 that so many people can't download my app. Almost people not often update their device so that their device is low version than iOS 8.4 What should i do now ?
Can i make my app compatibility down to older version ?
Or In Upload App Progress ,does somewhere i must be notice to choose the compatibility of my app ?
How to know about the app compatibility before archive app . I look up for many app in App Store they are iOS 7.0 or older . Why my app is up to iOS 8.4 ? So confuse
Best Regard
Maybe Deployment Target of your app is "8.4". If you set lower version (ex. 7.0), many users can download your app.
Related
I have an iphone app that was accepted in the App Store before the arrival of iOS 7. The app used to support both iOS 5 and iOS 6.
Now i have updated the same app to iOS 7 and about to submit it to the App Store for approval. I have a question that is making me confuse.
Question 1: Is there any way the first version of the app stays in the App Store for iOS 5 and iOS 6 users while the new version that i am going to submit only serves the iOS 7 users. In other words, i want to save some time but not updating the same app compatible with the old versions.
A user that has an iOS version prior to 7.0 and have previously downloaded you app, can still restore the old version from iCloud.
New users of your app can not download an old version.
This is the information Apple sent out regarding this:
"Users who have already purchased your app are now able to download previous versions, allowing them to use your app with older devices that may no longer be supported by the current version.
If you do not want previous versions of your app to be available, for example due to a usability or legal issue, you can manage their availability in the Rights and Pricing section of the Manage Your Apps module on iTunes Connect."
Yes, since a few weeks. If a customer downloads your app and it is not available for his device (e.g. the app is iOS 7 only and the customer has iOS 6) and there is a < iOS 7 supporting version uploaded earlier, it will download that one.
Source: Engadget
First off I am going to ask why?
Secondly the two answers already given are completely wrong.
Too yoeribovens answer this isn't true, Apple haven't confirmed this and it isn't documented anywhere in the Apple documentation. The best reply I have for that article is it is complete rubbish. Unless Apple have confirmed it, it isn't true.
To user1673099s answer this is also not a good why to go. This means two apps to maintain on the app store, so unless one is a LITE version and the other is a FULL version I just wouldn't go this way at all.
The one thing I am going to do which is the actual way you should be working if you want to support iOS 5, iOS 6 and iOS 7 is direct you to the Official Apple Documentation for Supporting iOS 6.
This guide will help you make the transition from iOS 6 to iOS 7 and it will also instructed you on how to completely support previous iOS versions.
You might also want to read iOS 7 UI Transition Guide Before You Start and iOS 7 UI Transition Guide Scoping Your Project
I ask same question on Apple Support Communities. It is possible. They replied this-
iOS 7 and OS X Mavericks include new features that many of your favorite apps take advantage of when you update them. Some of these features are specific to the latest versions of iOS and OS X. As a result, the latest versions of some apps may not work with your device or computer if you are still using an earlier version of iOS or OS X. Thanks to the App Store, you may still be able to re-download a compatible, earlier version of an app when you are using an older operating system.
Here's how you install an earlier version of an app:
Open the App Store (with iOS 4.3.3 or later) or Mac App Store (with OS X Mountain Lion).
Go to the Purchased screen (iOS) or Purchases tab (OS X).
Select the app you want to download.
If a compatible version of the app is available for your version of iOS or OS X, simply confirm that you want to download it. For example, after purchasing iPhoto for your iOS 7 device, you can install an earlier compatible version of iPhoto from your iOS 6 device.
Additional Information
Note: Some earlier versions of apps may not be downloadable from the App Store if the app's developer has chosen not to make them available. If you don't see the version of the app you are looking for, contact the app developer for more information. The developer's contact information can be found on the app's product page on the App Store.
You can also read it from here-
http://support.apple.com/kb/ht5919
You have to use the different BundleId for Ios 7 app & changed it deployment target to ios 7.0.
So, idea is that you are making two different apps.
ios<7.0
ios=7.0
May this helpful to you.
We're talking about making the minimum iOS version of our consumer facing app 5.0+. We have a few questions, and I was unable to find a great resource for the answers:
For existing users with 4.xx, when the next update is released, will they just not see the update in the App Store? IE, until they update their iOS version to our new minimum version, they will never see the most recent update and will be "stuck" on the previous version?
For new customers with 4.xx, when they search for our app on the App Store, will it show up in search results? If so, what will be displayed when they click Install ?
Thank you for your help. I found lots of information on specifically 3.xx to 4.xx, but wanted to get a more detailed explanation for the scenarios explained above. If there is Apple developer documentation for this, please point me in the right direction.:)
Thanks!
Yes.
If you specify the deployment target for your app as iOS 5.x, your customers running iOS 4.x won't see an update on the app store and will be stuck at the previous versions of your app.
New customers running iOS 4.x will be able to see the app but won't be able to install it. They'll get a system error message that iOS 5 is required to install this app.
Hope that helps.
The App store on the device will filter out apps and updates that are inappropriate for the current iOS device OS version. The user won't see them (or if they see them on some devices, won't be able to download or install them).
However, the iTunes App Store on the customer's Mac or PC will not filter by OS version. iTunes will download apps that the user can't install on their devices running older iOS versions, and, far worse, will put any working app versions in the trash after downloading their useless updates.
The App store does not filter apps based on the operating system of your device. It will show iOS 5 apps even if your device is iOS 4. The update will definitely appear in iTunes. I don't know about whether it shows up in the updates in the app itself.
I currently have an app in the app store that works for iPhone users running iOS version 3.0 or newer. My next version of the app is going to use ARC, so it will only work for users running iOS version 4.0 or newer.
According to this answer, the users will be able to download the newer version, but it just won't run when they try to run it.
Is there any way to prevent users who can't run the app from even downloading it from the AppStore?
I haven't tested this recently, but in February 2011, and iOS 4.x, I had users who couldn't download my app as there device wasn't running the required version of iOS.
They received a nice explanation message on their device, courtesy of the App Store app, when trying to download the app directly to their device.
I'd be very surprised if this wasn't still the case.
So, set the deployment target in your target build settings, and let the App Store / iTunes take care of who can install it.
That was for new installs, and it be different for updates (rather than new installs) but again I'd be surprised if this wasn't handled by Apple for the sake of a better user experience.
UPDATE
I dug out my old iPhone 3 which reached the end of the road at 4.2.1 and resynced it with iTunes - the latest apps that require 4.3 etc are ignored, and are not overwritten with incompatible versions, as I would expect.
I also tried to update my own app (I'm a developer), requiring 4.3 and above, from the store via the device itself, and got a polite pop-up alert saying the app requires iOS 4.3 and above, again just as I'd expect.
The app was previously compatible with < 4.3, and somewhere along the line I bumped up the minimum iOS version requirement, so it is definitely possible.
So, you should just set your updated app's 'deployment target' version appropriately, and it will only be updated on compatible devices.
No. A new higher minimum Deployment target will prevent a user from installing an app on a device with a lower OS version, but will not prevent them from downloading the app using iTunes on their Mac or PC, even though they can't install the update once downloaded.
I am just about to upload my first app to appstore :-)
I have tested the app on an iPhone 3G (IOS 4.2) and my iPhone 4. What version of code should i upload and:
If i upload 4.2 to support iPhone 3G, will that cause any problems with newer phones?
If i upload the latest version of the code i guess iPhone 3G's will not be able to run it?
Is it worth while to still support iPhone 3G?
Can someone please recommend me what to do?
If you upload a version that the 3G does not support, then all 3G users will not be able to download the app.
If you upload a version that is supported by 3G, then only if the users have updated their firmware will be able to use the app.
In other words, the role of thumb is: upload the one that is tested on the latest firmware, but can be launched from as many firmware version as possible.
That might mean to just upload the one that is tested on the least firmware possible, but be careful because newer firmware versions might stop supporting certain APIs that you might have used, and then all newer (potential) customers will be locked out of your app.
If i upload 4.2 to support iPhone 3G, will that cause any problems with newer phones?
No.
If i upload the latest version of the code i guess iPhone 3G's will not be able to run it?
You need to compile for arm6 in addition to arm7 architecture.
Is it worth while to still support iPhone 3G?
That's a matter of opinion. This there any requirement for you specific app that requires a iPhone 3GS?
Choosing the latest ios as the deployment version is bad idea. iOS 4.3 isn't supported by Verizon devices, which means that you will lose a big portion of US users.
I believe most of apple's apps are using "iOS 3.1" as the deployment version, and i would recommend choosing the this as the lowest supported version.
iOS 3.1 is the last version supported by the original iphone, which guarantees that all users can use your app. Note it's not enougth to just pick 3.1 as the deployment version. you will have to test it with a REAL 3.1 firmware. There are a few guides on downgrading your iphone to 3.1, which is helpful for testing (such as http://lifehacker.com/5572003/how-to-downgrade-your-iphone-3g%5Bs%5D-from-ios-4-to-ios-313)
Let's say we have an application with a deployment target set to 3.0 and we want to raise the deployment target to 3.2. Normally, the App Store won't let the App be installed on devices with an IOS version less then this, but what about devices which already had the App installed prior to the update? Will they see the update but won't be able to install, will they just not see the update or, heavens forbid, will be able to install and the app just won't start?
I searched everywhere for this, but I can't find anything about raising the minimum OS version for an app update.
Thanks!
From my experience those updates just won't show up as available.
When I upgraded OS on my device from 3.1 to 4.1 about 10 available updates appeared immediately in App store app - so that should be the actual behavior.
In addition to only showing supported updates, the store now offers the "last compatible version". This lets people download an app even if their device doesn't support the most recent version. Unfortunately this means that some people could still download an older version with bugs you have already fixed. There may be a way to disable this, but none of my app updates have introduced new requirements, so I can not test.
It's nearly a safe bet that they won't be allowed to install it. A similar situation is iPad apps or Mac apps which won't display in the App Store on iPhones and iPods.
I say nearly because the updates should not appear to older users on their iOS devices. The risk, however, is when users sync with iTunes, or if they update with another device. The new version of the app is now associated with their account, and will ruin the install on the older device if they try to sync it with iTunes.