missing package product

Hello, Yes, I’m also affected. I’m using Version 26.2 (17C48) from the Developer site and running on Tahoe 26.1. My company has set up a system with LiteLLM to use multiple models. The integration works perfectly, but as soon as I close Xcode or reboot the computer, I lose the configuration and my history. See in action : https://www.icloud.com/iclouddrive/042pJSrC4mtosyDdYuH-PDFSQ#Xcode-Model-Provider-bug

Hello Quinn, It appears that we had not been properly code signing our applications, so I've spent the past month bringing our development environments in conformity and getting our software notarized through Apple. I was really hoping this was the problem and wanted to exhaust it before I came back here. Unfortunately, we are still having this issue. I have two new machines running Tahoe 26.2 that can replicate the problem consistently. They're connected over a manually configured ethernet network (both on fixed IP addresses) via an unmanaged switch. I use netcat to create an opening listening port on one and then copied the compiled version of NetworkIssueTest.app to the other from a flash drive. I get the local network permission prompt on the first time opening the app. If I reboot the computer and restart the app, it appears not to work until I toggle the permission in Privacy and Security. Sometimes it works on the second reboot, but it fails consistently on the third. Let me know if there's anything el

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

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.

Thanks for your post. We appreciate your interest in participating in the forums! These forums are for questions about developing software and accessories for Apple platforms. Your question seems related to a consumer feature from 2 OS already released and products running production versions and is better suited for the Apple Support Communities https://discussions.apple.com/welcome Albert Pascual
  Worldwide Developer Relations.

And when PTT notification arrives, saving the URL to the audio file in incomingPushResult, then downloading and playing that sound using AVAudioPlayer when didActivate is executed. It's working fine on the foreground, but when the app goes to the background, incomingPushResult is called as expected, but didActivate is not for some reason. Am I missing anything in my setup? Yes. The issue here is that you can't use AVAudioPlayer, as it does its own AudioSession activation. More specifically: It's working fine on the foreground. It works in the foreground app because the foreground app has inherent access to the audio system and can do whatever it wants. However: when the app goes to the background, incomingPushResult is called as expected, but didActivate is not for some reason. ...what happens in the background is that the same activation attempt then occurs and either fails entirely or succeeds (partially) but is then disrupted by callservicesd's own activation. Unfortunately, you'll ultimately end

Thanks for the post. Very interesting. My 5 cents if I may. It is crucial to prioritize user experience by ensuring consistency and stability in production environments. This is why feature flags, such as UIDesignRequiresCompatibility, are typically controlled by developers rather than end-users and are not exposed for arbitrary user-based toggling in production builds. This key allows developers to test the feature but does not provide a way to deploy it as it can be turned off, as explained in the documentation. Therefore, developers should refrain from rolling out new designs broadly before testing them thoroughly. Controlled feature flags enable developers to incrementally roll out new designs to ensure stability. By monitoring feedback and performance, developers can address issues before a full deployment. Apps submitted to the App Store should not contain hidden features or debugging options that alter the intended user experience for the general public. In development, set up differe