missing package product

Seeing the same issue on a couple of models we own - audio processing. Output diverges from 26.0.1 and 26.1. On our tests we have seen that a couple of models work as expected on CPU but present corrupt/degraded data on NPU/GPU. Would also like to know if Apple is aware of thjis issue as it is not only affecting our development but also our customer experience as our models are shared with clients and are used in production.

“Allowed” is a tricky word, because it covers both business and technical limitations. I don’t work for App Review and thus can’t offer definitive answers about the former. I recommend that you review their published guidelines. But ignoring that, the technical aspects are also tricky. The basic idea of updating your Core Spotlight index in the background should be feasible. The sticking point is getting access to the documents. The cool thing about Spotlight importers is that they’re tightly sandboxed. So the system is able to find all the user’s documents and present them to the importer. The importer is sandoxed so info can’t leak to the app, and the app never gets access to the user’s entire file system. Neat-o! You lose that if you do this indexing yourself. You will be able to access any documents in your app’s container, and any documents which you were previously granted access to by the system [1], but you won’t necessarily be able to see all documents. Share and Enjoy — Quinn “The Eskimo!”

[quote='864642022, oddeyed, /thread/805992?answerId=864642022#864642022, /profile/oddeyed'] I am looking at performing this check on file system paths which I can consume as an input to my product. [/quote] OK. But I’d like more info about your goal. Is this a security product? Or a developer tool? Or something else? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Is this only affecting new versions of your product? Or are you seeing it with old versions? That is, if you take a version of your product built, say, 6 months ago and try to install it on macOS 26.0 and macOS 26.1, do you still see it work on the former and fail on the latter? If so, you should file a bug about that, making sure to include: A copy of the installer package A sysdiagnose log taken shortly after seeing the failure Once you’re done, please post your bug number. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

When the notary service actually goes down, DevForums tends to light up with complaints. I suspect that this issue in something specific to your product. Looking at your older thread, it shows that notary responded, but with an error complaining about the format of your submission. Is that case again now? If so, please post your notary log again and I’ll see what I can figured out. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

iOS 26.1 is released, iOS 26.2 beta appeared, but no signs that UIManagedDocument loses @MainActor. Does anybody have the same concern? Anybody uses UIManagedDocument and wants to transition to Swift 6? Or, perhaps, already use it?

Is there no solution for this? I checked your other thread as well. Is there a way for me to remove the third party libraries from my SDK? I run the below commands to generate the SDK. xcodebuild archive -project Abc.xcodeproj -scheme AbcSDK -configuration Release -destination generic/platform=iOS Simulator -archivePath BuildArtifacts/iossim.xcarchive | tee build.log xcodebuild archive -project Abc.xcodeproj -scheme AbcSDK -configuration Release -destination generic/platform=iOS -archivePath BuildArtifacts/ios.xcarchive | tee build.log xcodebuild -create-xcframework -framework BuildArtifacts/iossim.xcarchive/Products/Library/Frameworks/AbcSDK.framework -framework BuildArtifacts/ios.xcarchive/Products/Library/Frameworks/AbcSDK.framework -output Frameworks/AbcSDK.xcframework As soon as I run, it gives me the list of resolved source packages that includes all the third party libraries. If I try removing the libraries, it gives error at all the import statements in my cod

We have found the cause of the issue. Below are our current entitlements: com.apple.developer.endpoint-security.client com.apple.developer.networking.networkextension content-filter-provider-systemextension dns-proxy-systemextension app-proxy-provider-systemextension com.apple.developer.system-extension.install com.apple.security.application-groups $(TeamIdentifierPrefix)xxxxxx com.apple.security.get-task-allow com.apple.security.network.client com.apple.security.cs.allow-unsigned-executable-memory We discovered that com.apple.developer.endpoint-security.client and com.apple.security.cs.allow-unsigned-executable-memory are in conflict. Currently, our approach is to download wasm files from the server to the local machine and load them dynamically at runtime, so we cannot package the wasm files into the Contents/Resources directory inside the app bundle. Could you please advise how to resolve this problem?

Hi Apple team, Just checking in to see if there’s any update on this issue. The SKOverlay still opens the default product page instead of the configured custom product page on iOS 26. This behavior persists across multiple devices and builds. Any guidance or confirmation from Apple Engineering would be appreciated. Thank you