“missing package product”

Hi, after a software update of our previously successfully notarizated installion .pkg we now receive a cryptic notarization issue refusing the entire .pkg: { logFormatVersion: 1, jobId: 5cff2d71-7228-4fb4-a39d-329084cd2713, status: Invalid, statusSummary: Archive contains critical validation errors, statusCode: 4000, archiveFilename: my_installer.pkg.zip, uploadDate: 2024-12-04T23:17:14.016Z, sha256: 2f26d0376506abe130ac904d7cb0d0cd5428666624428da9f44da7756352844f, ticketContents: null, issues: [ { severity: error, code: null, path: my_installer.pkg.zip, message: Package my_installer.pkg.zip has no signed executables or bundles. No tickets can be generated., docUrl: null, architecture: null }, { severity: warning, code: null, path: my_installer.pkg.zip/my_installer.pkg, message: The contents of the package at my_installer.pkg.zip/my_installer.pkg could not be extracted., docUrl: null, architecture: null } ] } What could be the reason for that? We've also submitted the .pkg

I am very new to this, so apologies if this is a noob question. I am creating a package using Packages. I have a Developer ID certificate that expires in 2027. If I set my project to use that certificate before building in Packages, the build fails. So I am certifying after using terminal. However, in both the Terminal certification and running the installer for my .pkg, it says that the certificate is expired. I don't understand how a certificate that expires in 2027 can already be expired. Any ideas out there? I found a post with the same problem from 7 years ago and there were no responses. Thanks all!

I have a flattened pkg file to notarize. It is signed at the build time by the Developer ID installer. Here is the output of a series of commands. check notarization status submit notarization and status check tatus of notarization after notarization complete. mtnview@C02YC2G0JGH5 ~/D/s/d/h/c/pkgs>spctl -a -vvv -t install ./foo.mac11.x86_64.pkg ./foo.mac11.x86_64.pkg: rejected source=Unnotarized Developer ID origin=Developer ID Installer: foo, Inc. (69Q4FM6AL9) mtnview@C02YC2G0JGH5 ~/D/s/d/h/c/pkgs> xcrun notarytool submit ./foo.mac11.x86_64.pkg --keychain-profile AC_PASSWORD --wait Conducting pre-submission checks for foo.mac11.x86_64.pkg and initiating connection to the Apple notary service... Submission ID received id: cc2d06be-fb07-4794-a92a-996ac07985fd Successfully uploaded file id: cc2d06be-fb07-4794-a92a-996ac07985fd path: /Users/mtnview/Documents/shared_vm/dev/hawkeye/cmake-macos/pkgs/foo.mac11.x86_64.pkg Waiting f

I would like to use ReferenceFileDocument or FileDocument but the file type I use is a package type that conforms to com.apple.package. However the FileDocument - https://developer.apple.com/documentation/swiftui/filedocument and ReferenceFileDocument - https://developer.apple.com/documentation/swiftui/referencefiledocument respective write methods are called with a inout FileWrapper. I need this this FileWrapper to be a directory FileWrapper so that i can add child items to it. However the write method is being called with a regularFile instance of the FileWrapper so i am unable to add nested files that I need within my package. My writableContentTypes is UTType(exportedAs: com.example.package, conformingTo: .package). And my Xcode project expires/declares this data type as a package, so that UIDocument/NSDocument work.

I have a package installer for my .app created with a sequence of commands (pkgbuild, productbuild, xcrun notarytool, xcrun stapler). When this installer is run on a pristine machine, the user is prompted to install Rosetta first before being able to run the installer. Is this expected behavior? Or am I creating the .pkg incorrectly?

I have an Xcode project that generates xyz.framework and that framework is used by other teams for their app. Updating the framework is a manual process. So I am planning to covert my xyz.framwork source to swift package manager. I couldn't find any such articles. Please let me know if there is any resource around this topic.

Hello. We have an app bundle that we package into a .pkg file. We are currently getting an error when notarizing the .pkg artifact. But running all the suggested tool vs the built bundle/package results in validating the bundle/package. We don't know what notarization service is rejecting the pkg. The notarization failure: Notarization Invalid { logFormatVersion: 1, jobId: b26ec329-409e-4a21-88f0-6f924795a6db, status: Invalid, statusSummary: Archive contains critical validation errors, statusCode: 4000, archiveFilename: MY-APP.pkg, uploadDate: 2021-07-19T17:39:59Z, sha256: 019c0409eab63e68cfe6323sd2e33715f07c731d5b4192254277ed62db1b6e97d, ticketContents: null, issues: [ { severity: error, code: null, path: MY-APP.pkg, message: The binary is not signed., docUrl: null, architecture: null } ] } Here is the output of codesign -v -vvv --deep --strict MY-APP.app: ... MY-APP.app: valid on disk MY-APP.app: satisfies its Designated Requirement Output of pkgutil --c

I used Xcode 16 beta 1 I would like to import the AccessorySetupKit introduced at the wwdc24 event it can imported iOS target source, but can't imported in my local package, ControllerKit what should I do ? why can't import local package ?

I am getting an error message (mixed language) while adding the Swift package dependency. Source code mostly contains Swift language and a little bit of Objective-C. Can't we mix Swift and Objective-C language? If so, what is the workaround