What happen if I remain to use old Xcode version? - xcode

I'm trying to understand, what will happen if one remains to use older Xcode version for developing, building and deploying.
I understand that each new Xcode version (...10,11,12) comes with new SDK support, improvements and features. I also have a great example of, we'll need the latest Xcode 12 to deploy our app to iOS 14 and above, since it won't work for Xcode 11 and below.
[Scenario ques]
However, what are the possible issues if one decided to continue in building and deploying their app with Xcode 11(SDK iOS13)?
Aside from not being able to test the app in a proper iOS 14 environment and risking of having bugs. Could the SDK version in Xcode11 and Xcode12 make any difference to the app?

You can certainly go on playing with Xcode 11 if that is what you feel like doing. But that's all you will be doing - playing. You won't be able to do anything with an app that you create that way. In particular, without Xcode 12, you cannot run the app on a device with iOS 14 on it, and you cannot submit the app to the App Store.
So when you say
use older Xcode version for developing, building and deploying
...you can just delete the word "deploying"; you won't be doing that (if the word "deploying" means what it usually means).
(And you cannot easily develop an app partly with Xcode 12 and partly with Xcode 11, as some of the things you do in Xcode 12 can make the project incompatible with Xcode 11.)

Related

Do I need Xcode 7 and Swift 2.0 to update my app

I have an UI issue in my Swift 1 (Xcode 6, iOS 7.1) app on devices running iOS9. I've tried to convert my app to Xcode 7 and Swift 2.0 but I'm running in a lot of issues here.
To give my customers a quick fix until I've figured out whats wrong I was wondering if I can download and install Xcode 6 (the version I build and uploaded the app last time) correct the UI issue (I know what to do) and upload the app again.
In a nutshell: Will Apple deny an app update with an old Xcode/Swift version?
The “Submit Your Apps” page currently (as of 2015-09-23) says
If your app still depends on Xcode 6, you'll need to keep a partition or external hard drive with OS X Yosemite installed in order to submit from Xcode 6.
This clearly implies that you can still submit apps with Xcode 6 (and therefore with the iOS 8 SDK).

am I safe to upgrade my cocos2d 2.1 game to XCode 6 to support iPhone 6?

I have been working on a game that is 95% done, and have been working in Snow Leopard with XCode 5.0.2, intentionally not upgrading to prevent any complications since I am so close. My other team mate got a new computer with mavericks and was using XCode 6, and so I attempted to upgrade XCode to 5.1.1--- when I did this, my entire project was full of errors and a disaster...
My question is, if I plan to release my game and have it tested on a new iPhone 6, do I need to install Mavericks + XCode? I absolutely do not want to go through the pain of upgrading my game to cocos2d 3.0, and I am afraid if I try to run a 2.1 game on the latest XCode its all going to blow up and not work (just as it did even with 5.1.1).........
In order to submit your App to the app store, you are going to have to submit it using at least Xcode 5.1.1

Xcode 4.4 - There was an internal API error

