missing package product

Apologies, the missing 's' was a typo, I double-checked on my terminal's history and and when typing there I was correctly using 'args'. Could it be that Sequoia has a bug preventing the boot-arg to be effective on th eVMM's behaviour?

Whether querying by recordName should work in production CloudKit Yes, in case you have the appropriate indice in the CloudKit production environment. What specifically causes the “Field recordName is not marked queryable” error in TestFlight builds The error is triggered when you try yo query a CloudKit record type and the type doesn't have the index for its recordName field. If the error only occurs in the production environment, which is by default used by a TestFlight build, and not in the development environment, it will indicate that the CloudKit schema in the development environment is not completely deployed to the production environment. To address the error, try to use CloudKit Console to add the indice, as discussed here and here. What steps are required to ensure CloudKit schemas are correctly deployed for cross-platform sync If you can use CKTool to dump the schemas, as discussed in Automate CloudKit tests with cktool and declarative schema, and then compare an

I ran the following commands in Terminal: cp /System/Library/CoreServices/Finder.app/Contents/Resources/Invitation.aiff ~/Downloads/Invitation.aiff xattr ~/Downloads/Invitation.aiff chflags -v 0 ~/Downloads/Invitation.aiff xattr ~/Downloads/Invitation.aiff but the output of each of these commands was empty, so again it seems that even with the chflags -v 0 Invitation.aiff command no extended attributes are revealed on that file. I tried copying the same System/Library/CoreServices/Finder.app/Contents/Resources/Invitation.aiff file to a FAT volume connected via SMB, and the results are the same. I'm afraid we'll never know how that file (and hundreds others) got to the SMB volume. The user told me they're currently unable to reproduce the issue and are tired of running experiments, so I guess that's it for now... until I'll hear from the next user having the same issue. I have lost count of how many users have already contacted me about the exact same issue and how many days I've already spent trying

[quote='874764022, TotalPhase, /thread/814226?answerId=874764022#874764022, /profile/TotalPhase'] We haven't setup a VM yet. [/quote] I strongly recommend that you do. It has some key benefits: It strictly constrains the problem space. For example, if you have a bug with identifying the correct broadcast interface [1], such a problem will go away in a VM because there’s only one interface. So, if the local network alert always shows up in a VM but fails on real hardware, it’s likely that this isn’t an issue with local network privacy per se, but something in your code. It makes it much easier to run tests in isolation. You can quickly iterate on your tests, creating a new clone of your ‘clean’ VM each time. It allows you to test across OS releases. If you think something broke in, say, macOS 26.2, you can easily test 26.1, 26.2, and 26.3 beta, all in parallel. Debugging these problems on real hardware just makes things harder. [quote='874764022, TotalPhase, /thread/814226?answerId=874764022#874764022, /profil

[quote='874797022, Xunreal75, /thread/814501?answerId=874797022#874797022, /profile/Xunreal75'] I find this termination behavior too aggressive [/quote] My role here on the forums is to help developers create products for Apple platforms as they currently stand. If you’d like to see things change in this space, you are free to file a bug report [1] describing what you’d like to see change. See my Bug Reporting: How and Why? post for more details about that process. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com [1] Or enhancement request. In cases like this the distinction is one of perspective.

Thank you for the detailed information. To investigate this behavior thoroughly, could you please file a report using Feedback Assistant and include a sysdiagnose log? Part 1 How to File the Feedback Report Navigate to Feedback Assistant and log in with your Apple Developer account. Choose iOS & iPadOS for the product. For the report details, please include the detailed description and steps to reproduce from your post as well as the sysdiagnose. Part 2 Capture and Attach sysdiagnose Go to the Bug Reporting - Profiles and Logs page. Follow the instructions to install the necessary profiles for App Store issues. Once the profiles are installed, reproduce the purchase issue in your app and capture the sysdiagnose. Attach the resulting log file to your Feedback Assistant ticket. Part 3 Share the Feedback ID After you submit the report, please share the Feedback ID here to find your report and track its progress.