When I saw a crash, I analyzed the stack and found that the contents of the release UILabel crashed, but the contents of the UILabel is an NSString, which is a constant, how could crash be triggered? Thread 0 Crashed: 0 libobjc.A.dylib objc_release + 16 1 libobjc.A.dylib object_cxxDestructFromClass(objc_object*, objc_class*) + 112 2 libobjc.A.dylib objc_destructInstance + 88 3 libobjc.A.dylib _objc_rootDealloc + 52 4 UIKitCore -[UILabel .cxx_destruct] + 232 5 libobjc.A.dylib object_cxxDestructFromClass(objc_object*, objc_class*) + 112 6 libobjc.A.dylib objc_destructInstance + 88 7 libobjc.A.dylib _objc_rootDealloc + 52 8 UIKitCore -[UIResponder dealloc] + 152 9 UIKitCore -[UIView dealloc] + 872 10 UIKitCore -[UILabel dealloc] + 172 11 libobjc.A.dylib AutoreleasePoolPage::releaseUntil(objc_object**) + 180 12 libobjc.A.dylib objc_autoreleasePoolPop + 224 13 UIKitCore -[UIView dealloc] + 844 14 libobjc.A.dylib AutoreleasePoolPage::releaseUntil(objc_object**) + 180 15 libobjc.A.dylib objc_autoreleasePoolPop + 224 16 UIKitCore -[UIView dealloc] + 844 17 UIKitCore -[UITableViewCellContentView dealloc] + 76 18 UIKitCore -[UITableViewCell .cxx_destruct] + 600 19 libobjc.A.dylib object_cxxDestructFromClass(objc_object*, objc_class*) + 112 20 libobjc.A.dylib objc_destructInstance + 88 21 libobjc.A.dylib _objc_rootDealloc + 52 22 UIKitCore -[UIResponder dealloc] + 152 23 UIKitCore -[UIView dealloc] + 872 24 UIKitCore -[UITableViewCell dealloc] + 236 25 homebrew -[CKBubbleCell dealloc] (CKBubbleCell.m:222) 26 CoreFoundation RELEASE_OBJECTS_IN_THE_ARRAY + 112 27 CoreFoundation -[__NSArrayM dealloc] + 272 28 UIKitCore -[UITableView .cxx_destruct] + 1524 29 libobjc.A.dylib object_cxxDestructFromClass(objc_object*, objc_class*) + 112 30 libobjc.A.dylib objc_destructInstance + 88 31 libobjc.A.dylib _objc_rootDealloc + 52 32 UIKitCore -[UIResponder dealloc] + 152 33 UIKitCore -[UIView dealloc] + 872 34 UIKitCore -[UIScrollView dealloc] + 852 35 UIKitCore -[UITableView dealloc] + 364

Hi, I'm using React-Native and XCode 12.5.1. Since the last update of XCode, I receive this error by mail when I upload my archive : We identified one or more issues with a recent delivery for your app, "***" 1.28.5 (83). Please correct the following issues, then upload again. ITMS-90427: Invalid Swift Support - The expected dylibs are missing from the app’s Framework location, such as /Payload/***.app/Frameworks. I don't touch anything, but I can't put a new buld on the App Store...

