dsym file

@ChristianBr if you are unable to resolve this problem by updating your certificates, please consider filing a bug report and opening a code level support request. If you open a support request, include the url of this forums thread and the feedback number so the request can be assigned to my attention. https://developer.apple.com/support/technical/ Bug Reporting: How and Why? has tips on creating your bug report.

Since this question isn't about a specific API and it is about some Apple application programs I recommend filing a bug report and switching back to using a non-beta system software release where this problem does not exist. Normally this is the sort of question you'd ask in the Apple Support Community (Though, I realize questions about beta releases are often referred from there to these developer forums). Bug Reporting: How and Why? has tips on creating your bug report.

The code above is loading the PDFDocument from a Data object. It isn't doing any file system related operations. Can you show some source code where you're accessing the file system to get the Data object? How is your code interacting with these files?

@DTS Engineer Thanks for the response. I have filed a feedback report with the details discussed in this thread. Feedback ID: FB21848143 I really hope there is some initiative inside Apple to improve this area. Apart from the initial sync performance issues with large datasets, CKSyncEngine is an amazing API and makes ongoing synchronization much simpler and cleaner than rolling custom CloudKit logic. It would be great to see it scale better for first launch scenarios as well. Thanks again for taking the time to reply. I am not really sure whether marking file a feedback as the accepted answer makes sense here, since it does not actually help with the problem or provide any workaround. Over the years I have filed quite a few feedback reports and only one was ever addressed, and that was a UI bug. Because of that, I am honestly not very optimistic about this changing, especially since this is not something that directly shows up as a user-facing bug.

Thanks for the post, this is something I don’t think I have seen before unless I have a reference to some of the file. Definitely a head scratcher for me. Inviting other developers here to to provide there opinion of possible causes for this. One thought I have is that Xcode keeps a lot of build artifacts and project-related data in its derived data folder. This can often lead to stale or incorrect information being used by Interface Builder. Have you try to go to Product > Clean Build Folder (or Cmd+Shift+K). Do this for both projects/targets if they are in the same workspace. Even if your NIB files are separate, the custom classes (e.g., your AppDelegate subclasses, custom NSWindowControllers, or NSView subclasses) that are referenced in those NIBs might be accidentally included in the wrong target. If a class from App A is somehow included in App B's target (or vice-versa), Interface Builder for App B's NIB might try to instantiate or show properties from App A's version of that class?

Thanks for providing the details. Yeah, the initial synchronization for a large dataset can take a long while. That's kind of a known issue, but I'd still suggest that you file a feedback report with your concrete use case to voice your need – If you do so, please share your report ID here. Regarding the batch size, CloudKit does have a limit on the records per modify and per query operations. Under the limit, the real batch size is up to the server to decide. There is no API for an app to configure the size. Best, —— Ziqiao Chen  Worldwide Developer Relations.

Thanks a very big lot for the detailed explanation! All clear now. You're very welcome. (I wonder if it might be perhaps worth the effort to add this information to the standard HomeKit documentation.) If you want to see this improve, please file bugs! __ Kevin Elliott DTS Engineer, CoreOS/Hardware

When an app is not in the foreground, any advertising by it is done on a best effort basis, and it cannot be guaranteed, and there are some changes and limitations to the advertised data. As Bluetooth is a shared resource, when other apps and system resources need to use Bluetooth, advertising for apps in the background will slow down, and may even stop for short periods of time. To perform certain peripheral role tasks while in the background, you must include the UIBackgroundModes key with the bluetooth-peripheral value in your app’s Info.plist file. That said, you should be aware that advertising while your app is in the background operates differently than when your app is in the foreground. In particular, when your app is advertising while in the background: The CBAdvertisementDataLocalNameKey advertisement key is ignored, and the local name of peripheral is not advertised. All service UUIDs contained in the value of the CBAdvertisementDataServiceUUIDsKey advertisement key are placed in a specia

Thank you for sharing your experience with Universal Links. I find it intriguing. However, I would like to clarify that other browsers may not implement the Universal Links functionality, and they are not required to be your default browser. Therefore, I always recommend testing the URL with the Note apps, for instance, to ensure that it opens the app registered with the Universal Link. So may I ask more information about what you are trying to accomplish and how you test it? Universal links are designed to open directly in the corresponding app if the app is installed. If the app is not installed (or if things are configured incorrectly), the universal link should gracefully fall back to opening in the browser (usually the default browser). How do you test? Do you try to send the same universal link to the app directly using the default browser, outside the context of your app's flow or do you open it from notes, messaging, or some other interface. See if it works. This helps determine whether it's truly an

Coming back to the ‘HomeKit outside of Mac Catalyst’ issue, I wrote: [quote='874075022, DTS Engineer, /thread/813853?answerId=874075022#874075022'] I don’t support HomeKit, so I’m gonna ask DTS’s resident expert if they have any context for that. [/quote] So, yeah, I chatted with my colleague about this on Friday and it is as you say: HomeKit is simply not supported on the Mac outside of Mac Catalyst. You’re not the first person to bump into this. If you’d like to track this issue, I recommend that you file a bug and ask that it be marked as a duplicate of FB11762771. That way you’ll be notified if this changes in the future. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='874485022, qb_s, /thread/814022?answerId=874485022#874485022, /profile/qb_s'] disable logging for all other processes/subsystems … that tend to be noisy too? [/quote] Yeah, I could see how that might actually help in your situation. [quote='874485022, qb_s, /thread/814022?answerId=874485022#874485022, /profile/qb_s'] I filed an improvement request anyway (FB21839588). [/quote] Fair enough. I’ll be interested to see how that pans out (-: [quote='874485022, qb_s, /thread/814022?answerId=874485022#874485022, /profile/qb_s'] And what of log stream …? [/quote] Honestly, I’m not sure what’ll happen in that case. Live streaming of the full system log has a significant impact on system performance, to the point that we even added a little warning about it in Console (“Stream log messages will impact system performance.”). My concern here is that, regardless of whether log entries get dropped or not [1], that performance impact could perturb the system to the point where the bug you’re hunting no long

[quote='814396021, Smitty at HP, /thread/814396, /profile/Smitty+at+HP'] Can Apple update its example code to fill in these gaps … ? [/quote] If you want to see improvements in the sample code, I recommend that you make it official by filing an enhancement request. Please post your bug number, just for the record. Having said that, it’s tricky to create sample code for this scenario because: Developers expect to be able to run sample code. But such a sample would be tied to a specific accessory. In the meantime, I have a couple of random notes: It’s well worth watching WWDC 2025 Session 228 Supercharge device connectivity with Wi-Fi Aware, which covers both the device-to-device and device-to-accessory cases. The Accessory Design Guidelines for Apple Devices, available from Developer > Accessories, has a Wi-Fi Aware section that outlines Apple’s requirements in this space. I’m not tracking the accessory side of this in great detail, so I’m not sure how well this works out in practice. Share and Enj

Thanks for filing FB21810618. That’s likely the best path forward here. Having said that, I noticed that there’s no sysdiagnose log attached to your bug. That’s gonna make it hard to investigate. I recommend that you follow the VPN (Network Extension) for macOS instructions on our Bug Reporting > Profiles and Logs page to enable additional logging on your macOS 14 test Mac, reproduce the problem, grab a sysdiagnose log, and attach that to your bug. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com