I tried running my project in Xcode Version 6.0 (6A313) and received Error creating LLDB target at path '/path' - using an empty LLDB target which can cause slow memory reads from remote devices. But it runs perfectly on xcode 5.1. I think the problem with architecture of iOS 8. Is this is a serious problem i should take care of ? Anyone help me with some suggestions.
Related
In one of my app I am facing this issue in Xcode 9.2. I have created my project in Xcode 8.3 and when I am running in Xcode 9.2 it shows me error like
Failed to find device type for System content for
IBCocoaTouchFramework-ElevenAndLater
scaleFactor=2x
Failure Reason: Could not find a suitable device type for the idiom
I am using Xcode 9.2 (Version 9.2 (9C40b)).I am not able to identify
problem.
It gives me error in assist catalog Any one have any idea ??
Hope this gets you well
Try to clear your derived data.
Try to completely restart your computer after downloading the new Simulator runtimes within Xcode for things to start working correctly again.
cheers :)
Hi I'm a newbie when it come to app development, but I DID have an app working just fine until I upgraded to xcode 4.5. The app has not changed but I am now getting 'Build Failed' when trying to put the same app on the same iPad I have always used.
The error I am receiving is show here http://i1342.photobucket.com/albums/o763/designedbyria/ScreenShot2012-09-27at162319_zpsfea02141.png (I stupidly am not able to include images) - Apple Mach-O Linker Error, does anyone know how I can solve this? I really don't have a clue what's going on and it's important I get this app working asap!
Any and all help will be greatly appreciated! Thank you in advance…
If your app is for iPad only, just remove armv7s from valid architectures. You can also do this for iPhone apps, and it will run on all viable targets, although it will be missing armv7s, which is the CPU for iPhone 5 - armv7 code will still run.
Alternatively, you can find an upgraded version of the Cordova framework built with armv7s support; you should just be able to build it yourself.
The error is on the line above. A framework you are linking (Cordova.framework) does not contain a binary for the appropriate processor architecture (armv7s).
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'm currently migrating an old OS X project from Xcode 3 GCC to Xcode 4 LLVM.
The migration has so far gone fine. I've updated the code from 10.4 to 10.6, with a lot of deprecated API, and it all compiles just fine.
But when I try do debug using LLDB, I get the following error:
error: failed to launch '/Users/trenskow/Library/Developer/Xcode/DerivedData/The_Famous_Web_Editor-ddfqhzdztzzgfrcxaaywyxgtahzx/Build/Products/Debug/The Famous Web Editor.app/Contents/MacOS/The Famous Web Editor'
The application runs fine on it's own (besides the runtime errors I am trying to debug).
When I switch back to LLVM GCC and GDB, it launches fine, but Xcode never stops at the breakpoints. The application stops, but I do not get any indication of a breakpoint is being hit by Xcode.
Long shot, but:
The Famous Web Editor
Xcode and the compiler can sometimes trip over spaces in the project/target name. This usually shows up in broken header or library search paths, so I'm not sure if it applies here. But it's certainly worth a try to rename the target so it contains no spaces.
First clear your DerivedData (/Library/Developer/Xcode/DerivedData/) delete every thing from there.
Now restart your XCode, Restart your device.
run Xcode
I've got 2 applications using Core Data with a sqlite persistent store. I've got a data loader routine that I run to populate the CoreData DB from csv files. During development, when my data changes I run the routine from the simulator to generate new databases and copy the new one into the project.
This has been working quite well for XCode 3.2.3 and iOS 4.0. It even works in the XCode 4 Preview 2 and 3. I just installed the final version of XCode 3.2.4 and iOS 4.1. Now my db loader fails. It gives me no message, no warning, no nothing. It just dumps out to the spring board and XCode gives me the "Debugging Terminated" message. It will fail at different times during the load so I'm pretty sure it's not a data issue. I'm not doing any threading. I assume the issue has to do with either Core Data or sqlite, since that's when the crash occurs, but with no info reported I can't tell for sure.
I uninstalled everything. Xcode 3.2.4, Xcode 4 preview (assuming it was an issue caused by XCode 4) and reinstalled XCode 3.2.3/iOS 4.0. Things returned to normal. After getting some work done I attempted to upgrade to 3.2.4/iOS 4.1 again. I uninstalled 3.2.3/iOS 4.0, rebooted. Installed 3.2.4/iOS 4.1, rebooted and tried again. No luck. Same hard crash. Same lack of messaging as to the cause.
I have determined that this only happens with the Simulator with XCode 3.2.4, the device is fine as is XCode 4 and 3.2.3. I've tried playing with the target OS selection (3.0,3.1,4.0,4.1). I've tired adjusting the Compiler from GCC 4.0, GCC 4.2,LLVM GCC 4.2, LLVM 1.5. I've tried setting the Base SDK to iOS Simulator 4.1. Interestingly enough it will work in the iPad simulator when using the 3.2 SDK. So I've at least go that as a work around.
I guess there is one of 3 issues:
An issue with my code that has been uncovered by 3.2.4.
Bug in 3.2.4.
A configuration issue that I've missed.
If anybody has any troubleshooting ideas or answers I'd love to hear them. I've been doing iOS full time since V 2.1 and I am seriously stumped.
Thanks in advance,
I figured out my issue. It looks like the CoreData/Sqlite connection was a total red herring. Following a tip I read on SO, I used OSX's Console application and got a critical message "Failed to launch in time" that was not being displayed in XCode's debugger console.
It looks like the process was being killed due to what is essentially a timeout error. The iPhone will kill an application that takes too long to complete "didFinishLaunching." That's where I was kicking the data load routine off from. The new version of XCode must have adjusted it's timeout values.
So my takeaway is give OSX's console a shot if XCode isn't telling you everything and watch out for those red herrings.
When I upgraded I ran into troubles in the simulator when saving the managedObjectContext. I finally deleted my sqlite CoreData store file and have not run into similar problems. Try deleting your data file (well save a copy of it before deleting to see what is different).