I've having trouble deleting AppleDouble files residing on my custom filesystem through Finder. This also affects files that use the AppleDouble naming convention, i.e. their names start with '._', but aren't AppleDoubles themselves. dtrace output In vnop_readdir, 'struct dent/dentry' is set up for dotbar files and written to the uio_t buffer. It's just that my vnop_remove is never called for dotbar files, and I don't understand why not. Dotbar files are removed successfully, when deleted through command line. For SMBClients, vnop_readdir is followed by vnop_access, followed by vnop_lookup, followed by vnop_remove of dotbar files. SMBClient rm dotbar files dtrace output Implementing vnop_access for my filesystem did not result in the combination of vnop_lookup and vnop_remove being called for dotbar files. Perusing the kernel sources, I observed the following functions that might be involved, but I have not way of verifying this, as none of the functions of interest are dtrace(1)-able, rmdir_remove_orphaned_appleDouble() in particular. rmdir_remove_orphaned_appleDouble() -> VNOP_READDIR(). rmdirat_internal() -> rmdir_remove_orphaned_appleDouble() unlinkat()-> rmdirat_internal() rmdir()-> rmdirat_internal() Any pointers on how dotbar files may be removed through Finder would be greatly appreciated.

I am working with an open source watch called PineTime to implement ANCS support so users can receive iOS notifications in the watch. I am having g trouble discovering the ANCS on an iOS device. The watch is properly paired and bonded. I realize that the ANCS may not always be present, so I also subscribed to the GATT Service changed characteristic, but never received a notification/indication for a service becoming active. Is there something I am missing? Thanks!

Attempting to acquire the value of the 'kern.hostname' ctl from a kext by calling sysctlbyname() returns EPERM with no hostname returned. sysctlbyname() is aliased to kernel_sysctlbyname(): config/Libkern.exports:839:_sysctlbyname:_kernel_sysctlbyname Looking at the implementation of kernel_sysctlbyname(), EPERM is returned by sysctl_root(). Not sure how to correctly identify the point of failure. Alternately, calling sysctlbyname("hw.ncpu") does return the value set for the ctl. The kext was compiled with SYSCTL_DEF_ENABLED defined to have the relevant section of sys/sysctl.h enabled. bsd_hostname() is a private symbol which is inaccessible to my kext. % sysctl -n kern.hostname does return the host name, so the ctl must be set. Is it possible to get the name of a host from the context of my kext? Thanks.

We use network extension for the VPN connection implementation. In the network extension, we need to call a third-party library to do some check. Before the macOS is upgraded to 15.2, everything is fine. It just stop working after macOS is upgraded to 15.2. I did some debugging, and looks like the api provided by the dylibs is blocked. One system log is shown suspiciously Unable to create bundle at URL (<private>): unable to create file system representation of URL (13) The background is that we did embed the third-party dylibs in the app resources folder and the app extension tries to dlopen the dylibs and call the functions. And actually we do not know how the dylibs are implemented. Since it was working with older macOS, we would like to see if there is any related change on os itself. I have tried to change the places of dylibs, moving them from container app bundle resource folder to app extension resources folder, even the app group folder. Unfortunately it does not work either. Do you guys have any opinions?

