“missing package product”

Hello,Is there any way to debug why my pkg is nt compatible with my MacOS?I was building the *.app using Qt and deploy by `macdeployqt`. After check every Frameworks and plugins paths the next step was:- `pkgbuild --component <NAME>.app --install-location /Application <APP_NAME>.pkg`and`sudo productbuild --package <APP_NAME>.pkg --content <APP_NAME>.app --sign Developer Install ID: (XXXXX) <SIGNED_APP_NAME>.pkg `I was trying to Install <SIGNED_APP_NAME>.pkg but Instaler throws me an error: This package is incompatible with your version of MacOS.I'm using MacOs 10.15. + I found also that there is no codesign folder in my bundle is that might be a reason?Maybe I missed something?

Apple seems to have archived its documentation for making PKG packages, and PackageMaker hasn't been seen since 2012. Are packages deprecated, or are there new ways for creating them?

Hello!This isn't so much a Developer issue, but developers are far more knowledgable about Notarization than anyone else, so here I am! :-)I'm creating a pkg with another (signed, notarized) pkg as its payload and a postinstall.sh to install that pkg (using /usr/sbin/installer) with particular configuration options. I can sign the resulting pkg just fine, but it has yet to pass Notarization. The original pkg installs fine with no warnings, but a pkg containing that original pkg fails Notarization with The executable does not have the hardened runtime enabled errors.Does anyone have any ideas on how to achieve what I'm trying to do? I'd really rather not have to re-package the original pkg's payload, likely having to edit its preinstall and postinstall scripts to add my configuration options. Is it possible that I'm just getting caught in the timeline issue with original apps and pkgs that were Notarized before Feb 1, 202

Hi, we have .pkg install package consisting of various sub packages. One of them contains presets and needs to be installed the the default preset location /Library/Audio/Presets. If this non-binary preset package is the only one in a .pkg choice notarization fails with: logFormatVersion: 1, jobId: *, status: Invalid, statusSummary: Archive contains critical validation errors, statusCode: 4000, archiveFilename: mypackage.pkg.zip, uploadDate: 2024-08-22T21:24:03.251Z, sha256: *, ticketContents: null, issues: [ { severity: error, code: null, path: mypackage.pkg.zip, message: Package mypackage.pkg.zip has no signed executables or bundles. No tickets can be generated., docUrl: null, architecture: null }, { severity: warning, code: null, path: mypackage.pkg.zip/mypackage.pkg, message: bInvalid component package: mypackage_vstpreset Distribution file's value: #com.mycompany.mypackage.vstpreset.pkgn, docUrl: null, architecture: null } ] } Not sure, but m

Hey all, I am working on a macOS application that has a requirement to have both normal and silent installation. The created package that installs the app uses a custom built plugin (which is packaged with the app) to retrieve package's name and use that as environment and secret for the installed application. When package is installed non-silently, the plugin runs properly and is visible as a step in the installer (attached screenshot, environment step). It can be confirmed that it runs as Console app records logs from the plugin and the file with environment is modified accordingly. If the package is installed silently via command line in terminal: sudo installed -pkg -target /Applications -verbose -dumplog no logs are caught by the Console app and there is no indication that plugin has ran as the file it modifies, isn't modified. Is it possible to run package's plugins in the silent installation and if so, what has to be done to do it? If need

We have a set of questions about Notarization. We create plug-ins for various 3rd party software. Our plug-ins operate under the 3rd party software. So for example Photoshop (our is not a typical Mac App store app - we make these also so we know how Mac App store code-signing etc works).Our infrasturcture is something like plug-ins for each version of Photoshop we support (which gets installed in the Photoshop plug-ins folder). Then component libraries that are installed in Library/Application Support/OurProduct folder and the Applications folder (we also create a folder in the Applications folder and stick in various other parts and libraries, readme, userguide etc). So its basically a set of libraries really thats all over.Then we take all of those components and we package (using Package Maker under 10.11.6) it and create flat package installers (which contain installer plug-ins at the end) which we deliver to our end user. The final installer are signed using th Apple 3rd party

My company would like to deploy packages from Perimeter 81 and cybereason to our macos devices managed by Intune, but we are getting the following error message when trying to create the distribution file: productbuild --synthesize --package ./cybereason.pkg ./distribution.xml productbuild: error: ./cybereason.pkg is a product archive, not a component package. productbuild --synthesize --package ./perimeter.pkg ./distribution.xml productbuild: error: ./perimeter.pkg is a product archive, not a component package. I do not have experience with packaging outside of the basic instructions provided by Microsoft, but is anyone familiar with how to get around this error message? Thanks

I'm trying to share a dependency between my the target of my Xcode project and a Swift Package (part of the same project) but I'm getting a duplicate symbols error with both dynamic and static targets. I have 3 targets: App - Cocoa Touch, Module A - Static Framework, Module B - Static Framework, and a Swift Package called shared (produces a static library). I'm trying to share Framework A between all the targets and the shared package. Is there any recommended approach for this? Also, I'm curious if dynamic or static frameworks are recommended in general.

I've been struggling to understand why the update package feature is failing for a private package I have hosted on our company gitlab server. I am able to add the package to the project just fine, and Xcode downloads the latest version. Any time I make a change and bump the minor version of my package (e.g. 0.0.8 -> 0.0.9), I cannot get Xcode to update to the latest. I have 0.0.8 - next major set for the version rules. Initially adding the package to the project was successful: But when I update my package, tag a new version e.g. 0.0.9, push to our gitlab repo (with tags), then in the project where I added this dependency, right click the package and select Update Package - I get the following error: If I remove the package dependency from the project and add it again, Xcode always correctly grabs the latest version. I have tried removing this package and running File > Packages > Reset Package