My app has been rejected because apparently its design slightly breaks on an iPad (a label overlaps something else due to the weird resolution)...
After clarifying that the app has only 'iPhone' selected in XCode (rather than Universal) I still received the following message.
Thank you for your response and your effort to resolve this issue.
Even if your app was developed specifically for iPhone, users should
still be able to use your app on iPad.
I don't understand the rational here, since:
This is an app update, the currently live-published version has the same issue on iPad.. but
It can't be downloaded on iPad anyway (doesn't appear in the store - probably because its not specified as a 'Universal' app)
The smallest physical iPhone that the app will run on (by virtue of it's target iOS version) is the iPhone 5, which it runs perfectly on.
How can I resolve this issue without doing a heap of work to support devices which we don't support and which can't get the app anyway?
Related
I developed an app that only runs on iPhone (iPad compatibility not required yet by me). After I publish it to the app store, the apple rejects the app as they test it on iPad and as I mention that it is only iPhone app, therefore, it looks ugly on iPad.
How could I submit it to app store by force apply the setting that it is an iPhone app only, not iPad?
This creates really much issue as I worked a lot and seeing this rejection made my heartbreak.
Apple have stated in their app-store guide lines that iPhone apps should run on iPad. Unless there is some really special need otherwise, which you must be able reason with them.
Check here: https://developer.apple.com/app-store/review/guidelines/
In addition to that it is really easy to make iPhone application compatible in most of the cases, just try and run it once on iPad device( or simulator), and you might find the crash and be able to fix that easy.
I got an app that is used throughout the day for collecting signatures. The current release is used by my customers without problems for months on a daily basis. But recently, some customers who updated their iPads (iPad 4 Retina in that case) to iOS 9.1 reported that the app is unresponsive when they start to use it after a night of charging the iPad on a Mac. It takes several seconds to respond to a touch in a list with just a few menu items and signing is not possible at all since the touch events are recognized only every few seconds. The app does not crash until the user gets annoyed enough and forces it to close.
The app is usually the only one used on the iPads. It is used heavily during the day and the iPads are not used at all during night (just charged).
I cannot duplicate the issue on my iPads or in the simulator. I don't see any leaks on Instruments or other problems in the debugger.
The app is build for iOS 5.1.1 and newer (so that it can be used on the original iPad). The App Store version is build with Xcode 6, a beta version, which shows the same behavior (at the customer), with Xcode 7.1. I use Core Data for local storage and CocoaAsyncSocket for communication with the server.
Sorry for being so vague, but does anybody have an idea where to look at?
This problem vanished after Apple updated iOS to 9.2.x, but I don't remember the exact version.
We have an app on AppStore for almost 3 years, and we've set Deployment Device Info of this app as "iPhone" (not "Universal").
Earlier it seems iPad users could download our app and used it by enlarging the screen.
Now our uses reported they cannot download our app. (The guy who reported uses iPad Air + iOS7.1.1)
So, my first question is..
Is this new AppStore regulation that does't allow iPad users to download apps with "iPhone" set as deployment device target ?
We are fine if it's the regulation, but more confusing is when seeing the app in AppStore with Mac, we still see our app is compatible with iPads.
So my second question is..
From what info AppStore shows this compatibility information ?
Our aim is not to confuse users, so we want to go either way - tell users we are completely unsupporting iPads, or tell them you can download the app anyway.
That device list suggests that you require cellular access. Does the user in question have a wifi only iPad? The dialogue would be shown if the app required capabilities that the device did not have.
There is no change to the App Store policy - iPad users can still download iPhone apps, and it's pretty clear in the store that you're not getting an iPad-native version.
To answer your second question, the information shown in the App Store comes from what is set in your info plist- the minimum targeted version of iOS, and then device capabilities. Device capabilities are explained here.
I'm a beginner programmer and I have a universal application that works perfectly on iPhone and iPad with IOS 6.0 and up. However, it has certain features which cannot run on an iPad 1 because this device can only upgrade up to IOS 5.1.1. Whenever I run on an iPad 5.1 simulator, the application crashes. This is not the problem since I already expect it to do that.
Will Apple reject my application since it does not run on the iPad 1? Are there other iPad applications that leave out iPad 1's?
Of course not! Obviously, Apple thinks iPad 1 owners should just buy new iPads. :)
BTW, you should check out Apple's page on the approval process
, especially their approval guidelines for information on what they are looking for in an app submission.
No, they will not. So long as your app is supported on the latest iOS version, they will not reject your app for not supporting older devices. If your app has additional hardware requirements that the latest OS does not, be sure to clearly specify this in your app description.
Okay, I made a pretty simple iPhone app, I tested it with the iOS 5 and iOS 6 simulators for both iPhone and iPad, and everything worked fine! But when I submitted it for review, they rejected it because it crashes on the iPhone 4, and iPad 3, Is there a way I can figure out how to fix this without buying an iPhone 5 and an iPad 3? They did send me the crash files, but I have no clue how to read them. Any suggested is appreciated! :)
You don't. The Simulators are not accurate enough to debug certain problems (the Simulators only run x86 code, not the actual ARM code in the more constrained environment a device presents).
So, you may need to buy, beg or borrow a suitable iOS device or two for testing.
You have to learn how to read the crash files. Try dragging them into the organizer to start with.
There are some aspects that are different on the devices, you should have at least one iOS device of some kind to test on. An iPad is a good choice as you can test both iPhone and iPad apps. Running on any one device will shake out many errors that would happen on all of them - if for example, you didn't realize the iPhone file system was case sensitive but the Mac (and therefore the simulator) filesystem is not.
Even an older iPad 2 refurb would do for such testing...
It's very difficult to debug problems on a specific device without actually having that device. I know that there are some apple stores in my area that will rent devices for a short time for that purpose. You might check around and see if you can find one to borrow or rent for a day or two.