On app minor update, after moving to xcode 15.2 Any thoughts on what could be causing it? Thank you in advance.

panic(cpu 1 caller 0xfffffff017a8bf60): x86 CPU CATERR detected Debugger message: panic Memory ID: 0xff OS release type: User OS version: 21P3049 macOS version: 23D60 Kernel version: Darwin Kernel Version 23.3.0: Wed Dec 20 22:31:16 PST 2023; root:xnu-10002.81.5~10/RELEASE_ARM64_T8010 KernelCache UUID: 5055C553638BB2B9A72F9B074650402D Kernel UUID: 98C51133-18A2-37CC-8054-0C2A5A0CC992 Boot session UUID: 10AF6C85-ABD5-4EFC-B894-FCA5526A15B3 iBoot version: iBoot-10151.81.1 secure boot?: YES roots installed: 0 x86 EFI Boot State: 0xd x86 System State: 0x0 x86 Power State: 0x0 x86 Shutdown Cause: 0x5 x86 Previous Power Transitions: 0x10001000100 PCIeUp link state: 0x89473614 macOS kernel slide: 0xa400000 Paniclog version: 14 Kernel slide: 0x0000000011820000 Kernel text base: 0xfffffff018824000 mach_absolute_time: 0x11dabe93a329 Epoch Time: sec usec Boot : 0x65fa28af 0x00067d4f Sleep : 0x660be300 0x0005f658 Wake : 0x660be3c7 0x000e9358 Calendar: 0x660e9064 0x000acc96 Zone info: Zone map: 0xffffffddcf6fc000 - 0xffffffe3cf6fc000 . VM : 0xffffffddcf6fc000 - 0xffffffdeb5d60000 . RO : 0xffffffdeb5d60000 - 0xffffffdf02a2c000 . GEN0 : 0xffffffdf02a2c000 - 0xffffffdfe9090000 . GEN1 : 0xffffffdfe9090000 - 0xffffffe0cf6f4000 . GEN2 : 0xffffffe0cf6f4000 - 0xffffffe1b5d5c000 . GEN3 : 0xffffffe1b5d5c000 - 0xffffffe29c3c4000 . DATA : 0xffffffe29c3c4000 - 0xffffffe3cf6fc000 Metadata: 0xffffffe3d570c000 - 0xffffffe3d6f0c000 Bitmaps : 0xffffffe3d6f0c000 - 0xffffffe3d702c000 Extra : 0 - 0 TPIDRx_ELy = {1: 0xffffffdfe92a24e0 0: 0x0000000000000001 0ro: 0x0000000000000000 } CORE 0: PC=0xfffffff018a4f008, LR=0xfffffff018a4f008, FP=0xffffffeff4337ef0 CORE 1 is the one that panicked. Check the full backtrace for details. Compressor Info: 3% of compressed pages limit (OK) and 1% of segments limit (OK) with 0 swapfiles and OK swap space Panicked task 0xffffffe29c34b8c0: 0 pages, 227 threads: pid 0: kernel_task Panicked thread: 0xffffffdfe92a24e0, backtrace: 0xffffffeff437f6a0, tid: 406893 lr: 0xfffffff018a1ea90 fp: 0xffffffeff437f710 lr: 0xfffffff018b4d6f4 fp: 0xffffffeff437f780 lr: 0xfffffff018b4c728 fp: 0xffffffeff437f8a0 lr: 0xfffffff0189e1630 fp: 0xffffffeff437f8b0 lr: 0xfffffff018a1e4cc fp: 0xffffffeff437fc60 lr: 0xfffffff01909d030 fp: 0xffffffeff437fc80 lr: 0xfffffff017a8bf60 fp: 0xffffffeff437fcb0 lr: 0xfffffff017a72f40 fp: 0xffffffeff437fd10 lr: 0xfffffff017a79908 fp: 0xffffffeff437fd60 lr: 0xfffffff017a73978 fp: 0xffffffeff437fe00 lr: 0xfffffff017a727d0 fp: 0xffffffeff437fe30 lr: 0xfffffff018a74034 fp: 0xffffffeff437ff20 lr: 0xfffffff0189ec6c4 fp: 0x0000000000000000

ASDisplayNode is obj-c.

Hello, I created an object which is inheriting from CLLocation. The main cause is that I want to store more properties Moreover I override the init function: override init(latitude: CLLocationDegrees, longitude: CLLocationDegrees) { super.init(latitude: latitude, longitude: longitude) } The objects aren't nil? Can anyone help Greeting Fabian

