I've just updated to XCode 8, I'm working with a old project ( probably created in XCode 6 or earlier ) the problem is (even in the simulator) XCode get stuck for at least half or one minute in the step signing product.
With XCode 7 the launch the app in the device was really fast, and there was not any Signing product phase.
Is there any way to make this process faster?
Because XCode includes the new feauture to help you to manage signatures and I tried to deactivate this in: Automatically manage signing. I still have the same problem.
I also tried with XCode 8.1 Beta
Any idea?
Thanks
Related
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).
I've been using essentially the same set of schemes for my app for several years with no problem. When selecting a scheme to build, for each simulator device there would be a choice of iOS reflecting what simulators were installed.
Trying to solve a problem, I deleted Derived Data per some suggestions here. Today, when I select a scheme to build, I get this:
This is not helpful! I cannot figure out how to get back to the Target/Scheme combinations I had before. Any and all help will be appreciated!
yes i got this when I installed Xcode 7 beta.
Went away when I downloaded XCode 7 from the mac app store.
But I had to run Xcode 6.4 to test swift 1.2 code and was fine for a while till i rang two simulators at once.
Then in Xcode 7 they all appeared again
I had also downloaded the 8.4 simulator in Xcode 7 today so this may also have caused it.
I believe both simulators were sharing this folder so they got merged:
/Users/gbxc/Library/Developer/CoreSimulator/Devices
/Users/gbxc/Library/Developer/CoreSimulator/Devices/device_set.plist
raised q:
https://stackoverflow.com/questions/32742962/xcode-devices-list-showing-50-devices
I tried to specify in the title so people didn't think i was a dullard, I've used every version of Xcode 6 Beta alongside Xcode 5.1.1, but as I have only one dev machine I don't want to install Xcode 6 if it will overwrite Xcode 5 entirely.
I also realize I can download/reinstall Xcode 5 but I'm swamped at work and can't afford 30 minutes of downtime even, thanks for the help all!
Foolishly I let App Store update Xcode 5.1 and it upgraded me to 6.
Renamed /Applications/Xcode to Xcode 6
Downloaded Xcode 5.1 from https://developer.apple.com/downloads/index.action?name=Xcode%205
Installed Xcode 5 from the DMG into /Applications
Start Xcode 5, rebuild my project and ran my app on my iOS 6.1 device OK.
Downloaded iOS6.1 Simulator (Prefences>Downloads)
Ran my app in the iOS6.1 Simulator OK.
Started Xcode 6, rebuild my project for my iOS6.1 device - reported signing error.
In Xcode 6, rebuild my project for iPhone 4s 7.1 - could not boot simulator
Conclusion:
I got Xcode 5 back doing what I needed but will need to do more work to play with Xcode 6.
So that people don't need to read comments to find the accepted answer:
Yes, MANY versions of Xcode can exist at the same time, in order to prevent overwriting find Xcode in the Finder (CMD+Clicking is one quick method) and rename (simply hit the return key while the app is highlighted) as you see fit. On my machine I have Xcode 5.1.1, Xcode 6.1 and usually whatever Beta Apple has available if I'm having any issues with an app.
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.
I have a serious ongoing issue with Xcode 4. I have been using Xcode 3 for years, and had everything set up perfectly. All my Build Configurations worked A-OK.
I updated to iOS 5 GM, and naturally I have to use Xcode 4 to submit my app to the Store or use TestFlight. I can't change my Build Configuration. I've tried making a new "Scheme" (which are stupid IMHO, when the old system worked 100%), and everytime I do, I set everything the same, I go "Product" > "Archive"....it works, and I share the IPA to my Desktop, to upload it to TestFlight, or I save it as a ZIP and send it to Application Loader.
IT NEVER WORKS. On TestFlight, my testers will install it, and immediately the application will crash. It won't even launch, no matter how I build the app, regardless of Scheme. It worked 100% and I have made ZERO changes since updating to Xcode 4.
Xcode 4 only works when I wish to "Debug" my app on my own device. It builds, installs and runs perfectly. Why won't it work on AdHoc or App Store?
PLEASE HELP! I'm ready to pull my hair out.
To answer this question, it was an absolutely STUPID issue!
I was checking the size of my Info.plist for any changes, and for some ridiculous reason only Apple can comprehend, updating to iOS 5 made that code obsolete. So the use of the code in my Release/AppStore/AdHoc builds was making it crash on launch. Once I commented the code out, everything is back working 100%.
Strange.
Even Apple Technical Support couldn't figure it out and they had my whole project to peruse. Apple REALLY need to improve their software when they change it. Not create a massive learning curve for their users and encourage code-cleanups if the SDK decides it doesn't like 4.3 code.