xCode 7 - dyld`dyld_fatal_error: - ios

When I was attempting to run my game (the code was generated by unity), I can get all the way to run the game in the simulator (for iPhone 5S - as thats the phone I have) but when I go to try and run it on my real iPhone, It will install, and then it will try to run, but I get a blank screen, and on my computer theres the error:
dyld`dyld_fatal_error:
-> 0x1200a5088 <+0>: brk #0x3
and beside the second line is:
Thread 1: EXC_BREAKPOINT (code=1, subcode=0x1200a5088)
The app will only open if xcode is trying to run it, but it will freeze, and if you just try click into the app on the actual phone it will quit out straight away.....
Anyone any ideas?

I just had this problem and resolved it by doing a hard clean (Cmd + Shift + Opt + K) and then re-building.

Try to go into Build settings -> Configuration -> Scripting Backend -> Mono2x (not IL2CPP)

Same problem occurred in Xcode 8. Found out that I am using a device of iOS 9. Same app run but no problem found in another iOS 10 device.
It seems that this occur when debugging only. The release app has no problem after installing via iTune.

Related

IOS 11 breaks (ionic) app

I recently updated my IOS to 11 beta 3, to make sure my ionic app would still work.
However it crashes almost right away with a black screen when I launch it.
I try to debug it with Xcode, however when I build to run it on my iPhone and catch the error, the "running on device" gets stuck on the following :
What can I do with this? I'm stuck with an app doomed to die once ios11 gets released, anyone could help?
The problem is normally caused due to wk web view plugin. Try removing the plugin and run again

EXC_BAD_ACCESS at lauch for EAGLContext renderbufferStorage: fromDrawable: in Cocos2d app whie debugging

Using default cocos2d-swift app I'm receiving the error EXC_BAD_ACCESS on my iPad Mini 2 at the line:
BOOL rb_status = [_context renderbufferStorage:GL_RENDERBUFFER fromDrawable:layer];
But if I try to launch the app without debug all works fine. If I use debug on any virtual device I receive no error too.
Why it doesn't work? How to remove this error?
Looks like this is an issue on certain devices on iOS 8.3+. It works for me on almost all devices but the iPad mini 2 fails for me as well. The short of it is that there's nothing wrong with the call itself. Seems to be an Xcode bug with those devices for some reason. You can get around it (until Apple fixes it) by:
In Xcode, go to Product -> Scheme -> Edit Scheme ...
And for the Run Debug configuration (on left side) choose "Options" (on right side) and configure "GPU Frame Capture" as Disabled.
For more information, check out this thread:
https://github.com/BradLarson/GPUImage/issues/2022#issuecomment-118943746
I found the device hadn't got the last iOS version. When I updated the iOS version of the devices the error has removed.

Swift App Opens on Simulator But Not on Device

I've been working on my iOS app for a while, and it builds and runs fine on the simulator, but when I try to run it on my device, a few things happen:
The app launch screen appears
The app crashes and my Xcode output is as follows:
dyld: Library not loaded: #rpath/libswiftCore.dylib
Referenced from:/private/var/mobile/Containers/Bundle/Application/18932CDB-57DA-4A87-B154-45B9F3CD01D0/Up & Down - Minimalistic, Beautiful Counter.app/Up & Down - Minimalistic, Beautiful Counter
Reason: no suitable image found. Did find:
/private/var/mobile/Containers/Bundle/Application/18932CDB-57DA-4A87-B154-45B9F3CD01D0/Up & Down - Minimalistic, Beautiful Counter.app/Frameworks/libswiftCore.dylib: mmap() error 1 at address=0x100110000, size=0x0015C000 segment=__TEXT in Segment::map() mapping /private/var/mobile/Containers/Bundle/Application/18932CDB-57DA-4A87-B154-45B9F3CD01D0/Up & Down - Minimalistic, Beautiful Counter.app/Frameworks/libswiftCore.dylib
(lldb)
The following message also appears, with a few other similar errors:
dyld`dyld_fatal_error: Thread 1: EXC_BREAKPOINT (code=1,subcode=0x1200f5088)
-> 0x1200f5088 <+0>: brk #0x3
So I don't waste your time, I would like to warn you that I have tried to clean and build, revoke and renew certificates, delete all breakpoints, and restart both Xcode and my iPhone.
Any ideas on how to make my app run on my device? Thanks!!!
My project has Cocapods and I'm using multiple schemes. Running pod update fixed something wrong that happened during a merge and now it runs fine.

App crashes without reason with xCode 4

Something weird is going on here.
My app crashes on this line of code:
int end = NSMaxRange(endRange);
but I don't get any error message, and everything is fine: endRange. The app just freezes in the iPhone and that's it.
1.
The weird thing is that the same code was working before, and I've reversed from repository to see what's wrong but it still doesn't work.
2.
Also xCode removes the breakpoint every time the app crashes. I add it again, I run the app, I step over, the app crashes and Xcode removes the breakpoint.
3.
I've cleaned the build, restarted xCode, restarted the iPhone, removed the app from the iPhone. Same issues.
4.
If I don't use breakpoints, the app doesn't crash, but the code right after that line is "skipped", but it was working before. At least the app doesn't freeze without breakpoint.
What the hell ?
I've had similar problems with the debugger in the past too. Try switching from LLDB back to GDB (From the Product / Edit Scheme menu). I've found LLDB to do exactly what you are describing with breakpoints.

xcode instrument problem

i try to use intrument application from xcode to find out about some leaks in my app, i can use it when i running my app on simulator, but the problem is, when i try to use instrument on running my app on device, it give me warning like this
target failed to run : remote exception encountered : 'Executable 'MyApp' ' is already running as process 97 which was lauched from the 'Xcode Debugger' process
is it something wrong?? i dont know what wrong step i made before, can somebody help me??
thank you
this seems that your app is already running in your device and you are trying to run it again with instrument, try to close your app completely from device and then start it again with instrument.

Resources