Hello, My react native iOS app crash on startup on iOS14. And the crash may not have anything to do with the js code, because I remove all js code in App.tsx, It still crashes. My Env is: React Native: 0.76.1 Xcode: 15.4 here is the crash log: ------------------------------------- Translated Report (Full Report Below) ------------------------------------- Incident Identifier: 2665B36E-F475-44FA-B53C-951668A70886 CrashReporter Key: 902ecf6cea3413a23ae0ed8e51de826bacd686c9 Hardware Model: iPhone13,4 Process: ConcreteApp [20498] Path: /Volumes/VOLUME/*/ConcreteApp.app/ConcreteApp Identifier: com.lets.concrete Version: 1.1.7 (1) Code Type: ARM-64 (Native) Role: Foreground Parent Process: launchd [1] Coalition: com.lets.concrete [3008] Date/Time: 2024-12-25 11:38:14.7041 +0800 Launch Time: 2024-12-25 11:38:14.6657 +0800 OS Version: iPhone OS 14.8.1 (18H107) Release Type: User Baseband Version: 1.80.02 Report Version: 104 Exception Type: EXC_CRASH (SIGABRT) Exception Note: EXC_CORPSE_NOTIFY Termination Reason: DYLD 4 Symbol missing symbol '_$sSo12NSURLSessionC10FoundationE4data3for8delegateAC4DataV_So13NSURLResponseCtAC10URLRequestV_So0A12TaskDelegate_pSgtYaKF' not found, expected in '/usr/lib/swift/libswiftFoundation.dylib', needed by '/private/var/containers/Bundle/Application/9C2952C2-DA35-4C38-B060-C385050F3DB9/ConcreteApp.app/ConcreteApp' Highlighted by Thread: 0 Backtrace not available No thread state (register information) available Binary Images: Binary images description not available Error Formulating Crash Report: _dyld_process_info_create failed with 6 Failed to create CSSymbolicatorRef - corpse still valid ¯\_(ツ)_/¯ Failed to extract dyld error info: The size of the data is not what is expected EOF ----------- Full Report ----------- {"app_name":"ConcreteApp","timestamp":"2024-12-25 11:38:16.00 +0800","app_version":"1.1.7","slice_uuid":"809cfd69-02ad-36b6-8478-40b3a92daa01","adam_id":"0","build_version":"1","platform":"0","bundleID":"com.lets.concrete","share_with_app_devs":"0","is_first_party":"0","etl_key":"3","bug_type":"309","os_version":"iPhone OS 14.8.1 (18H107)","incident_id":"2665B36E-F475-44FA-B53C-951668A70886","name":"ConcreteApp"} { "uptime": 750000, "procLaunch": "2024-12-25 11:38:14.6657 +0800", "procRole": "Foreground", "version": 2, "exception": { "type": "EXC_CRASH", "signal": "SIGABRT", "codes": "0x0000000000000000, 0x0000000000000000" }, "userID": 501, "modelCode": "iPhone13,4", "coalitionID": 3008, "osVersion": { "isEmbedded": true, "train": "iPhone OS 14.8.1", "releaseType": "User", "build": "18H107" }, "captureTime": "2024-12-25 11:38:14.7041 +0800", "incident": "2665B36E-F475-44FA-B53C-951668A70886", "pid": 20498, "cpuType": "ARM-64", "procName": "ConcreteApp", "procPath": "/Volumes/VOLUME/*/ConcreteApp.app/ConcreteApp", "bundleInfo": { "CFBundleShortVersionString": "1.1.7", "CFBundleVersion": "1", "CFBundleIdentifier": "com.lets.concrete" }, "storeInfo": { "applicationType": "User", "itemID": "0", "deviceIdentifierForVendor": "47A5105F-B968-4006-BE3F-BE9C7E566C3B" }, "parentProc": "launchd", "parentPid": 1, "coalitionName": "com.lets.concrete", "crashReporterKey": "902ecf6cea3413a23ae0ed8e51de826bacd686c9", "basebandVersion": "1.80.02", "isCorpse": 1, "termination": { "flags": 518, "code": 4, "namespace": "DYLD", "indicator": "Symbol missing", "reasons": [ "symbol '_$sSo12NSURLSessionC10FoundationE4data3for8delegateAC4DataV_So13NSURLResponseCtAC10URLRequestV_So0A12TaskDelegate_pSgtYaKF' not found, expected in '/usr/lib/swift/libswiftFoundation.dylib', needed by '/private/var/containers/Bundle/Application/9C2952C2-DA35-4C38-B060-C385050F3DB9/ConcreteApp.app/ConcreteApp'" ] }, "legacyInfo": { "threadHighlighted": 0 }, "reportNotes": [ "_dyld_process_info_create failed with 6", "Failed to create CSSymbolicatorRef - corpse still valid \u00af\\_(\u30c4)_/\u00af", "Failed to extract dyld error info: The size of the data is not what is expected" ] }

