i have snow leopard 10.6.3 installed via iAtkos..everything runs good even XCode as well.I can successfully build iPhone apps run them on the simulator and the device but when i use the "build and archive" option( for adhoc distribution or itunes connect ) XCode simply crashes..does anybody have a solution for this?
thanks in advance
btw XCode version 3.2.3(tried 3.2.3 as well same result,also in safe mode)
Mac OS X version 10.6.3
I had the exact same problem, and it turned out it was caused by a variable of wrong type in info.plist. My short bundle version was created as int instead of string.
I was getting the warnings about it, but it didn't seem relevant since the crash happened only when archiving, and normal building worked fine, the app ran fine. I suggest you check your benign looking warnings, one of them could fix the issue.
You might try 3.2.4 (available now).
Related
I just installed the latest version of Xcode (10.1) on MacOS 10.14 (Mojave).
I can build my application and it runs fine on my Mac or similar system.
However, I want to share this application with someone using MacOS 10.11 (El Capitan) and it fails to launch, asking for a minimum requirement of MacOS 10.13 (High Sierra).
My application is only very simple, can't I compile it to be compatible with older MacOS ?
After some research, I did download MacOSX10.11.sdk
(from https://github.com/phracker/MacOSX-SDKs/releases/).
I did decompress it, and drag it into:
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs
(This folder originally contains only "MacOSX.sdk" and a link pointing to it, named "MacOSX10.14.sdk")
I also noticed the value of the string "MinimumSDKVersion" from the file /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Info.plist is equal to "10.11", which sounds good in my case.
I read on some forums adding additional SDK versions into Xcode is not supported. And by the way, I cannot see any menu from Xcode to specify my target build (neither in Xcode Preferences, nor in the project settings (see picture below).
Where can I tell Xcode to use, let's say "MacOSX10.11.sdk" over "MacOSX10.14.sdk"?
And, is there a better way?
Or, do I have to install an old version of MacOS on a different partition, with an old version of Xcode (which would be a pain)?
I am not sure if this still works on Mojave, but there is a project called XcodeLegacy which is created specifically with this intention in mind:
https://github.com/devernay/xcodelegacy
Regarding the menu, you can find it at: Xcode -> Select File -> Project/Workspace Setting
Open Workspace Settings
Works on Xcode 13, I'm a bit late to the party but just had the very same question.
i recently received my Macbook and wanted to start developing iOS apps with it.
I Created a default Master-Detail App using the Templates in Xamarin.Studio and everything worked.
Now today i wanted to actually do something in the app, but didn't change a single line of code, still the app doesn't show up anymore in the simulator as long as i want it to use the 6.1 sdk for ios. if i use any other (6.0 etc) it works fine.
I already tried clearing my Cache in /Users/MYNAME/Library/Xamarin/ but this didn't change anything.
What would you suggest me to do now? can i simply reinstall the 6.1 sdk?if so, how would i do this?
Thanks for your help
I had a similar problem where the environment hang when I was trying to debug in the simulator (just showing the spinning ball). I found out that it only occured if I had my phone connected to the computer. Perhaps not valid in your case, but it might be a lead in your problem solving.
I'm using the latest version of everything. :)
From within Xamarin Studio (or MonoDevelop):
Project -> Your.Application.Name Options
Build -> iOS Build (iPhone Build in MonoDevelop)
SDK version: -> 6.1 (it's probably still on 6.0)
This fixed it for me. Also, it wouldn't hurt to make sure the target build in info.plist is set to 6.1.
Delete this folder:
/Users/[username]/Library/Application Support/iPhone Simulator/6.1
And if your Library folder is hidden:
sudo chflags nohidden ~/Library/
I have experienced this problem several times again and my previous answer doesn't solve it. Ya know what does? Rebooting the computer. Works every time. shrug
You need to fill the Application name, Identifier, Version # in the project setting.
I had the same problem and got it solved that way.
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.
Im using Xcode 4.4 on Mountain Lion OS X 10.8, to archive an iOS app however I keep receiving this error:
(null): There is no codesign_wrapper executable. Please reinstall the Xcode developer tools. (-19058)
Has anyone come across this problem or know how to solve it?
Thanks, Sami.
Do you need to install the command line tools via xcode?
they are located in the Preferences window's Downloads section and the Components tab.
In case anyone else comes across this as well...I was having trouble with this for hours while trying to submit the application with the Application Loader. Perhaps its a slightly different issue, since your getting this error while trying Archive, but for what its worthere this is/was my situation
. Using the "latest" Xcode 5.0.1 (past what I saw other threads saying - using 4.0.x), eventually installing Xcode 5.1 when released with the same error/issue. After upgrading, I believe I was still receiving the issue because I was still using the same (2.9) Application Loader from the first (5.0.1) Xcode. When I explicitly opened the new (2.9.1) Application Loader from (5.1) Xcode via Xcode --> Open Developer Tool --> Application Loader, the submittion process went futher. However failed for me for a different issue.
So it goes.
I've read every other thread on this and have tried everything but the "Build and Archive" function is determined not to be clicked.
I am running OSX 10.6.7 and Xcode 3.2.4. I am developing a MAC application and am trying to submit it to the Mac App Store, but to do this i need to run the Build and Archive feature, and I simply cannot figure out how to get it to run. I have heard about these "developer tools 1.1" from some other thread but cannot find those either. If you are about to say that that will fix things, then please link me, otherwise, any suggestions are greatly appreciated.
P.S. Yes im in Release Mode
Another answer could be that your active SDK should be set to Device not to simulator. You can find this setting in Project > Set Active SDK > Device.
Happy Coding..!
Figured it out... In order to Build and Archive with a Mac App (as opposed to iOS) you need Xcode 3.2.5 (maybe even 3.2.6) or better. So to all those with the same problem, make sure you are running the lasest version before trying ot Build and Archive.