I am using default snapshotView(afterScreenUpdates: false) in my app and it crashes on Mac Mini with M1 chip (Thread 1: EXC_BAD_ACCESS (code=1, address=0x20)
Also, I got the same crash with drawViewHierarchyInRect and all of this graphics/UI methods.
Any ideas what's wrong and how to fix it?
We also had this crash, suspected it had something to do with using a Metal layer in our app. Couldn't figure out the exact cause, but the issue seems to be resolved in macOS Monterey.
Related
So I have a number of apps that were working fine. Just recently I tried some of them out on an earlier iOS (13.5) in the simulator and they ALL crash when I load the advert (interstitial.load or banner.load). They were ALL working on earlier simulators previously (some of them are a few years old so iOS 14 didn't even exist).
The error is:
Thread 1: EXC_BREAKPOINT (code=EXC_I386_BPT, subcode=0x0)
I don't understand what this means but there is no other context so Ive been struggling to understand what the issue is. It always stops at the .load line.
I am using app tracking transparency but have tried removing it and still get the same behaviour.
Has anyone else experienced this??
I don't know if its on real devices or just the simulators...(I don't have a real device with an old iOS to test it on).
Ive a feeling it might be to do with all the new privacy stuff that's flying around.
Thanks for any help.
I am getting crash on iOS13 devices with a following crash log
Crashed: BSXPCCnx:com.apple.frontboard.systemappservices (BSCnx:client:com.apple.frontboard.workspace-service)
EXC_BAD_ACCESS 0x0000000104a1c458
App has Firebase, Facebook and Realm SDK which uses NSClassFromString. 96% crashes have occurred when app is in the background state.
We used NSFileProtectionComplete for data protection
One solution suggested on Apple Forum is, if NSFileProtectionComplete in entitlements, use NSFileProtectionCompleteUntilFirstUserAuthentication, then locking specific directories with NSFileProtectionComplete. But not sure this solution will work or not as not able to reproduce the crash. Any help will be really appreciated
With iOS 13.2 beta 3, the crash is not reproducible with above-mentioned step. Looks like the issue was from Apple and they have taken care in 13.2 release
I just have device UDID & client reported that the app is crashing
on his device & he is not able to start application.
The client device iOS version is 7.1.2
Also i am not having any crash report.(Asked for Crash Report)
Now referring
(iAd works on simulator but crash on device(ipad)):
I am assuming the reason behind this might be the library,
So will making iAD.framwork optional & handling codes related to this do the trick?
**Update:
Unfortunately the cause of the crash was -[__NSCFString containsString:]: unrecognized selector sent which was iOS version fault & not device fault. I got it resolved. sorry to iAd for blaming or trying to blame. Long live iAd. Thanks**
First of all - you need crash details. Without it, nobody help you.
Integrate any crash reporter SDK: Crashlytics or anything like this.
Crittercism SDK 4.3.7 is crashing in iOS 8.0 :
Getting error at com.apple.NSURLConnectionLoader after running application.
Can anybody have solution for this or need to wait for new version of SDK with fix for this bug.
Let's try doing this and see where it takes us.
Set NSZombieEnabled, MallocStackLogging, and guard malloc in the debugger. Then, when your App crashes, type this in the gdb console:
(gdb) info malloc-history 0x543216
Replace 0x543216 with the address of the object that caused the crash, and you will get a much more useful stack trace and it should help you pinpoint the exact line in your code that is causing the problem.
More can be read here: "Thread 6 com.apple.NSURLConnectionLoader: Program received signal: EXC_BAD_ACCESS"
FYI we'll be working on tying up any iOS8 related loose ends on the 17th.
Thanks for using Crittercism!
I have an app I'm developing where setting a breakpoint in Xcode while the app is running causes it to crash. At least I assume it is a crash. There is nothing in the console saying what happened. The app just terminates.
Note that the break point is not being hit, just the act of setting it causes this.
I've developed many apps and this is the first to act like this. Does anyone have any ideas what could be happening or how to figure this out? It is really slowing down my debugging.
I'm assuming you're using Xcode 4.x. Try going into your scheme's settings and switch to a different debugger (GDB if you have LLDB currently set, or vice versa).
If that doesn't work, we need more info:
which version of Xcode and iOS are you using?
does the problem occur in the Simulator or on your device, or both?
have you tried placing a breakpoint in different places in your code?
As far as I can tell, it's a debugger issue. So your app does not actually crash, it's the debug session that crashes which causes the app to terminate. You can observe a similar effect when you hit Stop in Xcode or disconnect your device while an app is attached to the debugger in Xcode.
Might be an issue with mismatching Xcode and iOS versions. Please provide more info about your environment to help diagnose the problem.