I'll answer my own post. You can not upload an app bundle (my-app.app) directly to the App Store. You need to upload a signed product package (my-app.pkg) to the store. This involves multiple steps including adding an entitlements file, adding the provisioning file, signing the app bundle and then finally creating and signing the product package.
missing package product
42,924 results found
Post
Replies
Boosts
Views
Activity
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)
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.
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.
How can I get my hands on the guidelines for packaging for accessories for apple products.
I'm using Swift Package Manager on an iOS app on Xcode 11 following the instructions from https://developer.apple.com/videos/play/wwdc2019/408/Everything looks great, except Unit Tests won't work now.Screenshot: Errorhttps://www.dropbox.com/s/uws8hur4ro7bv5j/2265eb764586d19671d2e98f755533026fe76bd7.png?dl=0Screenshot: Navigatorhttps://www.dropbox.com/s/bovk30pqfa5ydw7/e7a8c97ecb1c7b30b22100c77012a65a87c91018.jpeg?dl=0Screenshot: Projecthttps://www.dropbox.com/s/p5smomqhb2n3gtc/313462f93c519e2d592792860fc62c2d1e027580_2_690x412.png?dl=0
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)
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.
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?
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
I work on an Xcode project that has three targets: macOS app CLI shared framework (mostly shared types and constants) macOS app and CLI have NIO as a dependency. When I build and run targets in the default configuration, everything works. However, I plan to bundle the CLI into the main app bundle so users can install/symlink it to make it available in their PATH. When I add the Copy Files build phase and select the CLI product, the macOS app doesn't build with the error missing required module 'CNIOAtomics' that originates in the CLI. How to configure the build considering the requirements?
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.
Situation I am working on two Swift packages, let's call them Applied and Base. Package Applied has dependency on a package Base. Both are stored on Github and the package Applied has dependecy specified as: .package(url: https://github.com/.../Base, branch: main), When I work from command-line, I mark the Base package in the Applied package directory for edditing with: swift package edit --path ../Base Base This works as expected from the command-line. Problem XCode seems to be ignoring packages in edit mode. The article Organizing your code with local packages seems not to be applicable in this case, as it assumes that the Applied package is a XCode project or a workspace, which is not - it is just another plain Swift package. Both projects are plain Swift packages. What is the way to make XCode use the local package in edit mode when none of the packages is XCode Project/Wo
In Xcode, make sure that the IAPProductIdentifier field in the ContentInfo.plist file is set to your product identifier (the product ID column in App Store Connect). When uploading the archived hosted package, select the app's bundle identifier associated with this product identifier to proceed.
ITMS-90237: The product archive package's signature is invalid. Ensure that it is signed with your '3rd Party Mac Developer Installer' certificate. How can I solve? I've revoked my mac installer distribution certificate and re-download or did many things but the same error occurs several times.