“missing package product”

Apple Transporter.app report this issue: Asset validation failed (90237) The product archive package's signature is invalid. Ensure that it is signed with your 3rd Party Mac Developer Installer certificate. In the post https://developer.apple.com/forums/thread/680438 Quinn “The Eskimo!” reply: For the Mac App Store you need: Apple Development: TTT (or the older Mac Developer: TTT) for day-to-day development 3rd Party Mac Developer Installer: TTT for signing the installer package you submit to App Store Connect 3rd Party Mac Developer Application: TTT for signing the code inside that installer package In https://stackoverflow.com/questions/29039462/which-certificate-should-i-use-to-sign-my-mac-os-x-application Apple Codesigning Certificate Types Mac App Distribution 3rd Party Mac Developer Application: Team Name Used to sign a Mac app before submitting it to the Mac App Store. Mac Installer Distribution 3rd Party Mac Developer Installer: Team Name Used to sign and submit a M

I know that Xcode doesn't have explicit support in the UI for Package Registries yet, but can use packages referenced by ID if the registry is set up through the CLI. I also see that xcodebuild has support for SCM to registry transformation (resolving and downloading packages through a registry, even if the packages are referenced using their Github URLs) through command line arguments like -defaultPackageRegistryURL and -packageDependencySCMToRegistryTransformation. Is there any way to achieve the same thing in Xcode itself?

I have a swift Package, and I have some extra .h header to be shipped with the package, but this files are not copied to the build destination. It would be nice to have this files included as header in the modulemap file

We provide our software on a single dmg that contains several pkgs that are then used individually on customer computers. That is, the installers will usually not be run directly from the dmg. So I think the correct approach is to notarize and staple each pkg before creating the dmg. In this case, is it unnecessary to notarize the dmg?And a similar question / request for clarification: I understand that notarizing a pkg will also notarize the apps contained therein, but is it the case that we only have to staple the pkg, and this will include whatever is needed for the apps as well?Thanks for any insights,Mark

Hi, I am building a new app in the App Store - the app is not live yet. I have setup an annual subscription product in AppStore Connect. Our problem is that we are unable to retrieve the product from our app - we've made sure that there are no missing metadata (e.g. price, availability). Has anyone encountered before? Appreciate any help provided. Thanks

I have an iOS app that includes a local Swift package. This Swift package contains some .plist files added as resources. The package also depends on an XCFramework. I want to read these .plist files from within the XCFramework. What I’d like to know is: Is this a common or recommended approach—having resources in a Swift package and accessing them from an XCFramework? Previously, I had the .plist files added directly to the main app target, and accessing them from the XCFramework felt straightforward. With the new setup, I’m trying to determine whether this method (placing resources in a Swift package and accessing them from an XCFramework) is considered good practice. For context: I am currently able to read the .plist files from the XCFramework by passing Bundle.module through one of the APIs exposed by the XCFramework.

To ship a product outside of the Mac App Store, you must notarise it. The notary service issues a notarised ticket, and the ultimate consumer of that ticket is Gatekeeper. However, Gatekeeper does not just check the ticket; it also applies a variety of other checks, and it’s possible for those checks to fail even if your notarised ticket is just fine. To avoid such problems showing up in the field, test your product’s compatibility with Gatekeeper before shipping it. To do this: Set up a fresh machine, one that’s never seen your product before. If your product supports macOS 10.15.x, x < 4, the best OS version to test with is 10.15.3 [1]. Download your product in a way that quarantines it (for example, using Safari). Disconnect the machine from the network. It might make sense to skip this step. See the discussion below. Install and use your product as your users would. If the product is signed, notarised, and stapled correctly, everything shou

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 work in music production, the way the tools are set up is we use many tools (plugins) inside one larger app (a DAW), as such the process of setting up a machine to do work involves running 50-100+ different installers to get all tools installed. I'd like to write a small app that will automate the install process. I have a working approach for this where all steps work when run individually in terminal or via AppleScript, but as I create one unifying app I am running into an issue where any app I create in Xcode is not allowed to mount DMGs or give commands to terminal (even if I make a build app package and move it out of the Xcode directory, and even if I give explicit permission via settings) and if I try to have the app try to do the works via terminal it also can't seem to access terminal. I think there are some limitations I'm missing here. Any tips?

I have a code-signed app bundle that I need to convert to a *.pkg for submission (via Transporter) to the Mac App Store. This has worked fine in the past, but not after rebuilding the computer and recreating my certificates. (I had to downgrade to Catalina from Big Sur if that's relevant.) The command that fails is: $ sudo productbuild --component /Applications/Hollows.app --sign 3rd Party Mac Developer Installer: Gerald Schmidt (FBCSA85C72) hollows.pkg This leads to the error: productbuild: error: Cannot write product to hollows.pkg. (Could not find appropriate signing identity for “3rd Party Mac Developer Installer: Gerald Schmidt (FBCSA85C72)”.) According to Xcode and Keychain, this certificate is valid and the private key is present. However, if I validate it from the command line, I get: $ security find-identity -p macappstore ... 202B1775FC64882C215BCC8D52A2156038AEBD1C 3rd Party Mac Developer Installer: Gerald Schmidt (FBCSA85C72) (Missing required extension) Do I need to rec

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.