I have an app which is Live on Appstore and has several daily active users. Recently a user reported consistent crash at random sports on her device. After communicating with the user, I got that the crash from her iPad mini 2 with iOS 12.4.8 and the stack trace has following information: log.ips After symbolicate the log: Thread 0 name: Dispatch queue: org.reactivecocoa.ReactiveObjC.RACScheduler.mainThreadScheduler Thread 0 Crashed: 0 libsystem_platform.dylib 0x0000000194547258 os_unfair_lock_lock$VARIANT$mp (in libsystem_platform.dylib) + 24 1 CoreFoundation 0x0000000194903190 __CFGetConverter (in CoreFoundation) + 92 2 CoreFoundation 0x0000000194902960 CFStringEncodingUnicodeToBytes (in CoreFoundation) + 180 3 CoreFoundation 0x0000000194905d78 __CFStringEncodeByteStream (in CoreFoundation) + 1604 4 Foundation 0x00000001952953d4 -[NSString(NSStringOtherEncodings) getBytes:maxLength:usedLength:encoding:options:range:remainingRange:] (in Foundation) + 248 5 CoreFoundation 0x000000019482de84 -[NSTaggedPointerString getBytes:maxLength:usedLength:encoding:options:range:remainingRange:] (in CoreFoundation) + 120 6 CoreFoundation 0x00000001948eb958 CFStringGetBytes (in CoreFoundation) + 144 7 Foundation 0x00000001954415ac _convertJSONString (in Foundation) + 416 8 Foundation 0x000000019544074c _writeJSONString (in Foundation) + 92 9 Foundation 0x00000001954418e0 ___writeJSONObject_block_invoke (in Foundation) + 80 10 libswiftCore.dylib 0x00000001c1f199f0 specialized _SwiftDeferredNSDictionary.enumerateKeysAndObjects(options:using:) (in libswiftCore.dylib) + 852 11 libswiftCore.dylib 0x00000001c1d6776c @objc _SwiftDeferredNSDictionary.enumerateKeysAndObjects(options:using:) (in libswiftCore.dylib) + 44 12 Foundation 0x0000000195440f20 _writeJSONObject (in Foundation) + 384 13 Foundation 0x0000000195441b84 ___writeJSONArray_block_invoke (in Foundation) + 156 14 CoreFoundation 0x0000000194919944 __NSArrayEnumerate (in CoreFoundation) + 412 15 Foundation 0x000000019544133c _writeJSONArray (in Foundation) + 288 16 Foundation 0x00000001952fd58c -[_NSJSONWriter dataWithRootObject:options:error:] (in Foundation) + 140 17 Foundation 0x00000001952fd2b4 +[NSJSONSerialization dataWithJSONObject:options:error:] (in Foundation) + 356 18 ??? 0x00000001035737b8 static Mapper.toJSONData(_:options:) (in --) (Mapper.swift:388) 19 ??? 0x00000001035736a4 static Mapper.toJSONString(_:prettyPrint:) (in --) (<compiler-generated>:0) 20 ??? 0x0000000103570e38 Mapper.toJSONString(_:prettyPrint:) (in --) (Mapper.swift:370) 21 ??? 0x000000010356eb94 Array<A>.toJSONString(prettyPrint:) (in --) (Mappable.swift:104) The logic is to dump an array to a file. Can anyone suggest what could be the possible issue here?

I am unable to find the reason of the crash and where it's happening. Please find the attach crash report below. Thanks. Crash Report

After updating to Xcode Version 13.0 (13A233) RC. I am no longer able to auto-sign my archived app and upload it to Testflight. I have double-checked my provisioning profiles on my developer account and everything seems to be in order. I was able to upload to Testflight on Xcode 12 without issues. Communication with Apple failed. You are not allowed to perform this operation. Please check with one of your Team Admins, or, if you need further assistance, please contact Apple Developer Program Support. https://developer.apple.com/support No profiles for '~~~~~~~~' were found Xcode couldn't find any iOS App Store provisioning profiles matching '~~~~~~~'.

Yesterday, I updated to Xcode 13 via the App Store. I'm trying to send an archive of my app to App Store Connect through the usual way in the "Organizer" window, and once the archive is submitted, I get the warning message: App Store Connect Operation Warning Your version of iTMSTransporter will be updated in approximately 10 days. I've never seen this before and have no idea what it means. The archive still shows in Testflight later and is useable, but I am not sure if it's safe to update the App Store version of my app with this archive build when it was uploaded with warnings. What is this warning, and how can I fix this? I also get this email about alternative icon errors after App Store Connect upload. I have alternative app icons enabled in the app and know for sure that I have 120x120 on iPhone, so I'm not sure why this is happening:

