“missing package product”

I want to implement in-app-purchase in iOS App. I have a list of records that have digital audio assets. I want to implement like a product id com.product.id and using this product id i want to implement and user can purchase n number of products using in-app from app.As Example : user1 can purchase product xyz of price $9.99 having the same product id com.product.id. then same user1 can purchase product abc of price $9.99 having same product id com.product.id.

Is there a way to purchase the same app and distribute it among multiple users using one link or a code (a package of downloads) and not paying them one by one?

HiWwhat's the difference between Frameworks and Swift Packages, both create reusable code that we can use in another programs or I'm wrong ?

Hi All,I have a Canon printer installer package “.pkg” and couple of Apple Scripts “.scpt” .I like to combine them to a single installer package.Here are the sequences:run Apple1.scptrun Canon printer installer.pkgrun Appl2.scptPlease advise,Thanks in advnace,Abi

I want to statically link xcframework as binaryTarget in Swift Package, but it is copied into the product as dynamic when the Xcode build. How to use xcframework in SwiftPackage and statically link it into iOS product? The Package.swift content and the project are: The WebP.xcframework is static: The Xcode Build Product's WebP.framework is dynamic:

Is it possible to validate the code signature of an installer package (.pkg) on Mac OS X 10.6? I normally use spctl for that, but spctl seems to have been released with 10.7.(I'm _assuming_ 10.6 has a concept of a signed installer package, because when I open it, the UI is able to see the certificate and say that it's valid)

Hello, I am currently learning SwiftUI through a paid course and am working on integrating Firebase into my project. While trying to add the Firebase package through Xcode, everything seems to work fine except for the fact that I am unable to find the FirebaseFirestoreSwift package. I am using the latest versions of both Xcode and macOS. I have attached a screenshot from the package manager where I couldn't locate the FirebaseFirestoreSwift package. Could you kindly assist me in resolving this issue? How can I correctly add this specific package to my project? Thank you for your support.

Hi,Notarization of .pkg files has stopped working for me. Basically, the .pkg file is notarized but the contents are not. The notarization log shows the following response:{ logFormatVersion: 1, jobId: [jobId-edited], status: Accepted, statusSummary: Ready for distribution, statusCode: 0, archiveFilename: WiFiExplorerPro_2.3.pkg, uploadDate: 2019-10-25T22:34:38Z, sha256: [sha256-edited], ticketContents: [ { path: WiFiExplorerPro_2.3.pkg, digestAlgorithm: SHA-1, cdhash: [cdhash-edited] } ], issues: [ { severity: warning, code: null, path: WiFiExplorerPro_2.3.pkg, message: This archive is corrupt, and cannot be unpacked for analysis., docUrl: null, architecture: null } ] }The same packaging/notarization workflow was working for me two weeks ago but now it ends up with this error. Well, a warning, but the error comes later when trying to staple the .app inside the .pkg, since it wasn't notarized. As far as I know, nothing changed on my side, as I sai

The question about how to notarise an installer package (.pkg) containing a KEXT has come up on a number of threads [1] over the past few weeks. Unfortunately my answers have been less than clear, so I sat down with the notarisation team to fix that. The fundamental question here is the order in which you notarise things. Do you:Sign the KEXT, wrap the KEXT in a signed installer package, then notarise the package, then staple the ticket to the package (option A).Sign the KEXT, then notarise it, then staple the ticket to the KEXT, then wrap the KEXT in a signed installer package, then notarise the package, then staple the ticket to the package (option B).We generally recommend option A, because option B requires multiple round trips to the notarisation servers.For installer packages that don’t contain a KEXT, this is the end of the story. For installer packages that contain a KEXT, there is one extra gotcha. The gotcha, a

I've updated my Swift Package, PixelKit, to Swift 5.3. I tagged my commit with 1.1.1 and pushed to origin. Tho when trying to add it to another package, it failed to resolve dependencies: because PixelKit >=1.0.13 contains incompatible tools version and root depends on PixelKit 1.1.1..<2.0.0, version solving failed. Here's how I include it: .package(url: https://github.com/hexagons/PixelKit.git, from: 1.1.1) I'm not sure what the old tag 1.0.13 has to do with this. I'm using the same swift tools version in both packages: // swift-tools-version:5.3

When i try to install applications in my macbook pro it shows me this and m using macOS Catalina (Version 10.15.6) This package is incompatible with this version of macOS. Please Help Thank You! (:

Currently, I am working on binary XCFramework. For some time I simply hosted SPM package on GitLab but recently I had to create another repo with the same framework. The issue is that after Cloning old repo Changing its origin and URL in Package.swift Pushing it to new repo Xcode fails to resolve package graph. The error is: Resolve Package Graph failed downloading http_link_to_package.zip which is required by binary target 'package name': ~/Library/Developer/Xcode/DerivedData/bim-gxfvjyyecuziudbusqkrtpdhgrtv/SourcePackages/artifacts/package_name/package_name.zip already exists in file system I have tried: rm -rf ~/Library/Cache/org.swift.spm rm -rf ~/Library/Xcode/DerivedData reset package cache from Xcode resolve package cache xcodebuild -resolvePackageDependencies resolve in a completely new project searching for package_name.zip on the system and deleting all found packages. I do understand it is a strange use case but I don't see any reason w