LLDB crash

Effectively, your code crashes in Xcode 26 / iOS 26 (but works in Xcode 16.4 / iOS 18.4). I think problem is the type used for event. I changed UIEvent in sliderValueDidChange: @objc func sliderValueDidChange(_ sender: UISlider, for event: UIEvent) { to UIControl.Event @objc func sliderValueDidChange(_ sender: UISlider, for event: UIControl.Event) { print(Slider value changed to: (sender.value) ) print(event) } No more crash, just the log: Slider value changed to: 0.025641026 UIControlEvents(rawValue: 0) Slider value changed to: 0.03926282 UIControlEvents(rawValue: 0) Did Xcode 26 replaced UIEvent by UIControl.Event ? In that case I could not find it in documentation.

Thanks for taking the time to answer. It's still crashing with your recommendation (screenshot 2) and lldb still shows an uninitialized pointer (screenshot 1). Also, I should add that this starts crashing with iOS 26 betas. It has been working fine with every iOS version so far. .

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.

Crash Report

Im seeing the same issue. After creating both an on-going and snap shot report, neither have crash metrics, (but they are clearly visible in the web UI) I have confirmed the API key associated with the request has the proper permissions. @Nathandorsch did you ever resolve this issue?

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

[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

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-

[quote='750847021, s.mojtaba, /thread/750847, /profile/s.mojtaba'] FamilyActivityPicker crash randomly [/quote] Please try again on the latest iOS 26 beta (beta 6 or newer). This should have been addressed by now. At least on my device I can no longer reproduce the crash.

[quote='743770021, popedriver, /thread/743770, /profile/popedriver'] frequent crashes with the FamilyActivityPicker [/quote] Please try again on the latest iOS 26 beta (beta 6 or newer). This should have been addressed by now. At least on my device I can no longer reproduce the crash.

[quote='728498021, _anteloper, /thread/728498, /profile/_anteloper'] FamilyActivityPicker freezes and crashes [/quote] Please try again on the latest iOS 26 beta (beta 6 or newer). This should have been addressed by now. At least on my device I can no longer reproduce the crash.