“missing package product”

A) Sell the credits in packages and discount the larger packages.1 credit for $105 credits for $4525 credits for $20050 credits for $300B) have a set of products available for purchase but only display those products when the user has made previous purchases:User has no previous purchases: (show only products A and B) 1 credit for $10 (Product A) 10 credits for $100 (Product B) - limit quantity 2User has 25 previous purchases: (show only products C and D) 1 credit for $8 (Product C) 10 credits for $80 (Product D) - limit quantity 2User has 50 previous purchases: (show only products E and F) 1 credit for $6 (Product E) 10 credits for $60 (Product F)

You have to set Add To Target to None when you don't want a Package Product. It work for me.

Same situation here, got around the problem by adding library A as a new product of the package. e.g. let package = Package( name: PackageB, products: [ .library( name: PackageB, targets: [PackageB]), .library( name: LibraryA, targets: [LibraryA]) ], targets: [ .binaryTarget( name: LibraryA, url: https://url.to/LibraryA.xcframework.zip, checksum: checksum), .target( name: PackageB, dependencies: [ LibraryA ]) ]) Then add both libraries to App's Frameworks, Libraries, and Embedded Content. Still would like a better solution.

Are these packages of yours dependencies in Package.swift, or do they live locally alongside your project? If the former, then my answer applies (make sure to .gitignore .swiftpm from whatever repo you're storing your packages in). If the latter, then this is standard behavior from Xcode as it autogenerates schemes for all local package products.

EVERY DAY my Xcode welcomes me with missing packages problems. Yes, Reset Package Caches works but really Apple, fix this horrible issue, still present in Version 14.3 (14E222b)

Same issue here. After trying everyone's suggestions from this thread and coming up dry, I finally narrowed down the needle-in-a-haystack. In my case it was a Swift Package. Debug builds built fine, but Release builds (with optimizations) caused the Swift compiler to crash with the same stack trace and error: Abort trap: 6 as others have mentioned. The culprit? A single missing import statement in one of the package's .swift files. To elaborate the particulars: PackageA (crashed compiler) has PackageB as a dependency, which in turn has PackageC as a dependency. All three packages show up in the dependency pool of course. PackageA was accessing methods from PackageC without actually using an import PackageC statement (possibly by way of PackageB exporting types from PackageC in some of its interfaces). The missing import statement was forgotten because compilation succeeded in Debug builds and development and testing was only ever done in a Debug build. It wasn't un

Hi @eskimo, Thank you for sharing me the debug process. And you are right, this file is indeed not signed. With this lead I found that this file is used to make an installer package before it is signed. This explains the issue here. So my next question is here we have two schemes, one for the app and the other one for the installer package. During the execution of the installer package, we were trying to copy the product of app scheme. We have a dependency within installer package scheme. And the app scheme is in the dependency. But it looks like it could not guarantee that app is signed before used. Do you know is there any way to make sure that the product of app scheme is signed before used/copied?

I'm seeing the same: 100% packet loss when pinging sandbox.itunes.apple.com and yet the developer system status shows everything all green. Retrieving products seems fine, but doing anything substantive—like purchasing products or restoring purchases—is very hit & miss. Mostly miss.

The mediafilesegmenter is a reference implementation of an HLS packager (for VOD). It is not intended to be used in a production environment; it is designed to produce working examples and as a validation tool for an actual production workflow.

We are encountering the same issue since Xcode 16. We run XCTest and Swift Testing. For us it is flaky, sometimes some local Packages (SPM) are missing in the .xcresult file, resulting in a Coverage of 0% for these packages