Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 5 years ago.
Improve this question
I'm developing an iOS app with two different targets. The first target is deployed to support iOS 5 and iOS 6, and the second target for iOS 7. Both targets have different user interfaces (different storyboards), but they have the same code. I have been searching the way to submit both targets for the same app, but I didn't find the answer. Does someone know how to do that?
Thanks.
You can't submit the same app twice for different iOS versions.
Since all apps submitted must support iOS 7 and be built with the iOS 7 SDK you will need to create one app. Thus you can not submit an iOS 5/6 only app.
You will need to create an app that support both iOS 5,6 and 7.
Addition to #rckoenes :
Both targets have different user interfaces (different storyboards)
For this, you need to switch storybaords accordingly, while the app about to gets launch.
You need to submit an app with a different bundle id.
You can have two info.plist in your xcodeproject, and link only one to each target
You cannot submit one ipa build with different targets having different version of deployment target in one app.
So in your case you have to load different storyboard based on iOS version.
You can find iOS version using below code and load respective storyboard in your app.
[[UIDevice currentDevice] systemVersion];
Related
This question already has an answer here:
When can we start submitting apps to the iOS App Store written using the Swift programming language? [closed]
(1 answer)
Closed 8 years ago.
I have tried a number of different methods and I am still not able to submit my app written in Swift (set to target iOS 7.0) for app store review and I just wanted to confirm that no one will be able to submit swift apps until Xcode 6 is officially released.
So has anyone been able to submit their Swift app?
No! No one has submitted their Swift app in the Store, because it's not officially released yet, as you yourself mentioned.
You can begin using Swift code immediately to implement new features in your app, or enhance existing ones. New Swift code co-exists along side your existing Objective-C files in the same project, making it easy to adopt. And when iOS 8 and OS X Yosemite are released this fall, you can submit your apps to the App Store and Mac App Store.
From http://developer.apple.com/swift
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 8 years ago.
Improve this question
i've rebuild a old app code for my company and after correct all the errors for the updated xcode5, when i launch the app on my devices it has a different appearance.
In specific the old one are in old iphone style and now, without make grafics change(i think), the theme in iOS7.
i'm sorry if the question is too simple but i'm very newbie in iphone develop
If you build your application with a pre-xcode 5 IDE then it will retain the iOS6 look and feel, even when you download the old version of your app that is on the app store to an iOS 7 running device.
However there are some UI Elements that you have zero control over such as the UIAlertViews and UIActionSheets these will appear with the iOS 7 look and feel no matter what you do.
Once you start building your applications though with xcode 5 and above your application will now start to use the look and feel of iOS 7 so as soon as you do a new build with xcode 5 and above your applications will look different even if you haven't changed anything.
Note that from the 1st of February 2014 all Apps submitted to the Apple Apps Store must be built using at least xcode 5 and must be optimized for iOS7. So if you want to provide anymore updates to the Apple App store you will need to optimize your application to use iOS7 properly. Here is the Apple iOS7 Human Interface Guidelines that you may want to read.
This question already has answers here:
How to detect which 3rd sdk use UDID?
(4 answers)
Closed 9 years ago.
I submitted an update for my app to itunesconnect to discover that one of my third party libraries is using UDID. It was not picked up when I first submitted the app and I have made no changes to my third party libraries since then. Is there a tool that I can use to discover which one is using it. I have looked manually through them, but found nothing...
try doing cmd+shift+f on the project and search for [[UIDevice currentDevice] uniqueIdentifier]
This question already has answers here:
What's the meaning of "App must be built for iOS devices with Retina display"
(3 answers)
Closed 9 years ago.
I've heard about and read some of the new regulations from Apple about submitting apps to app store.
Firstly, the new version of my app is nearly done and it supports the 4-inch screen now.
About the UDID regulation, I don't exactly know what it means and am not quite sure whether my app follows the rule, how should I check this?
And before I submit my app, what steps and setting should I do in my project? My last submitting was over 1 year ago with other's help, so I'm not confident in myself.
For example, how many icons do I need in my project? (currently I have icon.png, icon#2x.png, icon-small.png, appIcon-small#2x.png, icon-72.png, and icon-small-50.png).
I just want to be fully prepared to submit my app.
Thanks for any help!
Icon sizes are listed here:
http://developer.apple.com/library/ios/#documentation/userexperience/conceptual/mobilehig/IconsImages/IconsImages.html
The biggest shock for me, when submitting an app after a hiatus, was the 1024x1024 App Store icon. Who has artwork that big???
You will also need double-resolution screen shots for all device sizes (iPhone 4, iPhone 5, and iPad).
My book has a pretty good checklist of the things you'll need as part of your final preparations before submission:
http://www.apeth.com/iOSBook/ch09.html#_final_app_preparations
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
Recently, my first iPhone app is approved. I decided to convert it to a universal app, and since it is a basic application I did it easily. I'll resubmit the app today, but I have some concerns about the process.
Idea 1) Creating a new application on itunesconnect. However, current users of my app won't get update notification and there will be 2 different applications. So this idea sounds really stupid
Idea 2) Creating a new version of my current application, this looks good for iPhone side of the app. However, I don't have any iPad app. Defining a new version for a non-existing iPad app sounds weird.
Please correct me if I'm wrong. As I know, one have to debug app on a real device to submit .app file. In my case - universal application, do I have to test app on both iPhone and iPad ?
I really don't know what I should do about it. Please share your ideas. Thanks in advance.
Ideally you should test your universal on both an iPhone and an iPad. If you don't own an iPad but just an iPhone, then if it works well on the iPhone and on the iPad simulator, then you should be OK. But it is still possible for there to be hidden issues. One issue you can have by not testing on a real iPad is making sure all of you iPad specific images and xib files actually work on a real device due to filename case sensitivity. But you can only test on devices that you actually have.
There is no requirement that you test on any device before you can submit the app. Apple has no way to know whether you did or not. Of course it is a really bad idea to only use the simulator for testing since there are so many differences.
As for submitting the app, you must use idea 2. Create an update to your existing app in iTunes Connect. Submit the binary. It will be detected as a universal app. Then you can update the meta data with new iPhone screen shots and iPad screen shots.