“missing package product”

So I finally settled on using a swift package to handle the command line tool project, which I added to the main app project using the package dependencies. This package executable product could be set as a dependency, and I added a run script build phase to sign the tool and embed it in the main app's Resources folder. The SPM executable product needs to be signed with --options=runtime to be embedded in a notarized macOS app. The script is pretty simple: #!/bin/bash devID=Developer ID Application: Me Myself (ASDF1234) toolPath=${BUILT_PRODUCTS_DIR}/MyTool codesign --force --options=runtime --sign ${devID} ${toolPath} cp ${toolPath} ${CONFIGURATION_BUILD_DIR}/${CONTENTS_FOLDER_PATH}/Resources

Removing type: parameter in package products helped me fix SwiftUI previews: .library( name: MyLib, // type: .static, targets: [MyLib] )

Same. MacBook M1 Pro. All SPM packages are missing from the project folder, and same error as above. Downloading the previous version :-(

I’m happy to comment on security fixes if they relate to your code. For example, if you’re writing code that’s stopped working because of a security fix, I’m happy to talk about that [1]. Re-reading your question today, that doesn’t seem to be the case here. While you are building a product for an Apple platform, that product is not having a problem on our platforms. Rather, it’s various third-party services that are complaining. I can’t comment on those. Presumably your installer package will ship either via the Mac App Store or independently using Developer ID signing. Either way, you can have Apple run its checks on it. For the Mac App Store that means simply uploading it to the store. For independent distribution that means notarising it (and, if you want to go further, testing it per Testing a Notarised Product). If it passes those checks then Apple is happy. Now it’s quite possible that these third-party services are spotting something that Apple has missed.

I solved this by deleting the IAP on iTunes Connect/App Connect and re-creating it. Wasn't able to reuse the Product ID, but I was able to upload my IAP pkg.

I looked into the Info.plist file and it seems that it is the same before and after the pack md5 ./Build-Mac-EP-New/SBSimulatorPackage/build/SafeBreach EPS.app/Contents/Info.plist ./Build-Mac-EP-New/SafeBreachMenuBar/Build/Products/Release/SafeBreach EPS.app/Contents/Info.plist MD5 (./Build-Mac-EP-New/SBSimulatorPackage/build/SafeBreach EPS.app/Contents/Info.plist) = e9be84f77bf23176a8d337fbce83aeb2 MD5 (./Build-Mac-EP-New/SafeBreachMenuBar/Build/Products/Release/SafeBreach EPS.app/Contents/Info.plist) = e9be84f77bf23176a8d337fbce83aeb2 I'm using Packages (http://s.sudre.free.fr/Software/Packages/about.html) to create the final .pkg file.

Thank you. And yes, I realized that when updating the app, since we don't lose any data in NSUserDefault, we can do a routine to convert any unused Product A into an equivalent Product B.Thank you!

I add local packages via Add Files to project and then add package product in General tab, Frameworks, Libraries section. this way I can add -Wl,-make_mergeable to unsafe flags. Package compilation itself works fine, but main app target fails ld: -make_mergeable can only be used when creating a dynamic library. filed feedback to apple about it https://feedbackassistant.apple.com/feedback/13547751.

I’d like to get a better understanding of your requirements here. Here’s what I think is going on: You have a Mac product that you distribute directly (as opposed to on the Mac App Store). Your users download that product from your website. At the point of download, you want to customise the product for each user. Am I right so far? If so, I have a couple of follow-up questions: Roughly how many users are we talking about here? Tens? Hundreds? Thousands? How is your product currently packaged. You mentioned an disk image, so I’m presuming that’s the outermost container. What’s on that disk image? Just your app? Is there more nested containers, like an installer package? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Any suggestions as to what I'm missing or doing wrong? You are signing your installer package as code, which is not right. Installer packages must be signed by installer tools using a Developer ID Installer code signing identity. Packaging Mac Software for Distribution shows the basics. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com