Hardware Model: iPhone15,3 Process: fieldserviceapp [14394] Path: Version: 1.0.446605 (446605) Code Type: ARM-64 Parent Process: [1] Date/Time: 2024-12-03 22:01:11.0030 +0530 OS Version: iPhone OS 18.1.1 (22B91) Exception Type: SIGTRAP Exception Codes: #0 Triggered by Thread: 31 Thread 0 name: Thread 0: 0 libsystem_kernel.dylib 0x00000001ecc76688 mach_msg2_trap + 8 1 libsystem_kernel.dylib 0x00000001ecc79cb0 mach_msg_overwrite + 424 2 libsystem_kernel.dylib 0x00000001ecc79afc mach_msg + 24 3 CoreFoundation 0x000000019c8b5a84 __CFRunLoopServiceMachPort + 160 4 CoreFoundation 0x000000019c8b5130 __CFRunLoopRun + 1212 5 CoreFoundation 0x000000019c8b4830 CFRunLoopRunSpecific + 588 6 GraphicsServices 0x00000001e88941c4 GSEventRunModal + 164 7 UIKitCore 0x000000019f41aeb0 -[UIApplication _run] + 816 8 UIKitCore 0x000000019f4c95b4 UIApplicationMain + 340 9 fieldserviceapp 0x0000000100e44e60 0x100e34000 + 69216 10 ??? 0x00000001c22a2ec8 0x0 + 7552511688 Thread 1 name: Thread 1: 0 libsystem_kernel.dylib 0x00000001ecc76688 mach_msg2_trap + 8 1 libsystem_kernel.dylib 0x00000001ecc79cb0 mach_msg_overwrite + 424 2 libsystem_kernel.dylib 0x00000001ecc79afc mach_msg + 24 3 CoreFoundation 0x000000019c8b5a84 __CFRunLoopServiceMachPort + 160 4 CoreFoundation 0x000000019c8b5130 __CFRunLoopRun + 1212 5 CoreFoundation 0x000000019c8b4830 CFRunLoopRunSpecific + 588 6 Foundation 0x000000019b55c500 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 212 7 Foundation 0x000000019b55c350 -[NSRunLoop(NSRunLoop) runUntilDate:] + 64 8 UIKitCore 0x000000019f42e358 -[UIEventFetcher threadMain] + 420 9 Foundation 0x000000019b56d6c8 NSThread__start + 724 10 libsystem_pthread.dylib 0x0000000224de937c _pthread_start + 136 11 libsystem_pthread.dylib 0x0000000224de4494 thread_start + 8 Thread 2 name: Thread 2: 0 libsystem_kernel.dylib 0x00000001ecc76688 mach_msg2_trap + 8 1 libsystem_kernel.dylib 0x00000001ecc79cb0 mach_msg_overwrite + 424 2 libsystem_kernel.dylib 0x00000001ecc79afc mach_msg + 24 3 CoreFoundation 0x000000019c8b5a84 __CFRunLoopServiceMachPort + 160 4 CoreFoundation 0x000000019c8b5130 __CFRunLoopRun + 1212 5 CoreFoundation 0x000000019c8b4830 CFRunLoopRunSpecific + 588 6 fieldserviceapp 0x0000000101226620 0x100e34000 + 4138528 7 Foundation 0x000000019b56d6c8 NSThread__start + 724 8 libsystem_pthread.dylib 0x0000000224de937c _pthread_start + 136 9 libsystem_pthread.dylib 0x0000000224de4494 thread_start + 8 Thread 3 name: Thread 3: 0 libsystem_kernel.dylib 0x00000001ecc7bf90 __psynch_cvwait + 8 1 libc++.1.dylib 0x00000001ace87584 std::__1::condition_variable::wait(std::__1::unique_lockstd::__1::mutex&) + 28 2 hermes 0x0000000103788f24 0x1036bc000 + 839460 3 hermes 0x0000000103788e8c 0x1036bc000 + 839308 4 libsystem_pthread.dylib 0x0000000224de937c _pthread_start + 136 5 libsystem_pthread.dylib 0x0000000224de4494 thread_start + 8 Thread 4 name: Thread 4: 0 libsystem_kernel.dylib 0x00000001ecc7bf90 __psynch_cvwait + 8 1 libc++.1.dylib 0x00000001ace87584 std::__1::condition_variable::wait(std::__1::unique_lockstd::__1::mutex&) + 28 2 hermes 0x0000000103788f24 0x1036bc000 + 839460 3 hermes 0x0000000103788e8c 0x1036bc000 + 839308 4 libsystem_pthread.dylib 0x0000000224de937c _pthread_start + 136 5 libsystem_pthread.dylib 0x0000000224de4494 thread_start + 8 Thread 5 name: Thread 5: 0 libsystem_kernel.dylib 0x00000001ecc7bf90 __psynch_cvwait + 8 1 libc++.1.dylib 0x00000001ace87584 std::__1::condition_variable::wait(std::__1::unique_lockstd::__1::mutex&) + 28 2 CardReaderWrapperDynamic 0x000000010432e3e4 0x104298000 + 615396 3 CardReaderWrapperDynamic 0x0000000104330a08 0x104298000 + 625160 4 libsystem_pthread.dylib 0x0000000224de937c _pthread_start + 136 5 libsystem_pthread.dylib 0x0000000224de4494 thread_start + 8 Thread 9 name: Thread 9: 0 libsystem_kernel.dylib 0x00000001ecc7bf90 __psynch_cvwait + 8 1 libc++.1.dylib 0x00000001ace87618 std::__1::condition_variable::__do_timed_wait(std::__1::unique_lockstd::__1::mutex&, std::__1::chrono::time_point<std::__1::chrono::system_clock, std::__1::chrono::duration<long long, std::__1::ratio<(long)1, (long)1000000000> > >) + 100 2 fieldserviceapp 0x0000000101d115fc 0x100e34000 + 15586812 3 fieldserviceapp 0x0000000101e740fc 0x100e34000 + 17039612 4 fieldserviceapp 0x0000000101e6f878 0x100e34000 + 17021048 5 fieldserviceapp 0x0000000101e75e2c 0x100e34000 + 17047084 6 libsystem_pthread.dylib 0x0000000224de937c _pthread_start + 136 7 libsystem_pthread.dylib 0x0000000224de4494 thread_start + 8 Thread 12 name: Thread 12: 0 libsystem_kernel.dylib 0x00000001ecc76688 mach_msg2_trap + 8 1 libsystem_kernel.dylib 0x00000001ecc79cb0 mach_msg_overwrite + 424 2 libsystem_kernel.dylib 0x00000001ecc79afc mach_msg + 24 3 CoreFoundation 0x000000019c8b5a84 __CFRunLoopServiceMachPort + 160 4 CoreFoundation 0x000000019c8b5130 __CFRunLoopRun + 1212 5 CoreFoundation 0x000000019c8b4830 CFRunLoopRunSpecific + 588 6 CFNetwork 0x000000019de30ee0 +[__CFN_CoreSchedulingSetRunnable _run:] + 416 7 Foundation 0x000000019b56d6c8 NSThread__start + 724 8 libsystem_pthread.dylib 0x0000000224de937c _pthread_start + 136 9 libsystem_pthread.dylib 0x0000000224de4494 thread_start + 8