Hello there, When I run iOS app into iOS Simulator in iOS 15 its working fine but when I am trying to run it on Real device its crashing on button click and other navigation like push Any help would be appreciated Here is the crashlogs attachment Crashlogs ips file's text. Thanks In Advance.

Anyone know how to get Xcode cloud build crashes desymbolicated? I have a crash in organizer, and there seems to be no way to associate the remote build with the DSYM. I have a build made through Xcode cloud. I can download artifacts. TBH it's been a while since I've gone fishing for dsyms in an xcarchive but I found one. Am I missing something?

I'm currently using analytics from AppCenter(MS), and there is a bug that is occurring very frequently but with no clue to what it can be, just saying AppDelegate.swift (L:20), witch means declaration of class.. i'll put all relevant logs, so if anyone can help me, i'll appreciate! PS: I'm using AppAuth pod to manager login, already checked out all possible error cases. (code -2 to -15) I'm firing an event to AppCenter to register those events from error in Appauth library and comparing with crash log. Conclusion: there is no any relation each them. The only relevant thing about the app it needs to user log at app launch and it's using a third party service from web (SSO) Its work stuff and i'm not allowed to mention the name, so i changed app names in log from '##' Log: Incident Identifier: ## CrashReporter Key: ## Hardware Model: iPhone12,8 Process: ## [20613] Path: /private/var/containers/Bundle/Application/##/##.app/## Identifier: ## Version: ## Code Type: arm64 Parent Process: ??? [1] Date/Time: 2021-09-30T12:33:19.999Z Launch Time: 2021-09-30T12:31:05Z OS Version: iPhone OS 14.4 (18D52) Report Version: 104 Exception Type: SIGSEGV Exception Codes: SEGV_ACCERR at 0x6d6f633c6e6f6974 Crashed Thread: 0 Thread 0 Crashed: 0 libobjc.A.dylib 0x0000000198aee018 objc_release + 8 1 SafariServices 0x000000019ecf2e38 __75-[SFAuthenticationViewController dismissViewControllerAnimated:completion:]_block_invoke + 36 2 UIKitCore 0x0000000185c274b8 -[UIPresentationController transitionDidFinish:] + 1016 3 UIKitCore 0x0000000185c2bca4 __56-[UIPresentationController runTransitionForCurrentState]_block_invoke.528 + 208 4 UIKitCore 0x0000000185d708f8 -[_UIViewControllerTransitionContext completeTransition:] + 108 5 UIKitCore 0x0000000186972d28 -[UITransitionView notifyDidCompleteTransition:] + 240 6 UIKitCore 0x00000001869729d4 -[UITransitionView _didCompleteTransition:] + 1132 7 UIKitCore 0x00000001869aa8ec -[UIViewAnimationBlockDelegate _didEndBlockAnimation:finished:context:] + 720 8 UIKitCore 0x000000018697cc08 -[UIViewAnimationState sendDelegateAnimationDidStop:finished:] + 244 9 UIKitCore 0x000000018697d170 -[UIViewAnimationState animationDidStop:finished:] + 244 10 UIKitCore 0x000000018697d2d4 -[UIViewAnimationState animationDidStop:finished:] + 600 11 QuartzCore 0x0000000186ee7474 CA::Layer::run_animation_callbacks(void*) + 276 12 libdispatch.dylib 0x00000001836a8db0 _dispatch_client_callout + 16 13 libdispatch.dylib 0x00000001836b67ac _dispatch_main_queue_callback_4CF + 832 14 CoreFoundation 0x0000000183a3011c __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 12 15 CoreFoundation 0x0000000183a2a120 __CFRunLoopRun + 2504 16 CoreFoundation 0x0000000183a2921c CFRunLoopRunSpecific + 596 17 GraphicsServices 0x000000019b5f5784 GSEventRunModal + 160 18 UIKitCore 0x0000000186469ee8 -[UIApplication _run] + 1068 19 UIKitCore 0x000000018646f75c UIApplicationMain + 164 20 ## 0x00000001004bc1cc main (AppDelegate.swift:20) 21 libdyld.dylib 0x00000001836e96b0 start + 0 Thread 1: 0 libsystem_kernel.dylib 0x00000001b1a87184 __workq_kernreturn + 8 1 libsystem_pthread.dylib 0x00000001cf5e876c start_wqthread + 4 Thread 2: 0 libsystem_kernel.dylib 0x00000001b1a87184 __workq_kernreturn + 8 1 libsystem_pthread.dylib 0x00000001cf5e876c start_wqthread + 4 ....

