Today my Mac showed error message above for my own compiled app. This app worked for years. I slightly changed something, but what's the reason for this? How can I avoid it? There is no danger!
I'm using Xcode 10.15 and OSX 10.15.5.
It runs under XCode, but not standalone.
I found the reason/solution.
XCode may had a problem. I copied all files to another folder and restarted XCode with that new location. After compilation everything worked fine (as before).
Seems to be an internal problem of caches of XCode.
Use sign to run locall could fix this issue for me.
Related
Whenever I try and add any SpriteKit elements to my project, Xcode crashes. The files are created but not added to the project and if adding them manually, it still crashes when trying to open them. After some searching it looks as though previous versions have suffered with the same issue. I had the same issue with 8 beta 6 too.
Is there anything I can do to help with the issue? I can't find anything on the most up to date version so I'm guessing it's either something I'm doing or a problem with my setup.
I've the same issue when I try to maintain 2 Xcode versions in the same system, it is possible but you should install them into separate directories, for example Xcode_731 and Xcode_8 (my actual version is 8A218a GM, I haven't any crash).
This should be unuseful without crashes, but try also to free some memory (quit also simulator app after your crash), in your terminal:
sudo purge
When I run tests on my project in XCode, it builds, and then says Testing... which never ends.
When I use the stop button, the process stops with this text in the console:
*** If you believe this error represents a bug, please attach the log file at /Users/MY.NAME/Library/Developer/Xcode/DerivedData/APPNAME-gcsubmsjksdbljcswbefkgugjray/Logs/Test/C53D8988-3564-4C2B-A535-075D26D1E4A7/Session-APPNAMETests-2016-07-13_140704-t3DFd5.log
However, I am unable to run the tests again, and have to relaunch xcode to run them.
Is this an issue on XCode that may be known to the Apple developers?
EDIT
So, I figured, the simulator is not launching in time, and that fails the xcode to run the tests. It might be an installation bug with the simulator.
As I anticipated in my edit to the question the first time, XCode installation did not install the simulator correctly.
I trashed the old installed version and reinstalled XCode. And now everything works fine.
Thanks for all the help.
I found that the tests never ran if I was running anything other than iOS10 on the simulator, so use iOS 10. I guess backwards compatibility doesn't really matter.
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.
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).