missing package product

Can someone please explain why Mac app packaging is so farcically convoluted? Windows app packaging can be picked up in an hour or so. But I've spent longer trying to fathom how to package the Mac version than I did building the app. And it's not done with me yet. Every single line of code requires a deep dive into a new, unrelated skillset. So, it’s sidebar after sidebar. Kafka’s ‘The Trial’ comes to mind. Why does it have to be like this?

I just integrated a first Swift package into my app. I was looking for committing it, but found out that the package is downloaded into the DerivedData when it's resolved. I was wondering why that is, and if there's a way around it? Can we specify another folder? In my team we commit the pods with our code (so we can go back and build an old version with the exact versions of the pods). It seems odd to include that in the DerivedData. Also, it is not rare that we need to delete that folder, so it seems not so productive to delete and redownload that each time...

We have an app where people can buy guides and guides in bundles. They pay x for a single guide and y for a bundle. x always has the same price and so does y.We have over 300 guides and over 100 bundles. When a user purchases a product we store this transaction in our own database because the user can also login to our website and android app. Is it possible to use a consumable product to buy a bundle? So a person buys a consumable product (guide), when we get success we store the purchase in our database and then consume the product.

I've developed an SPM module in which I have a CoreData model defined as a xcdatamodeld file and I'm having trouble executing tests from the command line, which I want for a CI integration. In the package I load the model by constructing a URL using Bundle.module.url(forResource: ModelName, withExtension: momd). This works when building and testing in Xcode. When executing commands such as swift test from the terminal however, it doesn't, as Bundle.module.url(forResource:withExtension) fails to find the file. Comparing the build artifacts between Xcode's DerivedData and SPM's .build I see that both produce a PackageName_PackageName.bundle but while the Xcode version contains a momd file the SPM version contains an unprocessed xcdatamodeld file. I've tried adding the xcdatamodeld as an explicit resource in the Package.swift file such that the package target now includes resources: [.process(Resources/ModelName.xcdatamodeld)] as an argument. This does not impact the Bundle output. Any ideas ho

Hi, I've got a Swift Framework with a bunch of Metal files. Currently users have to manually include a Metal Lib in their bundle provided separately, to use the Swift Package. First question; Is there a way to make a Metal Lib target in a Swift Package, and just include the .metal files? (without a binary asset) Second question; If not, Swift 5.3 has resource support, how would you recommend to bundle a Metal Lib in a Swift Package?

The steps followed were: Signed the .app Notarized the .app inside a .zip Unpacked the .zip Stapled the .app Created a package using Packages Sign the package Notarize the package (both as .pkg and .zip) The result of the final step always comes out to: { tlogFormatVersion: 1, tstatus: Invalid, tstatusSummary: Archive contains critical validation errors, tstatusCode: 4000, tissues: [ tt{ tttseverity: error, tttcode: null, tttpath: App_Signed.pkg.zip/App Signed.pkg/App.pkg Contents/Payload/Applications/App.app/Contents/MacOS/App, tttmessage: The signature of the binary is invalid., tttdocUrl: null, tttarchitecture: x86_64 tt} t] } I read a number of forum posts and guides and this seems to take a hold of all the requirements. Did I miss something?