Ever since Xcode 15 and iOS 17 came out development has quite often been a nightmare of waiting and waiting -Xcode displaying endless circles saying preparing the device, connecting to the device, installing the device. But recently to add to this, installation and launching is just taking really forever. I'm currently running Xcode 15.1 and various versions of iOS 17 (I have several phones) and installing the app from Xcode takes about 7 - 10 minutes (compared to the same app installing in seconds with Xcode 14 for example). Then once its finally installed, it then takes further minutes to launch, Xcode often actually displays a dialog saying its taking longer than expected to launch the app, adding the footnote LLDB is likely reading from device memory to resolve symbols. What could be reasons, and solutions, for the excruciatingly slow installation time, and launch time? I really need to find a solution to this please - making a code change tweak, running, making another, running, making another,
Search results for
LLDB crash
30,302 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
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
Topic:
Programming Languages
SubTopic:
General
Tags:
One more, all crash is happening in iOS 26.1.0 and iPadOS 26.1.0
Topic:
UI Frameworks
SubTopic:
UIKit
Tags:
I have same problem, and crash count is groving because users update iOS
Topic:
UI Frameworks
SubTopic:
UIKit
Tags:
Hello Apple engineers, could you help me understand whether this crash is a UIKit bug or something in our code that causes it. Based on the documentation it is an invalid fetch instruction, that's why I suspect UIKit. I've found a similar crash here on the forums reported a year ago, it seemed to be a UIKit bug - https://forums.developer.apple.com/forums/thread/729448. I've attached the full crash report (the app name was replaced with ): Thread 0 Crashed: 0 libobjc.A.dylib 0x000000019daf7c20 objc_msgSend + 32 (:-1) 1 UIKitCore 0x00000001a3020c50 -[UIView _wrappedProcessTraitChanges:withBehavior:] + 1288 (UIView.m:0) 2 UIKitCore 0x00000001a3020720 -[UIView _processChangesFromOldTraits:toCurrentTraits:withBehavior:] + 196 (UIView.m:7840) 3 UIKitCore 0x00000001a3020618 -[UIView _updateTraitCollectionAndProcessChangesWithBehavior:previousCollection:] + 112 (UIView.m:7831) 4 UIKitCore 0x00000001a2fa90c0 -[UIView(CALayerDelegate) layoutSublayersOfLayer:] + 944 (UIView.m:19850) 5
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.
Topic:
Developer Tools & Services
SubTopic:
Xcode
Tags:
Ever since I did the update. My phone has been crashing apps are not opening. It shuts off by itself. It won’t send messages. I’ve never had such a problem before. I cannot get things to send, and my phone won’t answer calls and when IEvery since I did the update. My phone has been crashing apps are not opening. It shuts off by itself. It won’t send messages. I’ve never had such a problem before I cannot get things to send, and my phone won’t answer calls and when I try to answer them, it just won’t end so they go to voicemail.
Topic:
Community
SubTopic:
Apple Developers
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.
Topic:
Community
SubTopic:
Apple Developers
(NSString*)getClienttime { NSDate* currentDate = [NSDate date]; NSDateFormatter* dateformatter = [[NSDateFormatter alloc] init]; dateformatter.timeZone = [NSTimeZone timeZoneForSecondsFromGMT:8*3600]; dateformatter.locale= [NSLocale systemLocale]; [dateformatter setDateFormat:@yyyy-MM-dd HH:mm:ss]; return [dateformatter stringFromDate:currentDate]?:@; } the info of crash 1 libicucore.A.dylib icu::UnicodeString::copyFrom(icu::UnicodeString const&, signed char) (in libicucore.A.dylib) + 36 2 libicucore.A.dylib icu::DecimalFormatSymbols::operator=(icu::DecimalFormatSymbols const&) (in libicucore.A.dylib) + 64 3 libicucore.A.dylib icu::DecimalFormatSymbols::operator=(icu::DecimalFormatSymbols const&) (in libicucore.A.dylib) + 64 4 libicucore.A.dylib icu::DecimalFormat::DecimalFormat(icu::DecimalFormat const&) (in libicucore.A.dylib) + 188 5 libicucore.A.dylib icu::DecimalFormat::clone() const (in libicucore.A.dylib) + 48 6 libicucore.A.dylib icu::NumberFormat::createInstance(icu::Locale c
Topic:
UI Frameworks
SubTopic:
UIKit
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
Topic:
UI Frameworks
SubTopic:
UIKit
Tags:
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
Topic:
App & System Services
SubTopic:
Networking
Tags:
In the XCode 16 beta, it isn't possible to create a new StoreKit configuration file because the templates list doesn't contain that option. Adding the storekit extension to a file crashes XCode or doesn't have an effect at all. But, loading an existing file still works.
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
Topic:
App & System Services
SubTopic:
Notifications
Tags:
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
Topic:
Code Signing
SubTopic:
General
Tags:
Hello, I sent this in as a feedback several weeks ago about watchOS 26.2 beta 2 but since the issue is still active now that watchOS 26.2 is in production I'm reposting here for the community. I would also like to submit a DTS about this issue but honestly don't know the best way to go about it and would appreciate advice about that. There seems to be an issue with VPP distribution for our app on watchOS 26.2. When our watchOS companion app is launched after being installed through VPP to a supervised iPhone, it encounters a dyld error before main() or any application code is even called. The same app launches correctly in every other circumstance we could imagine and test: – Installed through VPP on supervised devices running watchOS 26.1. – Installed from the app store (using an apple id) on a supervised iPhone and paired watch running iOS 26.2 / watchOS 26.2. – Installed through Testflight on a supervised iPhone and paired watch running iOS 26.2 / watchOS 26.2. – Installed through the app store on unsuperv