I am trying to use ScreenCaptureKit to select this window automatically rather than having the user do it.

I've been working on implementing alternate app icons for my iOS app, and everything works perfectly in debug builds on both the simulator and a physical device. However, when testing on TestFlight, I encounter the following error: The requested operation couldn’t be completed because the feature is not supported. Has anyone faced this issue before? Is there a specific TestFlight configuration or setup I might be missing to enable alternate app icon functionality?

our app has a helper to perform privileged operations. previously that helper was installed via SMJobBless() into the /Library/LaunchDaemons/ and /Library/PrivilegedHelperTools/ we also had a script that would install the helper from the command-line, which was essential for enterprise users that could not manually install the helper on all their employee's Macs. the script would copy the files to their install location and would use launchctl bootstrap system as the CLI alternative to SMJobBless(). the full script is here: https://pastebin.com/FkzuAWwV due to various issues with the old SMJobBless() approach we have ported to helper to the new SMAppService API where the helpers do not need to be installed but remain within the app bundle ( [[SMAppService daemonServiceWithPlistName:HELPER_PLIST_NAME] registerAndReturnError:&err] ) however, we are having trouble writing a (remote-capable) CLI script to bootstrap the new helper for those users that need to install the helper on many Macs at once. running the trivial sudo launchctl bootstrap system /Applications/MacUpdater.app/Contents/Library/LaunchDaemons/com.corecode.MacUpdaterPrivilegedInstallHelperTool2.plist would just result in a non-informative: Bootstrap failed: 5: Input/output error various other tries with launchctl bootstrap/kickstart/enable yielded nothing promising. so, whats the command-line way to install a SMAppService based helper daemon? obviously 'installing' means both 'registering' (which we do with registerAndReturnError in the GUI app) and 'approving' (which a GUI user needs to manually do by clicking on the notification or by going into System Settings). thanks in advance! p.s. we wanted to submit this as a DTS TSI, but those are no longer available without spending another day on a reduced sample projects. words fail me. p.p.s. bonus points for a CLI way to give FDA permissions to the app!

