missing package product

Project Background: I developed a Mac project using Electron and VSCode Successfully uploaded the packaged pkg using Transporter, However, I will receive an email informing me that there are some issues with the project: ITMS-90296: App sandbox not enabled - The following executors must include the 'com. apple. security. app sandbox' entitlement with a Boolean value of true in the entitlement property list: [[com. electron. iflyrecclient. pkg/Payload/iFlytek Listen. app/Contents/MacOS/iFlytek Listen]] ITMS-90886: 'Cannot be used with TestFlight because the signature for the bundle at' iFlytek hears. app 'is missing an application identifier but has an application identifier in the provisioning profile for the bundle.' Bundles with application identifiers in the provisioning profile are expected to have the same identifier signed into the bundle in order to be eligible for TestFlight.' Here is my packaging process: Generate an app using the electron packager

Hi, I'm trying to notarise package file of our product. Notarization is success with some warnings on 3rd party package file. I see two executables in the 3rd party package file is not code signed properly. I need to expand, sign those binaries and flatten it again and include into our package file. I'm able to expand the 3rd party package file using the below command: pkgutil --expand directory name Now i'm able to see files of the above package file. But how do i expand pay-load files?

This package is incompatible with this version of OS X and may fail to install.Heads up for anyone who makes packages. If you write to SIP protected locations, (even symlinks) you will get this warning.Example:Writing to /var - badWriting to /private/var - goodFrom now on it might be ideal to write to the full path as these are not SIP protected./private/etc/private/tmp/private/var

I've setup my Xcode project to use a binary package, for which the manifest is stored in the private git repository. The dependency tracking is set to branch -- it just fetches the manifest from master branch of the repository. It seems, that after initial fetching Xcode or spm caches the commit hash used to fetch the manifest. If I push an update of Package.swift (i.e. containing updated artifact checksum) this change is not refreshed in the project (i.e. after resetting package cache it complains about the checksum mismatch between the actual binary artifact and the manifest). At the same time if I manually clone the repository I see valid checksum in the manifest. I've tried to use all 3 options in Xcode (i.e. reset package cache, resolve package versions, update to newest version). None of them solves the problem. It seems that to reset the cache I need to remove the package from the project and add it again. I'm looking for an elegant way to refresh the manife

It seems that preinstall/postinstall scripts in installer packages (.pkg) are not limited to shell scripts, but can be any kind of executable (e.g. compiled Swift programs). This sounds like an exciting possibility to re-use logic, constants, tests etc. from the app that is being installed, and at the same time benefit from Swift features like type safety for complex installer scripts. Has anyone done this? What were your experiences? Is it advisable, or is it likely to break on the next OS update?