missing package product

It is rather rare to reproduce and explain bugs Some users have remote logs for calls. Log for iOS 26.2.1 & identifier iPhone18,2 To understand: there is no inital providerDidBegin for first CXProvider as logger misses early logs if our logic triggers CXProvider invalidation so Provider to invalidate nil if iOS triggers CXProvider invalidation so Provider to invalidate Optional() func invalidateProvider(..) invalidates provider when either nil or equal to current provider second call providerDidReset happens after invalidateProvider as delagate is not set to nil Pls keep an eye on CXProvider 0x10e0463c0. A very first one 12:45:33_473-730:[CallsProviderDelegate.swift:47 -- providerDidReset(:)] providerDidReset 12:45:33_478-738:[CallsController.swift:307 -- invalidateProvider(:)] Provider to invalidate Optional() 12:45:33_478-739:[CallsController.swift:308 -- invalidateProvider(:)] Current provider 12:45:33_488-742:[CallsProviderDelegate.swift:47 -- providerDidReset(:)] providerDidReset 12:45:33

knytko wrote: Yes, reported today with ID FB13636366. Thanks for that. Annoyingly, that bug got lost in our system and there’s been no progress on it. I’ve taken steps to get it on the right track. Lanmac, Are you developing an app that contains a system extension? Because reading through your post it doesn’t look like you’re hitting the issue being discussed here. If you’re having a problem with the Finder that’s unrelated to app development, I recommend that you bounce over to the Apple Support Community, run by Apple Support. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='815340021, Leo_Nagano, /thread/815340, /profile/Leo_Nagano'] If this is a known limitation or bug in how Xcode validates NE entitlements for Developer ID [/quote] Indeed, this is a known bug in Xcode’s code-signing support )-: [quote='815340021, Leo_Nagano, /thread/815340, /profile/Leo_Nagano'] is there a recommended workaround? [/quote] You have to sign your product manually, outside of Xcode. Exporting a Developer ID Network Extension has all the details here. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Apple can fairly say: “Agents shouldn’t directly edit our serialization format.” But if they advertise agentic workflows and the agent can’t reliably do core build/debug tasks (target build settings, linking, schemes), then the product gap is real. Agentic workflows require a closed loop: apply build-setting changes → build → fix → repeat. If the only exposed interface is “chat + inline code edits,” it’s not agentic for build/debugging. Therefore Apple needs a supported automation surface (typed project actions with preview/undo), regardless of how ugly project.pbxproj is. Expected: Agent can apply target/scheme/build-setting changes (typed + preview/undo), run build, iterate on failures. Actual (Xcode 26.3 RC): Agent mostly suggests or edits source files; can’t reliably adjust the build/ debug configuration loop for multi-target/C++ integration. C/C++ integration is where an agent should shine because it’s repetitive, error-driven, and configuration-heavy. A “real” agentic C++ loop in Xcode would ne

@Vincent_Galilieo is right that way it works just make sure your external package doesn't take too much space as the size limit for your zip file is max 25 mb. So @advaitconty just download your packages locally and then create an folder besides your playground and save it there and then while adding packages in Xcode make sure to add that package with the same relative path. ( which is default if you are not editing package.swift file yourself ).

@kelin Hello, my friend, I have also encountered the same problem. However, for my new Icon, I used a normal PNG image and the full-size format. But when I published it to the AppStore build, it still reported an error indicating that the resource was missing and could not be found.

Hi Kevin, Thank you for your feedback and the feedback from the engineering team. We have integrated all suggestions from your forum posts (ID: 875288022, 875587022) and the Bug Report, and have conducted a full round of testing. Below is our current status. We now perform a memset on SCSIUserParallelResponse in the ISR and correctly populate the version, fControllerTaskIdentifier, and fBytesTransferred fields. The ISR now differentiates between Bundled/Legacy modes, calling BundledParallelTaskCompletion (without release()) and ParallelTaskCompletion (with release()) accordingly. The aforementioned fixes have resolved all 0x92000006 Panics and DEXT Corpse crashes. Unplugging the hardware or deactivating the DEXT while the driver is in a hung state no longer triggers a panic. We are in a logical deadlock. The kernel dispatches a probe command before UserCreateTargetForID returns, and both of our methods for handling this command result in a permanent hang of the registration process: Scenario A (Reporting SUCC

I have run some tests on my copy of StoreKit testing project. When the app is not active, and a renewal comes through, it will be unfinished. The listener task you have in Transaction.updates might not catch it. Question: Does your app handle unfinished transactions? You need to listen for Transaction.unfinished, and finish any verified transactions. Either call it on the next launch, or create another Task to listen for unfinished. func processUnfinishedTransactions() async { for await result in Transaction.unfinished { switch result { case .verified(let verified): // Always finish verified transactions await verified.finish() case .unverified(let unverified, _): // Handle unverified } } } If you check the Understanding StoreKit Workflows sample from WWDC25, notice they have 3 things going on in the Store.swift file: Task(priority: .background) { // Finish any unfinished transactions -- for example, if the app was terminated before finishing a transaction. for await verificationResult in Transaction.unfinish

So this method falsely returns NSURLRelationshipSame for different directories. One is empty, one is not. Really weird behavior. Do you know where/what the directories were? The problem here is that there's a pretty wide variation between the basic case of a bunch of files and directories sitting on a standard volume and the range of ALL possible edge cases. Two file path URLs pointing to two different file paths have the same NSURLFileResourceIdentifierKey? Yes, this is possible. As one example, the data volume basically ends up in the hierarchy twice meaning that, for example, the path /System/Volumes/Data/Users/ and /Users/ are in fact the same directory. And, yes, getRelationship returns NSURLRelationshipSame for those directories. Now, this: One is empty, one is not. ...is definitely weirder. Ignoring the cache issue below, I don't think you could do it within a standard volume, but you might be able to do it using multiple volumes, particularly duplicated disk image and/or network file systems. However,