How does one (re)install xcode? - ios

I made the mistake of upgrading xcode and its been painful.
I'm at my wits end trying to satisfy apples demand of "Rebuilding my app using the current public (GM) version of Xcode and resubmitting it."
some details Xcode 7.0.1 - Invalid Swift Support - cocoapods HOW TO FIX?
As far as I know I'm using the current public (GM). I'm using version 7.0.1 (7A1001), please someone tell me if thats not the current public (GM).
I've tried just about every "solution" here, the error still persists.
Now I'm down to reinstalling xcode as a last grasp.
Of course this process is cloaked in mystery, how do you go about "reinstalling" xcode? I've heard that xcode has a "large footprint" so it's just not a matter of trashing the app, is it?

Yes, it is just a matter of trashing the app and re-installing the older app.
Delete the Xcode, empty the trash. Make sure you get all copies, even ones outside the Applications folder.
Either get a fresh versio from the Apple app store or get an older version from the downloads.
To get the older version 6.4 from: https://developer.apple.com/downloads/ You will need to sign-in with your developer id.

Related

How to install previous version of an ios app?

I've developed an ios app, but now I got some crash reports which says that the app is crashing only when updated from a previous version and it goes away when uninstalling and then reinstalling that app altogether.
So I decided to reproduce the crash by going back to the older version doing some stuff and then updating it back to the latest build.
The thing is reverting back to an old commit for a switching back to the older version of the app is causing quite a lot of issues and errors which I'm unable to resolve as of now. So is there any way besides this to install the older version of the app.
I'm using Xcode 8 and Swift 4, while the previous version was built on Swift 2.3 and an older Xcode, my Testflight app only has the latest builds while there is nothing backed up on iTunes too.
The thing is reverting back to an old commit for a switching back to the older version of the app is causing quite a lot of issues and errors which I'm unable to resolve as of now
Ah, but that's not how to do it. What you want to do is not recompile the old version from source; you want the already compiled old version as an actual app. That is exactly what the archive is for! The reason we keep archives is so as to have the exact same already compiled code that has been distributed thru the store.
So just go to the Organizer window, find your old archive, and export it as an Ad Hoc build. Now you can install that on your device through the Devices window, play around with it, and then install the new version on top of it and run that and (one hopes) reproduce the problem.
A crash like this is almost always caused by data that is no longer compatible from the first version of the app.
If you don't have access to the compiled binary and don't have a way to re-install it, then your best bet is to install an old version of Xcode to install the old version of the app, and then use the new version of Xcode to install the new version of the app over it.
You may run into issues with the old version of Xcode not supporting your newer iOS version on your device. In that case, use the old version of Xcode to install the app to the simulator. Then in Xcode you open Window -> Devices and Simulators. You can download the sandbox folder for your app from the device and then copy over the exact files to a device with the new version of the app. Then when you run the new app you should be able to reproduce the issue.

Xcode 8.3.3 to Xcode 9.0 update

I have recently installed Xcode 9.0, but in order to also keep the previous version (i.e. both Xcode 8.3.3 and Xcode 9.0) available on my computer, instead of using the usual App Store Updates I have followed the instructions found here.
As much as I can see the result is pretty good.
Nevertheless the App Store application does not seem to understand that I am now up to date with Xcode 9.0.
It keeps showing me the update for it. What am I supposed to do about that? Any way to inform the App Store app?
The instructions you linked had you keep your old version and just install the standalone version of the new.
These instructions are bad. You've just found out why.
Throw away the standalone version of the new and go ahead and let the Mac App Store update your Xcode. Then download the old version from https://developer.apple.com/download/more/, rename it, and stick it in /Applications.
Also don't forget that while you can keep multiple versions of Xcode 9 open at the same time, this isn't true for older versions of Xcode. If you have Xcode 8.3 running, you can't have Xcode 9 running, and vice versa.

Can I delete entire developer folder under Library

I need to update my Xcode 8.2 to Xcode 9. I upgraded my OS to macOs High Sierra 10.13. Then I went to Mac App Store and tried downloading it and the update button keeps spinning for infinity. I searched google and stackoverflow and apparently this is a known bug going back ages. One of the solution suggested that I should delete Xcode application and then try the download/update button again in App Store.
See Here Unable to update to Xcode 8.3
So, if I am going to completely remove Xcode application from my computer then I was thinking I should cleanup my comp and remove unnecessary Xcode files that I don't need and they will be recreated upon a new install. These are huge folders and looks like related to my Xcode development activities. Can I safely delete them?
Can I delete the entire ~\library\Developer folder?
To answer my own question YES its completely safe to delete ~/Library/Developer folder if you plan to completely remove your existing Xcode and install a new version. Actually its highly recommended you do so. Everything worked and all projects compile.
The newly created one was only 772MB. Come on Apple! What a waste of space that was.
MacBookPro2012:Library$ du -sh Developer
722M Developer

ITunesConnect rejecting build even though I'm on normal Xcode version

I'm getting the following error and don't understand why I am getting it. I'm running Xcode 7.2.1 which is the normal released version and was able to upload builds earlier this week with this same Xcode version so this error makes no sense. Has anyone else encountered it or figured a way to get rid of it? I've tried the following:
Restarted Xcode
Deleted Derived Data
Restarted Computer
Ran Build Clean
Ran Build Folder Clean
Incremented versions on the build.
Any other ideas on how to fix this?
I've figured out what was wrong with it, and it is definitely my fault. As stated in the error message:
Don't submit apps with Beta software including OS X builds
Xcode was on the correct version but my OSX had auto updated the night prior to this appearing, and put my entire system on a beta. There is no easy way to revert if you didn't do a time-machine save prior to updating (mine happened automatically, so I definitely didn't). Now I'm stuck building on my back-up mac until Apple releases 10.21.4 publicly.
Thanks for the help, lesson learned. Don't register for any beta software unless you have Time Machine setup to automatically backup your machine.
UPDATE
Reinstalling your OS when you are on BETA is actually quite easy.
Go to the Mac App Store
Search for "OS X El Capitan" or whatever OS you need
Hit the Download button
Now you can reinstall your OS. Stupid easy.

Unable to patch projects with Jailcoder

I'd want to do some tests of an iOS app I'm developing concerning jailbroken devices, so I patched an Xcode. Since JailCoder seems to haven't been updated since quite time ago, I'm testing on an older Xcode version (4.6.2), that seems to be successfully patched. However, when I try to patch the project, JailCoder interface says 'Error'. Is somebody experiencing the same?
Thanks
Try on xCode 4.6.3 with JailCoder 1.2.1. You also need to have AppSync installed on your iDevice in order to install apps from xCode (with JailCoder). There might be an issue with code signing (if you are experiencing any errors there), in case the xCode Patch didn't work properly. Lastly, make sure to follow anything the developers suggest. Working perfectly on my Mac at the moment with the version mentioned above.

Resources