Recently, there are some strange crash in my app，the crash stack appears TrafficLights and ExcursionTrain, but I do not search any results in my project.
Search results for
LLDB crash
29,562 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
tldr: Our app is randomly crashing on startup (about 1 every 10 times) but no Crash Report alert is being shown on screen nor sent to the Crash Logs tab on TestFlight. The app just simply opens and immediately closes with no apparent reason. No logs of the crash are kept inside Settings -> Privacy -> Analytics & Improvements -> Analytics Data. On the iPhone, the options Share iPhone Analytics and Share With App Developers are checked ( Settings -> Privacy -> Analytics & Improvements). No memory leaks detected using the Instruments app. More detailed explanation: Out of 6 iPhones used for testing, only 1 iPhone is presenting the crash. It's an iPhone 11 iOS 15.4 and no one has been able to replicate the crash using the other iPhones. We have an iPhone SE (2020) and an iPhone 12 Pro Max both with iOS 15.4, but we haven't been able to replicate the bug. The steps to reproduce the bug are these: Open the app, switch views, then force-clo
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.
We’ve run into a strange issue here. We are running an iOS 13 simulator device on Monterey (x86_64) and an app on said device causes a crash (this is expected). However, when the crash reporter attempts to write out the crash report, it crashes. Here is an excerpt from the translated crash report: Process: ReportCrash [88409] Path: /System/Library/CoreServices/ReportCrash Identifier: ReportCrash Version: ??? Code Type: X86-64 (Native) Parent Process: launchd [1] User ID: 503 Date/Time: 2022-06-01 15:45:32.9876 -0400 OS Version: macOS 12.3.1 (21E258) Report Version: 12 Bridge OS Version: 6.4 (19P4243) Anonymous UUID: 9D02B4AF-C468-6AD7-78E4-48395612A5A9 Time Awake Since Boot: 450000 seconds System Integrity Protection: enabled Crashed Thread: 3 Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x00000001206c2008 Exception Codes: 0x0000000000000001, 0x00000001206c2008 Exception Note: EXC_CORPSE_NOTIFY Termination Reason: Names
Since XCode 13.1 I'm getting no crash logs error in my Organizer window. I have re-authenticated, changed the filters to be as broad as possible (ie all versions, all platforms, for the last year) - and I still get this error. I know there are crash logs because up until now (ie the past few weeks) I've been reviewing them! I've cleared derived data, I've cleaned the project, I've rebooted, I've closed and restarted xCode, I've opened XCode preferences and re-authenticated (I had recently changed password so it was prompting me to re-authenticate anyway). Still, no crash logs. Any other cached data I should be clearing that could fix this? I know I have crash logs piling up right now.
I know about this entitlement, I've been using it for a while for multiple apps, but then why does it work without lldb or any entitlements? This is why it doesn't make much sense. If the entitlement is required, then I should be getting no route to host without lldb, which is not the case. What I didn't try is to debug a binary with entitlements appiled, however it'd be very unreasonable to expect debug binaries to be signed which is a requirement to apply entitlements. I'm just trying to debug locally, on my own machine, these binaries are built on the same machine, never distributed, same as debugging through Xcode, which I can't because this is not an Xcode project. For distribution it's 100% sensible, but I don't think the entitlement has anything to do with it.
Topic:
App & System Services
SubTopic:
Networking
Tags:
Hello everyone , Today I have a question about Apps on sale on Appstore. My apps have many crash, but those are ok I know why they crash. However, totally, something I want to ask is whether will Apple terminal our accounts or not if our apps get many crashes like that?
This is a general question- When a WidgetKit extension crashes is it ever restarted? When my widgets crash they do not refresh until the device is rebooted.
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
Hello so when I start xcode and create a new Swift project for IOS, the project is created correctly, then when I debug on the physical device (in this case iphone 6) the application crashes! and it generates the error below! The strange thing is that in the output only writes (lldb) without a specific error, how can I solve this?Xcode Crash Image: https://imgur.com/a/mXSeLbMAll Output Error :dyld`__abort_with_payload:0x1008322f0 <+0>: mov x16, #0x2090x1008322f4 <+4>: svc #0x80-> Thread 1: signal SIGABRT 0x1008322f8 <+8>: b.lo 0x100832310 ; <+32>0x1008322fc <+12>: stp x29, x30, [sp, #-0x10]!0x100832300 <+16>: mov x29, sp0x100832304 <+20>: bl 0x100831990 ; cerror_nocancel0x100832308 <+24>: mov sp, x290x10083230c <+28>: ldp x29, x30, [sp], #0x100x100832310 <+32>: ret(lldb)
I added widgets to my app and now it is crashing on launch when installed via TestFlight. The crashlog only shows ??? and the address 0x0 (see screenshot). Has someone of you seen something like this already and has an idea how to fix it? Some parameters: Very old project (started in 2009) some ObjC, some Swift, some SwiftUI Added an intent handler extension and a widget extension added base internationalisation the project has localisations that are marked as deprecated. When I delete them, App Store connect tells me that the binary is invalid. If you need more information, please let me know. crashlog-D727A673-E3C1-405C-B002-F7581A78DA09.crash
It’s not clear to me whether you’re trying to: Keep things secret Allow clients of your static library to debug There’s a significant tension between these two; you can’t support debugging and keep everything secret. Anyway, lemme start with the debugging situation. You are correct that: The compiler encodes a bunch of full paths into DWARF debugging information. If these paths don’t resolve, LLDB will have problems. An easy way around this is to set up source path mappings. To learn more about this, consult the LLDB help: (lldb) apropos target.source-map However, this is not your only option. For example: Various compilers have various options to cause them to embed relative paths. Or you can build your shipping libraries on a build server that uses a standard non-private path. There’s a whole world of info about this stuff out there on the ’net. A good search term is reproducible builds. In fact, one of my colleagues was has been discussing this with another developer recently in
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Can someone help me?!When I enter in the bug problems with iOS 10 on Bug Report, I recieve a message back that is telling me to Please provide crash logs. Please upload the actual crash log, rather than pasting it into the Description or into a text file.Can someone explain to me exactly how I am supposed to provide the crash logs, I enter in the text and upload an attatchment that includes my crash logs. Im not to sure what else they need from me or how they want it submitted.
Thanks for reply, I cant see anything worng at lldb. The point is, that its worked for few days and then stop. If im paste the same code (waze://?ll=32.233, 31.333&navigate=yes) to the safary url its working fine. Any idea?
Topic:
Programming Languages
SubTopic:
Swift
Tags:
I'm getting Photos crashing when I try to open it, tried opening it under a fresh login and it still crashed, anyone else getting this?