file uri scheme

unique_cfref is just a std::unique_ptr wrapper that calls CFRelease when we go out of scope. Looks like something in OpenDirectory tries to access released data (weak references and delayed processing?). The problem seems to occur on macOS 15. No, that's not what's going on, though I can see why you might have thought that. The key details here are this note in the middle: 0x000166890010 is located 10946 bytes after 789838-byte region ASAN includes information about nearby allocations because there often is a relationship between allocations that are close to each other. However, the problem here is that 10946 bytes is 10KB, which isn't really all that close. It's possible there is some connection, but it's more likely that this was just the closest block ASAN could relate, not that they were actually tied to each other. Similarly, what the code is actually doing is converting raw bytes it received through XPC into plist data (Array/Dictionary/String/etc.), which your larger app wouldn't really have ever had

Hello! This is a known issue. To be notified when the fix is ready, you can file a feedback report and reply to this thread with the feedback ID. Thanks!

I understand now, thanks for your patience. Unfortunately, this means that the only way for this to work is having the Gurobi libraries' code and incorporating mmap there, because that's where the memory-heavy node-files are created and put in memory. I don't know anything about their product, so it might be worth raising the issue with them. Too bad this is not open-source software, and therefore this is impossible. Is there an alternative to mmap to perhaps squeeze some extra space in the disk? No, not really. The limit you’re hitting is actually a system-wide cap enforced by the kernel. You're hitting it because your single process is using an extraordinarily large amount of memory, but you'll see exactly the same failure with more processes using smaller amounts of memory. I was wondering if renicing the process to, say, -20, can have some indirect benefits... No, not really. Theoretically, you could free up some additional memory by reducing total system activity, but you're using so much memory

We know how bug reporting is important for good software quality. We use Feedback Assistant each time we encounter an issue. Then, we also know we never get progress reports, but we had a majority of issues solved. It's worth it. Nothing changed in our infrastructure. The only changes were macOS 26.2 and Xcode 26.2. And has we had checked, and Apple Care rechecked, we have no other sync issues, just the .xcodeproj file, and now the new project .xcodeproj file. I have updated the FB to include the zip of the file with the issue to help your Xcode team. Thank you very much for you answers.

Have you filed a bug on this and, if so, what's the number? __ Kevin Elliott DTS Engineer, CoreOS/Hardware

Thank you for your prompt response and for attempting a new project in Xcode. Your efforts are commendable, and I appreciate you filing the bug. I started to think that could be some sync issues due a firewall or internet settings? Do you know when stopped working and the change was just a new version of Xcode or could be something related to the infrastructure? In any case, the team for Xcode cloud is highly skilled and extremely nice as well and will swiftly identify the underlying issue. However, I kindly request your patience, considering the upcoming time of year and holidays. Your prompt attention to this matter is crucial for a timely resolution. You can see the status of your feedback in Feedback Assistant. There, you can track if the report is still being investigated, has a potential identifiable fix, or has been resolved in another way. The status appears beside the label Resolution. We're unable to share any updates on specific reports on the forums. For more details on when you'll see up

Thnak you for you quick reply. The problem occurred in a 3 years old project after updating to macOS 26.2 (25C56) and Xcode Version 26.2 (17C52). I've created a new project : same error! All files synchronize except the .xcodeproj file. There is 19GB free on iCloud Drive, and 59GB free on the Mac. If I open the original .xcodeproj package file, copy all the included files in a folder outside, then they all synchronize on iCloud Drive except project.xcworkspace Here are the attributes of this file com.apple.FinderInfo 32 com.apple.fileprovider.fpfs#P 4 com.apple.lastuseddate#PS 16 com.apple.macl 72 It's also a package, but the time if copied outside all its file are correctly synchronized to iCloud. A feedback had been opened : FB21363976. It includes a zip with the file not syncing. Thank you.

Thank you for your post and description. It appears that Apple Care support provided you with a valuable insight that seems to be the underlying issue. Have you attempted to create a new project file using the latest version of Xcode? This simple test can help identify whether your project file contains settings that require correction. Additionally, I recommend verifying that you are logged into the same Apple ID on each device and checking the available iCloud storage to ensure it is not full. Lastly, please ensure that you are utilizing the most recent version of Xcode, and identify the specific build version you are using. While I still believe that creating a new Xcode project and incorporating your existing source files can be beneficial, as it may address underlying corruption issues, I concur with Apple Care Support’s assessment that the issue lies within your existing project. Please let us know the results of your troubleshooting. Albert Pascual
  Worldwide Developer Rela

Thanks for the suggestion! We’re looking into this. While we can’t comment on future updates, we recommend filing a feedback report so that you can be notified if we implement any changes. In the meantime, you can also find more details about archiving asset packs here in App Store Connect Help.