Got emailed three .txt crash files. Cannot for the life of me figure out how to get Xcode to do something with them. Tried: renaming .txt to .crash Dropping onto "devices and simulators" window Dropping on to "devices and simulators > select device > View device logs" "Download debug symbols" for the archive in Xcode (says "dowloaded debug symbols" so did it) ... and many other things Xcode 13 simply refuses to respond to the drag-and-drop of the file no matter the file extension and no matter where in Xcode's various windows/tools I drop it. Has anyone done this with a crash .txt file from app review and Xcode 13?

My App seeing crashes very rarely on some devices with this crash log, How to identify what is making iOS terminating the app due to extended time and watchdog issues is occurring. I tried to understand and locate the issue reading these articles but somewhat not getting exactly to pin it.  Read this but still not able to pin point Writing link to Question asked on Stackoverflow as here it was not accepting the length of the crash log. Question here

I have been developing an app for a long time and I've been archiving it perfectly and users been able to install the ipa file on their iOS devices, but lately when I publish my app it crashes on start up and it can not finish function "didFinishLaunchingWithOptions". when I distribute earlier versions which I have their archive file, they are ok, but when I archive the earlier version it crashes too on the devices. I have to add that I run the app perfectly fine on Xcode run and it has no error nor crash. I believe something is wrong with archiving my application and it's almost a week that I'm stuck with it!! any help is appreciated :) xcode 13, macos :11.6, ios:15.0.1

Hi I have uploaded a new version of my macOS application successfully via Xcode 13 (archive & distribute app)... no errors during the upload. But the new release is not showing up in AppStore Connect, also I get no mail notification at all if an error occured. Can anybody help me out here? Sincerely, Domenico

Firebase logged crash Crashing on exception: -[UITableView setSectionHeaderTopPadding:]: unrecognized selector sent to instance 0x1589ca800 After checking code everywhere is call if #available(iOS 15.0, *) {    tableView.sectionHeaderTopPadding = 0.0 } Stack trace: Crashed: com.apple.main-thread 0 AppKit 0x3dda28 -[NSApplication _crashOnException:] + 372 1 AppKit 0x3dd70c -[NSApplication reportException:] + 588 2 AppKit 0x31f10 -[NSApplication run] + 792 3 AppKit 0x3878 NSApplicationMain + 1064 4 AppKit 0x2f2ad0 _NSApplicationMainWithInfoDictionary + 22 5 UIKitMacHelper 0x4e18 UINSApplicationMain + 1280 6 UIKitCore 0x2b1c UIApplicationMain + 164 7 TARGET 0x11358 main + 20 (AppDelegate.swift:20) 8 libdyld.dylib 0x18430 start + 4 Find out, that crash occures when using macbook with m1 processor.

The error received in crash report is NO_CRASH_STACK + 0 i am using xcode 13

HI all, My system keeps crashing (meaning rebooting...). I had several reports, all marking different threads as crashed. I do not know how to read these reports (i.e. I cannot pinpoint the correct information to spot the problem). Can you help me out? Thanks in advance! Crash report 19 Oct 2021

HI all, My system keeps crashing (meaning rebooting...). I had several reports, all marking different threads as crashed. I do not know how to read these reports (i.e. I cannot pinpoint the correct information to spot the problem). Can you help me out? Thanks in advance! Crash report 19 Oct 2021

It is not crashing the devices with my QA. Can you help us to give logs.