Hi I just upgraded to Mountain Lion. I created an empty Single View Application and run it. The first time it runs fine but the next runs will give me the "There was an internal API error" pop-up warning TWICE. It's the same with my other projects. They run okay once but gets this error the next runs. There was no warning or any specific warning message of any kind.
Any idea how to solve this?
Would really appreciate your help.
I have it working on iOS6 Beta 4!! This is what I did but other variations may also work:-
Install XCode 4.5 Developer Preview 4
Delete your app from the device
Run your app from Dev Preview 4
Delete your app again (not sure if you have to do this)
Return to XCode 4.4.1
Run your app, stop running, run again!!!
Of course you could continue developing in 4.5, but I prefer to wait.
Installing 4.5 Beta 4 installs updated device support. Once this is done once (possibly on any device) it should work fine. If you use the same device on a different machine you will have to again run it once from 4.5 Beta 4 before using your preferred version of Xcode (You do not need to delete the app from your device this time).
Edit: I am pretty sure that if you make a change to your core data you will need to run from 4.5 for the first time also.
Don't know if this helps, but I've deleted all files in ${HOME}/Library/Developer/Xcode/iOS DeviceSupport and it worked as a charm (Xcode 4.4.1, OSX 10.7)
I had this problem when I upgraded my device to Preview4 but had my MBP still running Xcode Preview3. Updating to Xcode Preview4 made the problem go away for me, no restarts necessary.
Deleting the app manually from the device/simulator will allow you to build and run successfully. A long term solution is to not use a Beta Xcode :)
Sounds crazy but you can also not use the Beta version of XCode 4.
However, you must keep it in your left hand to authorize your iPhone to compile with the non Beta version (don't ask me why, it works).
If you run your app with XCode 4.5 preview & IOS6 Beta 4, the second time you run your app on the device, you'll get the internal API error.
In theory, you cannot use XCode 4.4 to compile on your iOS6 Beta 4 iPhone.
But...
It seems that, if you launch XCode 4.5 Preview, connect your iPhone (so it is recognized), run the application on it (even if you get the error), quit XCode 4.5, launch XCode 4.4 and .. tadaaaa... your iPhone is now recognized as an authorized device to compile on...
And of course, XCode 4.4 doesn't generate the api error...
I have Xcode 5.0.2 and iPhone with iOS 7.0.6.
Every time when I launched my project on iPhone, I saw "There was an internal API error". And it was launched on simulator without any problems.
I did all the stuff that usually helps (like remove an app, clean, restart Xcode, restart a mac, etc.).
This problem went away only after I restored the iPhone. Sad but true.
I don't know so far, why it appeared.

Location services are not functional in iOS 4.3 simulator running on Mac OS 10.7 with Xcode 4.2

I have built an iOS app that leverages Core Location Framework. I have Xcode 4.2 installed and Lion and now Location services are not functional.
Anyone know if there is a patch or workaround for this? I basically stuck and can't test my app on the simulator.
The updated location services in the iOS Simulator are not available to the general public as of yet. If you have access to the iOS Developer Program, you can download the latest beta of XCode, 4.2, and test that way.
As a warning, the beta is just that, a beta. You may end up with more testing issues that are completely unrelated to your location services.
Best case scenario is 2 machines, one for each. That isn't always feasible, so you'll have to decide which is more important. Good luck.
Testing on the device would definitely be a good work around. You will want to test on a real device to check Xcode 4.2 is still in Beta, so this might be a bug in this latest version. According to the documentation it is supposed give you the latitude and longitude of the Apple headquarters as a default.
iOS Simulator notes

Very confused about XCode 4 (after upgrading from 3.x)

My world was perfect when I had XCode version 3.x (3.1 or 3.2?).
Then one day, after upgrading my iPhone device to ios 4, i tried to deploy an app to my device. For some reason I thought that i needed XCode 4 (or SDK 4) in order to deploy directly to an ios 4.0 device (via xcode) because it was giving me an error(s) i've never seen before that seemed it was suggesting I upgrade XCode/SDK.
So now i have XCode 4.0 installed (build 4A304a) and am in a situation where I can't build my code, things are breaking left and right, and on top of it all I have to learn XCode all over again!!
Now here are my questions:
A) Do I need XCode 4 (and/or SDK 4) in order to deploy directly to an ios 4 device?
B) Do I have the right version of XCode?
C) I think there is a new Xcode version out, 4.02 or something. Should I get that right away?
D) Every time I download a new XCode, does it install "next" to the previous XCode versions? (it is a completely new XCode installation or does it upgrade any existing versions?)
Taking your questions in order:
A) Do I need XCode 4 (and/or SDK 4) in
order to deploy directly to an ios 4
device?
No, you can happily use Xcode 3.x to deploy to an iOS 4.x device. That said, if you want to develop using SDK features that are only present in SDK 4.3 or greater, you'll need to use Xcode 4.x as Xcode 3.x is only available as a package with version 4.2 of the SDK.
B) Do I have the right version of
XCode?
Being realistic, you'll need to move to using Xcode 4.x at some point, so you might as well bite the bullet now and get used to the new environment. Whilst it might take a while, it's worth the transition. (IMHO.) :-)
C) I think there is a new Xcode
version out, 4.02 or something. Should
I get that right away?
As Xcode 4.x is still fairly new they're patching it quite frequently. As such, if bandwidth isn't an issue, you might as well stay on top of Xcode releases. That said, unless you encounter a bug that's specific to a release, there's no requirement for you to do this.
D) Every time I download a new XCode,
does it install "next" to the previous
XCode versions? (it is a completely
new XCode installation or does it
upgrade any existing versions?)
By default Xcode will install over any existing versions. However, you can select a different destination during the install process if you want to run multiple versions in parallel.
Upgrading to Xcode 4 is indeed disruptive, luckily Apple doesn't do that too often. My experience with Apple technology is that you better go with the latest.
Personally: It took me 3 weeks to become break even in productivity. Now I'm more productive.
A: dunno, probably
B: yes
C: yes
D: in apple's tradition: it overwrites

Resources