I have NTFS which is mounted on '/Volumes/usb_vol' #mount Filesystem Mounted on /dev/disk5s1 /Volumes/usb_vol The following simple code reports different values of device Id for device-file and mount point directory struct stat buf; for (int i = 1; i < argc; i++) { std::cout << argv[i] << std::endl; if (stat(argv[i], &buf) < 0) { continue; } if (S_ISBLK(buf.st_mode)) { std::cout << "st_rdev (" << major(buf.st_rdev) << "/" << minor(buf.st_rdev) << ") hex: " << std::hex << buf.st_rdev << std::endl; } else { std::cout << "st_dev (" << major(buf.st_dev) << "/" << minor(buf.st_dev) << ") hex: " << std::hex << buf.st_dev << std::endl; } } Output: /dev/disk5s1 st_rdev (1/22) hex: 1000016 /Volumes/usb_vol st_dev (48/119) hex: 30000077 I believe this is expected but I have not found any explanation of this behaviour. Are there any explanation of difference these values? I can assume the stat() will report (48/119) for all objects which are located on this file system. Is it correct? Thank you for the help!

Ples resolve

Hi, I'm not too good with terminal stuff, but when I looked at activity monitor, my corespotlightd was using too much of my cpu. I decided to look up solutions on google and stumbled upon this: https://forums.developer.apple.com/forums/thread/675482. I tried some of the commands, and I closed the terminal while sudo was still running because I was getting impatient. Somehow, before I even realized it, I was logged out of my Apple ID and my desktop and downloads files were completely gone. For some reason, my applications are still the same, which makes me wonder if some of the files or folders I had before can still be recoverable. I checked time machine, and I wasn't able to recover anything. How cooked am I? I've lost all of my university work and some other pictures and stuff that I thought would never be damaged if I had it locally. Would appreciate any type of help. Thanks.

Hello, I am encountering an issue with user-generated files stored in the Documents directory on an iPhone 11 running iOS 18.2. The problem occurs as follows: 1.The app generates and saves files in the Documents directory using FileManager. 2.These files are successfully saved and remain accessible while the app is running. 3.After restarting the app, the files appear to have been deleted from the Documents directory. I have confirmed that: 1.The files are being saved to the correct location (Documents directory) and can be accessed during the current app session. 2.The app is not explicitly deleting these files during shutdown or restart. 3.This behavior is consistent across multiple app restarts.

