“LLDB crash”

Here is a more step by step breakdown of the problem I have a iOS library that exposes a C function. This function is marked with default visibility and used via attribute tags to prevent the compiler/linker from stripping it #ifdef __cplusplus #define DYLIB_EXPORT extern C __attribute__((visibility(default))) __attribute__((used)) #else #define DYLIB_EXPORT __attribute__((visibility(default))) __attribute__((used)) #endif DYLIB_EXPORT bool say_hello_world(); #import helper_functions.h #import bool say_hello_world() { NSLog(@Hello WORLD 🟢!); return true; } From a dynamic library, called sdk, I want to call this function. In this example it's a Rust lib unsafe extern C { fn say_hello_world() -> bool; } #[unsafe(no_mangle)] extern C fn sdk_init() -> i32 { unsafe { say_hello_world(); } return 0; } When the app is compiled and launched from Xcode (either on debug or release schemes) then this works, the following snippet works and prints the hello WORLD message: #import OpacityObjCWrapper.h #import helper

One more, all crash is happening in iOS 26.1.0 and iPadOS 26.1.0

I have same problem, and crash count is groving because users update iOS

AN UPDATE: This suggestion (from ChatGPT) resolved the problem of the AI Assistant crashing: # from the folder that contains your .xcodeproj / .xcworkspace mv *.xcodeproj/xcuserdata ~/Desktop/xcuserdata_xcodeproj_backup 2>/dev/null mv *.xcworkspace/xcuserdata ~/Desktop/xcuserdata_xcworkspace_backup 2>/dev/null There still remains the problem where one specific .mm file will absolutely NOT show its specific changes. I'll continue to investigate.

Not enough information to help you. What phone are you using? What version of iOS did you install? When does the phone crash? And do you mean the actual phone crashes and reboots, or do you mean apps just crash immediately when you try to launch them? Why doesn't it send messages? What happens? Any errors? No one can help you unless you provide the right information. It's like walking up to a mechanic and telling him your car won't start, but not telling him what model of car it is, where it is, what you've tried to get it to start, and into which lake you threw the keys. Besides, this isn't the place for your query. These are the Developer Forums, where developers of apps for Apple's platforms ask each other for hints and tips on coding. Your question is more of a product support one, so I'd suggest you ask it over at the Apple Support Forums. Thanks.

We're experiencing a similar UpdateCycle crash on iOS 26, though with a slightly different manifestation. Our crash occurs when displaying custom inputView keyboards on iPad devices. Crash Details: Exception: NSInternalInconsistencyException Message: Invalid parameter not satisfying: parentEnvironment != nil Location: UC::DriverCore::continueProcessing() at address 5472 in UpdateCycle library OS Version: iPadOS 26.1.0 (84.6% of crashes), also seen on 26.0.0 and 26.0.1 Device: 100% iPad devices (iPad Pro models, all in landscape orientation) Reproduction Context: The crash occurs when a custom UIView is set as textField.inputView and the text field becomes first responder on iPad. The crash happens during UpdateCycle's processing when it attempts to access the focus environment hierarchy. The custom keyboard view appears to be accessed by UpdateCycle before it's fully integrated into the focus hierarchy, resulting in a nil parentEnvironment. Key Observation

As i am facing also same crash into Xcode 26.1.1 (production build) and Testing on Xcode 26.2. and when i set usesClassicLoadingMode = false. its stopped preparing form request encoding. as i can see there is no data into httpbody. @DTS Engineer

First of all, App Review handles rules on a case by case basis, and usually will refrain from commenting on apps unless they are under review. So, for a final answer, you will need to submit your app. That said, these are my educated opinions. Although this is an off label use for a Notification Service Extension which is meant to be used for modifying content in newly delivered notifications, there are no strict rules for what you can do within the limits of an extension process. The process is short lived (30 seconds), memory restrained (24 MB), and bound by a number of sandbox rules that limit the abuse it can inflict on a user's device. The OS itself will enforce the rules, up to and including deciding to not launch the extension if it historically has been terminated for constantly crashing and/or being terminated due to not properly handling the constraints. Also keep in mind that these notifications have to be visible, and cannot be silent notifications. If you wanted to use silent notificatio

Following up here. This is of course infernally annoying to test and debug: there is no response from Apple on this issue or documentation about VPP vs App Store differences. Furthermore we can only test our attempted changes by submitting a new build to the app store, waiting for approval, and then trying to deploy to our devices with VPP. What we can confirm is: – This is happening with other watch companion apps installed through VPP. HOWEVER a couple of watch companion apps I tested DID work. I would be happy to provide a list for comparison to Apple if it's helpful. – We tried adjusting a bunch of project settings related to optimization, dead code stripping, symbol stripping, etc. following a mix of online and AI-based guidance about potential objective-c metadata issues flagged from the crash logs. Our app is primarily based on Swift 5 but it does target some objective-c pods and frameworks which haven't changed in years. This didn't help. – Our app used the old WatchKit architecture with both