Hello, I have an App on the App Store, and today, while inspecting the App analytics on the App Store portal, I've noticed that there had been 8 crashes on the App on January 15th. I went to Firebase Crashlytics, since I used to also see the crashes on the App, and it says that there are no crashes. Then I went to Xcode to see the details of the crash, and I found this: What does this crash mean? I have no idea whatsoever. I tested the App several times, and it works perfectly. I have absolutely no idea of what this crash is. Could someone give some hints on what this crash could possibly be? Thanks.
Search results for
LLDB crash
29,562 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
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
Hi, We've develop and publish an application for iOS. We use firebase crashlytics to grab crash report. We get a crash that related to iOS CFNetwork. This crash happen on iPhone 14 Pro/ iOS 16.1.0 I attach the crash log below. Please check and give me some suggestion. Thank you so much. Crash Log
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
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
Ed and I discussed the issue behinds the scenes, and so I am chiming in to comment the following error from the Core Data perspective. Regarding the following error: error: :8:15: error: cannot convert value of type 'NSFetchRequest' to expected argument type 'NSFetchRequest' context.fetch(request) ^ :8:15: note: arguments to generic parameter 'ResultType' ('ResultType' and 'any NSFetchRequestResult') are expected to be equal This seems to indicate that you were passing an NSFetchRequest object tied to one entity as an argument to a closure (configurationBlock?) and the closure expects (or infers) a fetch request tied to the other entity. Since the potential type mismatch happens in runtime, it's hard to reason the why by simply reading the piece of code. Do you have a minimal sample project that reproduce the issue? You mentioned that the error does not occur on every call, but since you've figured out the line triggering the crash and use lldb to trigger the crash report, I'd think
Topic:
App & System Services
SubTopic:
iCloud & Data
Tags:
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
Okay, looks like this is entirely down to SwiftUI being weird. It appears to be gaming the UITabBar system. Each time you tap to select a tab, SwiftUI is changing the view controller list for the tab bar. For n tabs, it contains n-1 plain UIViewControllers with empty views, and 1 HostingController<_ViewList_View>. Tapping on a tab will update the content of hosting controller to contain the content of the SwiftUI tab, and it will reassign the UITabBarController's viewControllers property—it moves the HostingController to the index of the tapped tab, and puts a new empty UIViewController at its old position.Here's the output of that property as I walk through four SwiftUI tabs:(lldb) po [$21 viewControllers] <__NSArrayM 0x6000015091d0>( <_TtGC7SwiftUI19UIHostingControllerVS_14_ViewList_View_: 0x7fddabe0c600>, <UIViewController: 0x7fdd9bc2eeb0>, <UIViewController: 0x7fddabf2bd80>, <UIViewController: 0x7fddabd11b40> ) (lldb) po [$21 viewControllers] <__NSA
Topic:
UI Frameworks
SubTopic:
SwiftUI
Tags:
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.
FB8819661 Thanks! We’ve seen reports of similar problems from internal folks. I can’t explain all the details but it seems that LLDB has encountered some complex debugging info related to C++, got itself confused, and then handled that very ungracefully. Clearly we are interested in finding a fix for this. Is there any chance you could share a project that reproduces the problem? If so, that’d really help the LLDB folks investigate this. If you’re able to do this, please add the project to your bug report and then post back here to let me know. But if not, that’s cool, I understand that sharing code is not always feasible. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @apple.com
Topic:
Programming Languages
SubTopic:
Swift
Tags:
Very deep cleaning (rm derived data, caches, ++) fixes the missing BackgroundTask console output. So whats left is that Xcode 13 LLDB does not print objects in most places of out code. Reproducible for the complete team. error: invalid target, create a target using the 'target create' command // ... (lldb) po someObject error: :3:1: error: cannot find 'someObject' in scope While Xcode 12.x works as expected. Due to the fact the internet did not explode yet, I assume this is not a general Xcode issue but something related to our Xcode Project. Any hint highly appreciated o/
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
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