Hello, I am encountering an issue with user-generated files stored in the Documents directory on an iPhone 11 running iOS 18.2. The problem occurs as follows: 1.The app generates and saves files in the Documents directory using FileManager. 2.These files are successfully saved and remain accessible while the app is running. 3.After restarting the app, the files appear to have been deleted from the Documents directory. I have confirmed that: 1.The files are being saved to the correct location (Documents directory) and can be accessed during the current app session and from iExplorer. 2.The app is not explicitly deleting these files during shutdown or restart. 3.This behavior is consistent across multiple app restarts.

I recently started saving a file, where I hold some app state, to an AppGroup in order to share it with my widget extension. Of the some 16k daily active users of my app, 55 are initially unable to read the file (it might not yet be created). And they are unable to write a file to the AppGroup as well. I only know this due to logging the error to Crashlytics. Error Reading: "The file “BFTPreferences” couldn’t be opened because you don’t have permission to view it. Error Code:257" My App sees this error and informs the user to restart their device. I have not been contacted by any of these users for support, so I assume the restart fixes things. Has anyone seen this before? Is restarting the device the only fix? Am I doing something wrong? The only solution I can think of currently is to save the file to the app's Documents directory and save a copy to the AppGroup for use in my extensions. At least then the main app won't have an issue and it will just be the widget unable to display data until a restart. Reading the file: do { // archive data let data = try PropertyListSerialization.data(fromPropertyList: preferences, format: .xml, options: 0) // write data do { if let groupURL = FileManager.default.containerURL(forSecurityApplicationGroupIdentifier: appGroupIdentifier) { let fullPath = groupURL.appendingPathComponent(preferencesFileName) try data.write(to: fullPath) } else { fatalError("Unable to find app group \(appGroupIdentifier)") } } catch { logthis("Failed to write dictionary data to disk. \(error.localizedDescription)") } } catch { logthis("Failed to archive dictionary. \(error.localizedDescription)") } Writing the file: do { if let groupURL = FileManager.default.containerURL(forSecurityApplicationGroupIdentifier: appGroupIdentifier) { let fullPath = groupURL.appendingPathComponent(preferencesFileName) let data = try Data(contentsOf: fullPath) if let dictionary = try PropertyListSerialization.propertyList(from: data, format: nil) as? NSMutableDictionary { preferences = dictionary } } else { fatalError("Unable to find app group \(appGroupIdentifier)") } } catch { if (error as NSError).code == NSFileReadNoSuchFileError { // file doesn't exist so create it } else { logthis("Couldn't read BFTPreferences:\(error.localizedDescription)\nError Code:\((error as NSError).code)") <--error code 257 is caught here } }

0 CoreFoundation __exceptionPreprocess + 164 1 libobjc.A.dylib objc_exception_throw + 88 2 CoreFoundation -[__NSArrayI objectAtIndex:] + 0 3 UIKitCore -[UIInputSwitcherView selectedInputMode] + 116 4 UIKitCore -[UIInputSwitcherView didSelectItemAtIndex:] + 148 5 UIKitCore -[UIKeyboardMenuView selectItemAtPoint:] + 92 6 UIKitCore -[UIInputSwitcherView buttonPressed:withEvent:location:isLocationInsideViewHitArea:isForDictation:tapAction:] + 1040 7 UIKitCore -[UISystemKeyboardDockController dictationItemButtonWasPressed:withEvent:isRunningButton:] + 660 8 UIKitCore -[UISystemKeyboardDockController keyboardDockView:didPressDockItem:withEvent:] + 448 9 UIKitCore -[UIKeyboardDockView _dockItemButtonWasTapped:withEvent:] + 120

I would like to share my specific use case and seek your guidance on implementing it effectively within iOS: We are developing an iOS application that may run simultaneously on multiple devices near each other. The core functionality involves continuous Bluetooth Low Energy (BLE) scanning to detect peripherals (beacons) in the range of a central device. The scanning needs to function seamlessly across the following states: • Foreground • Background • Locked mode (when the device is locked) Here are the detailed requirements: 1. Scanning Behavior: • The central device should continuously scan for nearby BLE peripherals (beacons). • If a new peripheral comes into range, the application should capture its data, including: • Device Name • MAC Address • Payload Data • RSSI (Signal Strength) 2. Peripheral Out-of-Range Handling: • If a detected peripheral (beacon) moves out of range, it should automatically be removed from the populated list displayed on the app. 3. Peripheral Reappearance: • If a peripheral (beacon) that moved out of range comes back into range, the application should detect it again and repopulate the list with updated data seamlessly. 4. Application State: • This behavior (scanning, detection, and updating) should work regardless of the app’s state: • Foreground • Background • Device Locked FYI, we are using Custom Ruuvi beacons Given the above requirements, I would greatly appreciate any guidance, suggestions, or best practices to implement this use case efficiently while adhering to iOS background execution and Bluetooth limitations.

Hello, My application monitors ES_EVENT_TYPE_NOTIFY_CLOSE. If a file is dragged to another location in Finder, the Endpoint Security reports the event ES_EVENT_TYPE_NOTIFY_CLOSE was performed by '/usr/libexec/xpcproxy'. So, xpcproxy is the process that performed ES_EVENT_TYPE_NOTIFY_CLOSE. Looks like the dragged file is copied by some XPC service. I have found the audit user id is equal to user who dragged a file. Can audit user id be used to identify a user who triggers copy file action in this case? If no, are there any way to define such info? Thank you in advance!

when app enter background,sometimes crash at BSXPCCnx:com.apple.backboard.hid-services.xpc (BSCnx:client:BKHIDEventDeliveryManager) this is crash stack: 0 libsystem_pthread.dylib 0x3b30 pthread_mutex_lock + 12 1 ilink_live 0xbd884 (缺少 UUID 973fe6c5058c35bda98679b0c8aa0129) 2 ilink_live 0xb75fc (缺少 UUID 973fe6c5058c35bda98679b0c8aa0129) 3 libsystem_c.dylib 0x23d68 __cxa_finalize_ranges + 492 4 libsystem_c.dylib 0x23b64 exit + 32 5 BackBoardServices 0x579ec -[BKSHIDEventDeliveryManager _initForTestingWithService:] + 98 6 BoardServices 0xbae8 __31-[BSServiceConnection activate]_block_invoke.182 + 128 7 BoardServices 0x17620 __61-[BSXPCServiceConnectionEventHandler _connectionInvalidated:]_block_invoke + 196 8 BoardServices 0x8f64 BSXPCServiceConnectionExecuteCallOut + 240 9 BoardServices 0x18e5c -[BSXPCServiceConnectionEventHandler _connectionInvalidated:] + 180 10 libdispatch.dylib 0x2370 _dispatch_call_block_and_release + 32 11 libdispatch.dylib 0x40d0 _dispatch_client_callout + 20 12 libdispatch.dylib 0xb6d8 _dispatch_lane_serial_drain + 744 13 libdispatch.dylib 0xc214 _dispatch_lane_invoke + 432 14 libdispatch.dylib 0x17258 _dispatch_root_queue_drain_deferred_wlh + 288 15 libdispatch.dylib 0x16aa4 _dispatch_workloop_worker_thread + 540 16 libsystem_pthread.dylib 0x4c7c _pthread_wqthread + 288 17 libsystem_pthread.dylib 0x1488 start_wqthread + 8 when crash happened ,most of time app recieved CBManagerStateResetting and CBManagerStateUnsupported event

My company manufactures an Accessory which has been a certified product for a number of years. We are switching manufacturers, and thereby need to re-certify under a new product plan with the new manufacturer. We release over the air updates to our accessory. The question is what do we do about the device's iAP2 IdentificationInformation Message, specifically the ProductPlanUID parameter. Should devices manufactured at our old manufacturer continue to declare our original Product Plan's UID in their identification information, or should they declare the new one?