LLDB crash

My phone just keeps crashing, screen turns off and the iphone just reboots himself. It happend now 6-7 times in 1,5 hours. I have a Iphone 15 Pro (IOS 18.0) what can i do?

I am seeing this crash (log at the bottom) after I am doing playing audio with AVAudioEngine. I know it might be related to the notification observer been released without calling removeObserver first. I have reviewed my code to make sure that removeObserver is called in the dealloc method. But to be sure, I have comment out adding all the observers that listens to any notification from the Audio engine but I am still getting this crash. It is much easier to reproduce if I use a bluetooth headphone. Any suggestions on how to debug this issue? I tried to printout the notification name with po $arg1 ($arg2, or $arg3) but I get this error on the console (lldb) po $arg1error: Couldn't materialize: couldn't read the value of register x0Errored out in Execute, couldn't PrepareToExecuteJITExpressionThread 4Queue : engine (serial)#0 0x000000019a4c1bd0 in objc_msgSend ()#1 0x0000000185e123a4 in +[NSConcreteNotification newTempNotificationWithName:object:userInfo:] ()#2 0x0000000185e122e0 in

Experience a hard crash that I can easily replicate when selecting a specific Navigation Link that is contained in a List on the Sidebar of my Navigation split view. I can replicate the crash with no issues, but I am unacle to identify the cause. What does this crash mean? How can I find the mine of code that is causing the crash? myDashboard 11-14-22, 3-25 PM 2.crash

i got crash 2023-02-15_17-41-50.0010_+0800-863b28cdcc74ab05fb2337bf3f8528df7318d377.crash

Hi,In iTunes Connect, if I navigate to the TestFlight tab, and look at the list of builds for my app, the latest build shows the number 4 in the Crashes column.However, if I select that build number in the Crashes tab of the Organizer window in Xcode, it says No Crashes.Also, if I click the build number in TestFlight to see the details of the build, there are no numbers (not even zeros) in the Crashes column.How should I interpret this information? Were there actually 4 crashes? If so, why didn't I get any crash reports?Thanks,Frank

Hi guys, My app gets many this kind of crash on iOS 15 recently. the exception type is EXC_CRASH (SIGKILL) but doesn't have the Termination Reason. I attached the crash log below. Does anyone have any ideas? Cheers. crash log

Hi all, Some of my end users are facing a crash at application start on iOS 15.0. Usually, I expect them to send crash logs (.crash format / .ips), so that I can symbolicate those files and check the root cause of the crash. This time, what they sent me is different to what I'm used to. It looks like a crash log but I don't find the real root trace linked to my app. I can see that the method abort() is called from CoreFoundation: exception : {codes:0x0000000000000000, 0x0000000000000000,rawCodes:[0,0],type:EXC_CRASH,signal:SIGABRT}, asi : {CoreFoundation:[],libsystem_c.dylib:[abort() called],libc++abi.dylib:[]}, And below it, a lastExceptionBacktrace: lastExceptionBacktrace : [{imageOffset:626780,imageIndex:5},{imageOffset:89940,imageIndex:4},{imageOffset:394752,imageIndex:9},{imageOffset:491384....} MyBeautifulApp-2021-10-15-144552.txt Not sure if this is a crash caused by my app?

I am getting this crash log, where crash is happening from iosCreateNamedProperties. I have attached image of crash log. What could be the reason and how to solve it.

Hi,My app is in Test Flight release at this time.In iTunes Connect, under Testflight Builds, several of the releases show a nonzero number of crash reports.However, I'm unable to access any of these crash reports in Xcode. When I select one of the builds that should have crash reports, the Organizer window says No Crashes.Why is this happening? Is there a way to access the crash reports directly through iTunes Connect?Frank

Hi there, I already filed radar FB9958917 two weeks ago and no response. this is super annoying when you are debuging a giant app and suddenly you switch the input source, and all debug work is gone and I have to kill xcode to start over again. unacceptable, only happens after you upgrade to 13.3

In TestFlight crash reports, all I see is the stack trace. Is there any other information hidden in there, such as the specific signal (etc) that caused the app to terminate? Thanks.

Recently received quite a number of crashes, and notice from the crash log it seems related to CFNetwork. In the crashed thread's stack trace, I do not see any of my application code involved. GA.crash