Search results for

LLDB crash

29,555 results found

Post

Replies

Boosts

Views

Activity

Reply to App crashes on start in TestFlight
7 libsystem_c.dylib 0x000000018decc2d0 abort + 124 (abort.c:122) 8 AppName 0x00000001048a19cc mono_log_write_os_log + 38214092 (mono-log-darwin.c:0) 9 AppName 0x0000000104897454 monoeg_g_logv + 38171732 (goutput.c:173) 10 AppName 0x000000010489759c monoeg_g_log + 38172060 (goutput.c:184) 11 AppName 0x00000001049b986c load_aot_module + 39360620 (aot-runtime.c:2406) 12 AppName 0x00000001048f55b4 mono_assembly_request_load_from + 38557108 (assembly.c:2020) 13 AppName 0x00000001048f50d0 mono_assembly_request_open + 38555856 (assembly.c:1625) 14 AppName 0x00000001048f6370 mono_assembly_open + 38560624 (assembly.c:1828) 15 AppName 0x0000000104838524 xamarin_assembly_preload_hook + 37782820 (monotouch-main.m:0) This stack shows your app is crashing in code from Xamarin. Note that frame 8 and 7 show their code directly called abort(), which will cause the process to terminate. You should follow up with the support for Xamarin to learn how to set things up so you don't encounter this abort via their library.
Aug ’25
Issues with pulling Crash data from API
We are currently experiencing an issue accessing crash data via the App Store Connect Analytics API for several of our mobile apps. Summary of Issue: For certain app IDs, crash data is clearly visible within the App Store Connect UI under the App Crashes report. However, when attempting to retrieve this same data via the official Analytics API, no crash data is returned. Our integration makes the following API calls: GET /v1/analyticsReportRequests//reports?filter[category]=APP_USAGE GET /v1/analyticsReports//instances GET /v1/analyticsReports//segment (to retrieve download URL) This process works as expected for some apps, where the “App Crashes” report is available and the segment URL is returned. However, for other apps, while the crash data appears in the UI, the API does not return the “App Crashes” report or any segment URL to download the data. We’ve confirmed the report IDs and used the correct authentication headers in our requests. Quest
1
0
72
Apr ’25
Reply to Invalid Code Signing Entitlements
Hi @DTS Engineer, thank you for your reply. I've removed the entitlements.plist entry. Could you help confirm if it is expected that in my distribution provisioning profile In-App Purchase is ticked, but greyed out in it's Capabilities so I can't edit it? Also, before I added the entitlements.plist I was able to successfully use Transporter on my Mac to send my IPA file to App Store Connect. However, when I tested the app using TestFlight it was crashing on start every time. I've got the crash file, but I'm not sure it's very helpful (I've attached it). Is the any help of guidance you can give for figuring out why it's crashing? It works perfectly locally in debug/release mode. symbolicated.crash Thanks, Ben
Topic: Code Signing SubTopic: Entitlements Tags:
Aug ’25
Reply to Overriding global new and delete is not working.
[quote='853475022, oikawa_yoji, /thread/796579?answerId=853475022#853475022, /profile/oikawa_yoji'] The same source code is included in the Xcode project attached to the email I sent [/quote] Got it. Thanks. I ran your project and was immediately able to reproduce the problem. Specifically: I’m using Xcode 16.4 targeting the iOS 18.5 simulator. I ran the app from Xcode and it exited as expected. I then ran the same app from the simulator’s Home screen and it crashed. Here’s the backtrace from the resulting crash report: Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib … __pthread_kill + 8 1 libsystem_pthread.dylib … pthread_kill + 264 2 libsystem_c.dylib … abort + 100 3 libsystem_malloc.dylib … malloc_vreport + 896 4 libsystem_malloc.dylib … malloc_report + 60 5 libsystem_malloc.dylib … ___BUG_IN_CLIENT_OF_LIBMALLOC_POINTER_BEING_FREED_WAS_NOT_ALLOCATED + 28 6 cccccccccccc.debug.dylib … __debug_main_executable_dylib_entry_point + 268 (main.cpp:103) 7
Aug ’25
iOS 26 crashes with CALayerInvalidGeometry when using magnifier on Webview
I have a Net8 Maui WebView app and whenever I use magnifier, it crashes. The magnifier works on iOS18 and lower but crashes on iOS26+ Exception **Type:** CALayerInvalidGeometry **Value:** CALayer position contains NaN: [nan 65]. Layer: >; sublayers = (, ); opaque = YES; allowsGroupOpacity = YES; anchorPoint = CGPoint (inf 0); opacity = 0> Stacktrace __exceptionPreprocess in unknown file [Line null, column null] (Not in app) objc_exception_throw in unknown file [Line null, column null] (Not in app) +[NSException raise:format:] in unknown file [Line null, column null] (Not in app) CA::Layer::set_position in unknown file [Line null, column null] (Not in app) -[CALayer setPosition:] in unknown file [Line null, column null] (Not in app) -[UIView _backing_setPosition:] in unknown file [Line null, column null] (Not in app) -[UIView setCenter:] in unknown file [Line null, column null] (Not in app) -[_UIEditMenuContentPresentation _displayPreparedMenu:titleView:reason:didDismissMenu:configurati
Topic: Safari & Web SubTopic: General
2
0
194
Aug ’25
"Assertion failed: (false) function _onqueue_rdar53306264_addWaiter file TubeManager.cpp line 1042" Crash
We are experiencing a large number of crashes in our production environment, mainly occurring on iOS 16 systems and iPhone 8 and iPhone X devices. The crash log and stack trace are as follows: Error: Assertion failed: (false) function _onqueue_rdar53306264_addWaiter file TubeManager.cpp line 1042 Crashed: com.apple.CFNetwork.LoaderQ 0 libsystem_kernel.dylib 0x7198 __pthread_kill + 8 1 libsystem_pthread.dylib 0xd5f8 pthread_kill + 208 2 libsystem_c.dylib 0x1c4b8 abort + 124 3 libsystem_c.dylib 0x70d8c err + 266 4 CFNetwork 0x1eb80 CFURLRequestSetMainDocumentURL + 6288 5 CFNetwork 0x44fd8 CFURLCacheRemoveAllCachedResponses + 22624 6 CFNetwork 0x39460 _CFHostIsDomainTopLevel + 968 7 CFNetwork 0x1f754 CFURLRequestSetMainDocumentURL + 9316 8 CFNetwork 0x233e0 CFURLRequestSetRequestPriority + 8792 9 CFNetwork 0x20d38 CFURLRequestCopyHTTPRequestBodyStream + 1612 10 CFNetwork 0x4f950 CFHTTPCookieStorageCopyCookies + 16276 11 CFNetwork 0x15878 CFURLRequestSetURL + 7600 12 libdispatch.dylib 0
9
0
159
Aug ’25
Reply to "Assertion failed: (false) function _onqueue_rdar53306264_addWaiter file TubeManager.cpp line 1042" Crash
It’s better to reply as a reply, rather than in the comments; see Quinn’s Top Ten DevForums Tips for this and other titbits. What modifications can we make to prevent this issue from reoccurring? Honestly, I’ve no idea. Earlier I wrote: [quote='854100022, DTS Engineer, /thread/796647?answerId=854100022#854100022'] Historically this crash has been triggered by a range of concurrency problems within CFNetwork [/quote] The nature of concurrency bugs is that they can come and go based on hard to understand criteria. Consider this thought experiment: CFNetwork has a concurrency bug that causes this crash. The bug is highly dependent on network timing. You see a huge uptick of crash reports in your app during late November and late December. This might be nothing to do with your code, or your infrastructure. Rather, a big chunk of your users are travelling in late November and late December due to the US Thanksgiving and Christmas holidays. While travelling they’re on WWAN rather than Wi-
Aug ’25
FamilyActivityPicker Crash on selecting some items
Both view and modifier versions of the FamilyActivityPicker crash randomly when selecting some items (usually the other option) throwing these in the console: [com.apple.FamilyControls.ActivityPickerExtension(1150.1)] Connection to plugin invalidated while in use AX Lookup problem - errorCode:1100 error:Permission denied portName:'com.apple.iphone.axserver' PID:22091 ( 0 AXRuntime 0x00000001c603b0fc _AXGetPortFromCache + 800 1 AXRuntime 0x00000001c603cce0 AXUIElementPerformFencedActionWithValue + 700 2 UIKit 0x0000000230de3ec8 DDE6E0C5-2AC3-3C73-8CFE-BC88DE35BB5F + 1453768 3 libdispatch.dylib 0x0000000103ef0b98 _dispatch_call_block_and_release + 32 4 libdispatch.dylib 0x0000000103ef27bc _dispatch_client_callout + 20 5 libdispatch.dylib 0x0000000103efa66c _dispatch_lane_serial_drain + 832 6 libdispatch.dylib 0x0000000103efb408 _dispatch_lane_invoke + 408 7 libdispatch.dylib 0x0000000103f08404 _dispatch_root_queue_drain_deferred_wlh + 328 8 libdispatch.dylib 0x0000000103f07a38 _dispatch_workloop_worker
6
0
1.5k
Aug ’25
FamilyActivityPicker Crashing / Freezing
Our users report frequent crashes with the FamilyActivityPicker. Since this is a screen controlled by Apple, I'm assuming that there's nothing I can do to prevent these crashes. I'm wondering, though, if there's any way to gracefully handle these crashes? When this happens, the following is printed to the console: [com.apple.FamilyControls.ActivityPickerExtension(1121)] Connection to plugin invalidated while in use. Does anyone know how to handle/catch this error?
4
0
1.2k
Aug ’25
FamilyActivityPicker crashing when expanding "Other" category
Hi there, I'm presenting a FamilyActivityPicker inside of a sheet, and on some phones, the FamilyActivityPicker freezes and crashes when the user expands the Other category only. Other is the only category that exhibits this behavior, and it only does this on some phones, not in all cases. This issue is perfectly reproducible on those phones when using the FamilyActivityPicker for the other category only, but on those same phones it does not reproducible in the Native ScreenTime Picker in Settings → ScreenTime → App Limits → Add Limit. I don't have access to these phones as they are user reports, but any guidance here would be deeply appreciated. More broadly, there are several issues with the FamilyActivityPicker (categories expand on top of each other when multiple are opened, varying behavior with tapping rows vs tapping select bubbles depending on phone size, etc) that the Native ScreenTime Picker doesn't have. Grouping websites as a standalone category is preferable as well. Could we as develope
4
0
1.5k
Aug ’25