Hey, I am trying to use Family Controls in Mac Catalyst. On the iOS app it works fine. On macOs using Mac Catalyst it builds fine but I get following console output. Failed to get service proxy: Error Domain=NSCocoaErrorDomain Code=4099 "The connection to service named com.apple.FamilyControlsAgent was invalidated: failed at lookup with error 159 - Sandbox restriction." UserInfo={NSDebugDescription=The connection to service named com.apple.FamilyControlsAgent was invalidated: failed at lookup with error 159 - Sandbox restriction.}` When i try to open the FamilyActivityPicker on the macOs app following error is displayed in the GUI. The operation could not be completed. (FamilyControls.ActivityPickerRemoteView Error error 2.) Do I need a familyControls capability for macOs? If yes, I only find it for iOS. Thanks for hints and help :)

Hello, I have received 3 almost identical crash reports from the App Store. They all come from the same user, and they are spaced just ± 45 seconds apart. This is the backtrace of the crashed thread: Crashed Thread: 3 Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6 Terminating Process: Ssssssss [46033] Thread 3 Crashed: 0 libsystem_kernel.dylib 0x00007ff81b90f196 __pthread_kill + 10 1 libsystem_pthread.dylib 0x00007ff81b946ee6 pthread_kill + 263 (pthread.c:1670) 2 libsystem_c.dylib 0x00007ff81b86dbdf __abort + 139 (abort.c:155) 3 libsystem_c.dylib 0x00007ff81b86db54 abort + 138 (abort.c:126) 4 libc++abi.dylib 0x00007ff81b901282 abort_message + 241 5 libc++abi.dylib 0x00007ff81b8f33fb demangling_terminate_handler() + 267 6 libobjc.A.dylib 0x00007ff81b5c67ca _objc_terminate() + 96 (objc-exception.mm:498) 7 libc++abi.dylib 0x00007ff81b9006db std::__terminate(void (*)()) + 6 8 libc++abi.dylib 0x00007ff81b900696 std::terminate() + 54 9 libdispatch.dylib 0x00007ff81b7a6047 _dispatch_client_callout + 28 (object.m:563) 10 libdispatch.dylib 0x00007ff81b7a87c4 _dispatch_queue_override_invoke + 800 (queue.c:4882) 11 libdispatch.dylib 0x00007ff81b7b5fa2 _dispatch_root_queue_drain + 343 (queue.c:7051) 12 libdispatch.dylib 0x00007ff81b7b6768 _dispatch_worker_thread2 + 170 (queue.c:7119) 13 libsystem_pthread.dylib 0x00007ff81b943c0f _pthread_wqthread + 257 (pthread.c:2631) 14 libsystem_pthread.dylib 0x00007ff81b942bbf start_wqthread + 15 (:-1) In the backtrace of the main thread, I can see that the error is caught by the app delegate which tries to display an alert, but obviously the message has no time to appear. Incidentally (but it's not my main question), I would like to know if it would be possible in such a case to block the background thread for the time the alert is displayed (e.g. using a dispatch queue)? ... (many other related lines) 72 SSUuuuIIIIIIIIIUUuuuu 0x000000010e8089f2 +[NSAlert(Ssssssss) fatalError:] + 32 73 Ssssssss 0x000000010dd5e75b __universalExceptionHandler_block_invoke (in Ssssssss) (SQAppDelegate.m:421) + 333659 74 libdispatch.dylib 0x00007ff81b7a4d91 _dispatch_call_block_and_release + 12 (init.c:1518) 75 libdispatch.dylib 0x00007ff81b7a6033 _dispatch_client_callout + 8 (object.m:560) 76 libdispatch.dylib 0x00007ff81b7b2fcf _dispatch_main_queue_drain + 954 (queue.c:7794) 77 libdispatch.dylib 0x00007ff81b7b2c07 _dispatch_main_queue_callback_4CF + 31 (queue.c:7954) 78 CoreFoundation 0x00007ff81ba62195 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 9 (CFRunLoop.c:1780) 79 CoreFoundation 0x00007ff81ba21ebf __CFRunLoopRun + 2452 (CFRunLoop.c:3147) 80 CoreFoundation 0x00007ff81ba20ec1 CFRunLoopRunSpecific + 560 (CFRunLoop.c:3418) 81 HIToolbox 0x00007ff8254a5f3d RunCurrentEventLoopInMode + 292 (EventLoop.c:455) 82 HIToolbox 0x00007ff8254a5d4e ReceiveNextEventCommon + 657 (EventBlocking.c:384) 83 HIToolbox 0x00007ff8254a5aa8 _BlockUntilNextEventMatchingListInModeWithFilter + 64 (EventBlocking.c:171) 84 AppKit 0x00007ff81eabfb18 _DPSNextEvent + 858 (CGDPSReplacement.m:818) 85 AppKit 0x00007ff81eabe9c2 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1214 (appEventRouting.m:407) 86 AppKit 0x00007ff81eab1037 -[NSApplication run] + 586 (NSApplication.m:3432) 87 AppKit 0x00007ff81ea85251 NSApplicationMain + 817 (NSApplication.m:9427) 88 dyld 0x00007ff81b5ec41f start + 1903 (dyldMain.cpp:1165) In all 3 reports, another thread indicates that it is sending or receiving a MIDI data (it's exactly the same backtrace in the 3 reports): Thread 1: 0 libsystem_kernel.dylib 0x00007ff81b908552 mach_msg2_trap + 10 1 libsystem_kernel.dylib 0x00007ff81b9166cd mach_msg2_internal + 78 (mach_msg.c:201) 2 libsystem_kernel.dylib 0x00007ff81b90f584 mach_msg_overwrite + 692 (mach_msg.c:0) 3 libsystem_kernel.dylib 0x00007ff81b90883a mach_msg + 19 (mach_msg.c:323) 4 CoreMIDI 0x00007ff834adfd50 XServerMachPort::ReceiveMessage(int&, void*, int&) + 94 (XMachPort.cpp:62) 5 CoreMIDI 0x00007ff834b118c5 MIDIProcess::MIDIInPortThread::Run() + 105 (MIDIClientLib.cpp:204) 6 CoreMIDI 0x00007ff834af9c44 CADeprecated::XThread::RunHelper(void*) + 10 (XThread.cpp:21) 7 CoreMIDI 0x00007ff834afae9f CADeprecated::CAPThread::Entry(CADeprecated::CAPThread*) + 77 (CAPThread.cpp:324) 8 libsystem_pthread.dylib 0x00007ff81b9471d3 _pthread_start + 125 (pthread.c:893) 9 libsystem_pthread.dylib 0x00007ff81b942bd3 thread_start + 15 (:-1) I wonder if this MIDI activity may be related to the crash, even if it doesn't occur in the crashed thread. I also wonder if the dispatch block starting the backtrace of the thread 3 is the same that leads to the thread 1 (to open the NSAlert), which would mean that it's after the error, or if it's a dispatch block into which the error occurs. Finally, 2024-03-25_13-04-40.6314.crash I wonder if std::terminate() could indicate a problem in C++ codes because I have some part of the application written in C++, and it would be a clue. More generally, is it something in these backtraces that can help me to find what's the problem ? Any help greatly appreciated, thanks! -dp

Hi, I'm curious if anyone knows what I might look for in this crash report. I'm not seeing any functions in my application in any of the stacks so I'm stumped as to what might be happening. com.apple.main-thread 0 libobjc.A.dylib 0x4808 objc_msgSend + 8 1 AuthKitUI 0x553a4 _DrawBorder + 140 2 AuthKitUI 0x54d68 AKDrawAppleIDButtonWithCornerRadius + 92 3 AuthKitUI 0x54cc0 AKCreateAppleIDButtonImageWithCornerRadius + 212 4 AuthenticationServices 0x39358 + 152 5 UIKitCore 0x15aee8 + 508 6 QuartzCore 0x67db8 + 252 7 QuartzCore 0x67cb0 + 64 8 QuartzCore 0x67168 + 1636 9 QuartzCore 0x66480 + 412 10 QuartzCore 0x6c860 + 464 11 QuartzCore 0x65b80 + 648 12 QuartzCore 0x65828 + 88 13 CoreFoundation 0x357bc + 36 14 CoreFoundation 0x341c4 + 548 15 CoreFoundation 0x338e0 + 1028 16 CoreFoundation 0x333f8 CFRunLoopRunSpecific + 608 17 GraphicsServices 0x34f8 GSEventRunModal + 164 18 UIKitCore 0x22c8a0 + 888 19 UIKitCore 0x22bedc UIApplicationMain + 340 20 MaaCompanionApp 0x8050 main + 8 (main.m:8) 21 ??? 0x1b0e02dcc (Missing) la_client 0 libsystem_kernel.dylib 0x10f4 semaphore_wait_trap + 8 1 libdispatch.dylib 0x489c + 28 2 libdispatch.dylib 0x4f4c + 132 3 LocalAuthentication 0x15398 + 500 4 LocalAuthentication 0x164bc + 196 5 CoreFoundation 0x31714 + 148 6 CoreFoundation 0x311ac + 428 7 Foundation 0x6a3a0 + 16 8 Foundation 0x69f20 + 520 9 Foundation 0x69888 + 188 10 Foundation 0x2033c + 2244 11 CoreFoundation 0x31b5c + 1008 12 CoreFoundation 0x172950 _CF_forwarding_prep_0 + 96 13 LocalAuthentication 0x163ac + 236 14 LocalAuthentication 0x2ba4 + 504 15 libdispatch.dylib 0x4300 + 20 16 libdispatch.dylib 0x13ce8 + 56 17 LocalAuthentication 0x295c + 196 18 LocalAuthentication 0x1626c + 340 19 LocalAuthentication 0x21f14 + 468 20 LocalAuthentication 0x226a8 + 304 21 Security 0x11b10 + 1712 22 Security 0x11454 + 140 23 Security 0x112b4 SecOSStatusWith + 56 24 Security 0x1855c SecItemCopyMatching + 400 25 MaaCompanionApp 0x2d0a0c -[RNKeychainManager getGenericPasswordForOptions:resolver:rejecter:] + 387 (RNKeychainManager.m:387) 26 CoreFoundation 0x31714 + 148 27 CoreFoundation 0x311ac + 428 28 CoreFoundation 0x30fd4 + 64 29 MaaCompanionApp 0x355598 -[RCTModuleMethod invokeWithBridge:module:arguments:] + 587 (RCTModuleMethod.mm:587) 30 MaaCompanionApp 0x3575ec facebook::react::invokeInner(RCTBridge*, RCTModuleData*, unsigned int, folly::dynamic const&, int, (anonymous namespace)::SchedulingContext) + 197 (RCTNativeModule.mm:197) 31 MaaCompanionApp 0x35723c invocation function for block in facebook::react::RCTNativeModule::invoke(unsigned int, folly::dynamic&&, int) + 304 (optional:304) 32 libdispatch.dylib 0x26a8 + 32 33 libdispatch.dylib 0x4300 + 20 34 libdispatch.dylib 0xb894 + 748 35 libdispatch.dylib 0xc3c4 + 380 36 libdispatch.dylib 0x17004 + 288 37 libdispatch.dylib 0x16878 + 404 38 libsystem_pthread.dylib 0x1964 _pthread_wqthread + 288 39 libsystem_pthread.dylib 0x1a04 start_wqthread + 8 Thread 0 libsystem_kernel.dylib 0x96d0 __workq_kernreturn + 8 1 libsystem_pthread.dylib 0x19b0 _pthread_wqthread + 364 2 libsystem_pthread.dylib 0x1a04 start_wqthread + 8 Thread 0 libsystem_kernel.dylib 0x96d0 __workq_kernreturn + 8 1 libsystem_pthread.dylib 0x19b0 _pthread_wqthread + 364 2 libsystem_pthread.dylib 0x1a04 start_wqthread + 8 Thread 0 libsystem_kernel.dylib 0x96d0 __workq_kernreturn + 8 1 libsystem_pthread.dylib 0x19b0 _pthread_wqthread + 364 2 libsystem_pthread.dylib 0x1a04 start_wqthread + 8 Crashed: com.apple.root.default-qos 0 libsystem_kernel.dylib 0xc358 __abort_with_payload + 8 1 libsystem_kernel.dylib 0x32ed0 + 104 2 libsystem_kernel.dylib 0x32f04 (Missing UUID 08f02c6b1443366598054a8bee87346e) 3 TCC 0x68f8 + 172 4 TCC 0x2e88 + 598 5 TCC 0xa1f8 + 624 6 libxpc.dylib 0x1eb44 + 116 7 libxpc.dylib 0x114b8 + 80 8 libdispatch.dylib 0x4380 + 20 9 libdispatch.dylib 0x21b04 + 344 10 libdispatch.dylib 0x16d40 + 336 11 libdispatch.dylib 0x16628 + 500 12 libsystem_pthread.dylib 0x199c _pthread_wqthread + 344 13 libsystem_pthread.dylib 0x1a04 start_wqthread + 8

After my project was packaged with Xcode15, the following crash occurred, which had not occurred before. After checking for a long time, the cause was not found, because similar problems did not occur when Xcode14 was used to package, so I think it is the problem caused by Xcode15 packaging Incident Identifier: 3DFEAAAC-DCEE-4C6F-B51D-29BE9448A9C0 CrashReporter Key: KSCrash2 Hardware Model: iPhone15,3 Process: KPlayi4Phone [11803] Path: /private/var/containers/Bundle/Application/FD3F5994-3F75-4477-B629-2343870A4995/KPlayi4Phone.app/KPlayi4Phone Identifier: com.KPlay.KPlay Version: 2035752548 (11.0.73) Code Type: ARM-64 Parent Process: ? [1] Date/Time: 2024-03-28 15:02:18 +0800 Launch Time: 2024-03-28 15:02:10 +0800 OS Version: iOS 16.2 (20C65) Report Version: 104 Exception Type: EXC_BREAKPOINT Exception Codes: KERN_INVALID_ADDRESS at 0x00000001d256402c Exception Subtype: SIGTRAP Triggered by Thread: 0 Thread 0 Crashed: 0 CoreFoundation 0x00000001d256402c __CFRunLoopServiceMachPort.cold.1 :56 (in CoreFoundation) 1 CoreFoundation 0x00000001d242ebd4 __CFBasicHashIncSlotCount :0 (in CoreFoundation) 2 CoreFoundation 0x00000001d242fd18 __CFRunLoopRun :1232 (in CoreFoundation) 3 CoreFoundation 0x00000001d2434ec0 _CFRunLoopRunSpecific :612 (in CoreFoundation) 4 GraphicsServices 0x000000020c48b368 _GSEventRunModal :164 (in GraphicsServices) 5 UIKitCore 0x00000001d492a86c -[UIApplication _run] :888 (in UIKitCore) 6 UIKitCore 0x00000001d492a4d0 _UIApplicationMain :340 (in UIKitCore) 7 KPlayi4Phone 0x0000000100f5608c main main.m:16 (in KPlayi4Phone) 8 ??? 0x00000001f0c56960 0x0000000000000000 + 8334436704 9 ??? 0x0000000000000000 0x0000000000000000 + 0 mycrash.crash

My App is crashing when launched on iPad but is working in the browser. The client was able to send me a crash log from an iPad experiencing the issue since I am not able to replicate the crash locally. Is this due to a data issue? It's unclear from the logs. Crash log attached, thank you.

iPhone 16.0 16.0.2 系统上运行小组件出现问题， 其他系统没有问题 SendProcessControlEvent:toPid: encountered an error: Error Domain=com.apple.dt.deviceprocesscontrolservice Code=8 "Failed to show Widget 'com.jiduauto.iphone.jdcomiphoneWidget' error: Error Domain=FBSOpenApplicationServiceErrorDomain Code=5 "The request to open "com.apple.springboard" failed." UserInfo={NSLocalizedDescription=The request to open "com.apple.springboard" failed., NSLocalizedFailureReason=Unexpected error type., NSUnderlyingError=0x600002bbd7a0 {Error Domain=BSServiceConnectionErrorDomain Code=3 "XPC error received on message reply handler" UserInfo={BSErrorCodeDescription=OperationFailed, NSLocalizedFailureReason=XPC error received on message reply handler}}, BSErrorCodeDescription=InvalidResponse}." UserInfo={NSLocalizedDescription=Failed to show Widget 'com.jiduauto.iphone.jdcomiphoneWidget' error: Error Domain=FBSOpenApplicationServiceErrorDomain Code=5 "The request to open "com.apple.springboard" failed." UserInfo={NSLocalizedDescription=The request to open "com.apple.springboard" failed., NSLocalizedFailureReason=Unexpected error type., NSUnderlyingError=0x600002bbd7a0 {Error Domain=BSServiceConnectionErrorDomain Code=3 "XPC error received on message reply handler" UserInfo={BSErrorCodeDescription=OperationFailed, NSLocalizedFailureReason=XPC error received on message reply handler}}, BSErrorCodeDescription=InvalidResponse}., NSUnderlyingError=0x600002bbd5f0 {Error Domain=FBSOpenApplicationServiceErrorDomain Code=5 "The request to open "com.apple.springboard" failed." UserInfo={NSLocalizedDescription=The request to open "com.apple.springboard" failed., NSLocalizedFailureReason=Unexpected error type., NSUnderlyingError=0x600002bbd7a0 {Error Domain=BSServiceConnectionErrorDomain Code=3 "XPC error received on message reply handler" UserInfo={BSErrorCodeDescription=OperationFailed, NSLocalizedFailureReason=XPC error received on message reply handler}}, BSErrorCodeDescription=InvalidResponse}}} Domain: DTXMessage Code: 1 User Info: { DVTErrorCreationDateKey = "2024-02-19 08:02:14 +0000"; } System Information macOS Version 13.5.2 (Build 22G91) Xcode 15.0 (22265) (Build 15A240d) Timestamp: 2024-02-19T16:02:14+08:00

HI! Trying to figure out a particularly odd crash report (via crashlytics). Crashed: com.apple.main-thread 0 libsystem_kernel.dylib 0x7558 __pthread_kill + 8 1 libsystem_pthread.dylib 0x7118 pthread_kill + 268 2 libsystem_c.dylib 0x1d178 abort + 180 3 libswiftCore.dylib 0x3b93a8 swift::fatalError(unsigned int, char const*, ...) + 134 4 libswiftCore.dylib 0x3b93c8 swift::warningv(unsigned int, char const*, char*) + 30 5 libswiftCore.dylib 0x3bdfd8 swift_deallocPartialClassInstance + 190 6 libswiftCore.dylib 0x3bde28 _swift_release_dealloc + 56 7 libswiftCore.dylib 0x3bec4c bool swift::RefCounts<swift::RefCountBitsT<(swift::RefCountInlinedness)1> >::doDecrementSlow<(swift::PerformDeinit)1>(swift::RefCountBitsT<(swift::RefCountInlinedness)1>, unsigned int) + 132 8 PSStore 0xab8de0 ThankYouViewController.viewCleanup() + 32 (TwoPhaseCommitHelper.swift:32) Complete stackTrace here com.predictspring.pos_issue_63a57f567d9db225552c2cd24d915564_crash_session_7dfdc13304324dd39f1e60b48d20a6af_DNE_0_v2_stacktrace.txt The stack trace line that refers to our code points to a specific implementation of a ThreadedDictionary where we are removing all the objects inside the internal storage: We have not been able to reproduce this crash, however we are seeing multiple instances in our crash reports for it (All instances happening in iPadOS + 16.4.1 devices). Is there anything relevant to take a look in the first 7 frames of the crash report to understand what could be the issue? While researching on this, we identified a post with a very similar stacktrace entries: https://developer.apple.com/forums/thread/729196?login=true&page=1#752337022 We are not using GC or Unity, however the first entries in the stack trace look very similar. Rgds!

Hello iOS developers, I'm encountering a persistent crashing issue with my React Native app on an iOS 12.5.6 device. I'm reaching out to the community for guidance in troubleshooting and resolving this problem. Here are the details: Description: My app, built using React Native version 0.71.4, runs smoothly on newer iOS versions and in the development environment. However, when I install and launch the app on an iOS 12.5.6 device, it crashes immediately after the splash screen. Environment: macOS: Version 14.1.1 Xcode: Version 15.0.1 React Native: 0.71.4 Target iOS device: iOS 12.5.6 I kindly request your assistance in resolving this issue. If you have any suggestions, insights, or experiences with similar problems, please share them. Any code snippets or specific troubleshooting steps you recommend would be greatly appreciated. I have attached the log file from the iOS device for your reference. Thank you for your time and support! Best regards,

I successfully submitted my project to App Store Connect, and got it approved for external TestFlight testing. I have made updates to my project, and am trying to submit another build, but am getting the error: "The value for key CFBundeShortVersionString[1.0] in info.plist must contain a higher version.." I attempt to change both the short bundle version, and regular bundle version to 1.1.0 without any luck. I also attempted to go into the "Versioning" within build settings to change both the current project version and marketing version to 1.1.0 without any luck. I am confused what is going on, and why my build is not just incrementing as expected. Any suggestions is very appreciated.

Since yesterday (03/22/24) we are unable to upload new or existing builds to AppStoreConnect. We get the following error - “Error ITMS-90432 Unexpected file found in Frameworks. MyApp.app/Frameworks/Configurations” file is in the Frameworks directory, but the Swift runtime libraries are the only files permitted in that directory. Please remove this file and upload a new build. (ID: 57e219ea-d27e-465d-9e9b-ec41d3a0b1f7). We have tried rebuilding targerts with no changes for Builds that use to upload ok and they now get the same error too. Is this an appstoreconnect bug? If not where is the Frameworks directory and how do we remove the file?

I submitted my app today but I have gotten the crashlog. I tried to analyze the code but I used the flutter to make app. someone knows what is the issue? I am also using the firebase. Thanks crashlog-7D0F863A-09BA-4477-92CD-DD20A5DFEF60.txt

Hello, When running an iPad app on Apple Silicon (M1) the expirationDate OptionKey of the UIPasteboard has no impact, i.e. the copied value is never removed from the clipboard. The following code works perfectly on iOS, however, behaves how I described above on macOS. let currentDate = Date() let expireDate = currentDate.addingTimeInterval(TimeInterval(90)) UIPasteboard.general.setItems([[UIPasteboard.typeAutomatic: myString]], options: [UIPasteboard.OptionsKey.expirationDate: expireDate]) Is this a bug? I am on Swift 5.10. Thank you!

我升级到xcode15.3后出现这样的报错，xcode14能正常，请问怎么解决个？ Build input file cannot be found: '/FrontEnd/App/iOS/App/trunk/-Xlinker'. Did you forget to declare this file as an output of a script phase or custom build rule which produces it?

Hello, I’m trying to use the Frontline Teledyne Lecroy BPA100 Bluetooth Protocol Analyzer with Apples ATS v7.15.0 to capture Bluetooth connections between our device and another companies radio (or troubleshoot the lack thereof more accurately). While the probe physically doesn’t display any signs of life, it does seem to get detected by ATS when I plug it in as the field in ATS Capture “BPA 100/600” autofill’s with “FBA41199”. But it tells me this When I do try to reconnect the probe ATS crashes. Is the device broken?

Hello, I developed a flutter app. But its crashing in review I got. I am attaching the crash report. Can someone help in that. Thanks so much crashlog-6B4650EA-FAC7-4D88-B3B6-FC8951C5C871.txt crashlog-D4F6B942-0A15-4613-9E43-E93BD671BA0B.txt

2024-03-18 15:13:19.549232+0800 Xeena[5316:4106501] -[__NSCFString containsObject:]: unrecognized selector sent to instance 0x6000014393e0 2024-03-18 15:13:19.599811+0800 Xeena[5316:4106501] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[__NSCFString containsObject:]: unrecognized selector sent to instance 0x6000014393e0' *** First throw call stack: ( 0 CoreFoundation 0x0000000118e168ab __exceptionPreprocess + 242 1 libobjc.A.dylib 0x000000010f06eba3 objc_exception_throw + 48 2 CoreFoundation 0x0000000118e25ab8 +[NSObject(NSObject) instanceMethodSignatureForSelector:] + 0 3 CoreFoundation 0x0000000118e1ad71 forwarding + 1431 4 CoreFoundation 0x0000000118e1d068 _CF_forwarding_prep_0 + 120 5 UIKitCore 0x0000000129c9b3b7 -[UIApplication _checkBackgroundRefreshAPIAdoption] + 169 6 UIKitCore 0x0000000129c7520e -[UIApplication _runWithMainScene:transitionContext:completion:] + 1023 7 UIKitCore 0x00000001290a18e5 -[_UISceneLifecycleMultiplexer completeApplicationLaunchWithFBSScene:transitionContext:] + 179 8 UIKitCore 0x0000000129c716e4 -[UIApplication _compellApplicationLaunchToCompleteUnconditionally] + 59 9 UIKitCore 0x0000000129c71aaf -[UIApplication _run] + 958 10 UIKitCore 0x0000000129c769ef UIApplicationMain + 123 11 Xeena 0x0000000102a8b350 main + 96 12 dyld 0x000000010e7bf2bf start_sim + 10 13 ??? 0x000000020640f41f 0x0 + 8694854687 ) libc++abi: terminating with uncaught exception of type NSException It's a crash log. react native projects crash on emulators after running locally, but on android machines there is no problem