“missing package product”

Hello,I successfully codesigned app bundle and it was accepted by notary service. Then I created a package using pkgbuild/productbuild commands and codesigned it using Installer identity. The installer works fine.I'm now trying to notarize the .pkg file but no success. It always returns invalid status with just one error:severityerrorcodenullpath<package internal path>.pkg Contents/Payload/Contents/MacOS/<executable>messageThe signature of the binary is invalid.docUrlnullarchitecturex86_64(I replaced real paths above).However, when the application is installed, both codesign and spctl return OK status. I use XCode 10.1 on macos 10.14.2.Any suggestions how to satisfy notary service?

I’m new to Mac packaging, and am confused by the multi-part signing and packaging process. I have built an app, using third party software, that I would like to upload to the Mac store for trial/testing purposes. I have joined the Apple Developers Programme, but am unsure whether I need to invest in third-party certification (e.g. Verisign) or can self-certify my app package. I would be obliged if someone would outline the sequence of steps that I need to follow to create a package that can be offered to users, and confirm whether my AD License is sufficient for me to follow same. Thanks in advance for any advice. Regards, L

Is the nutrition facts package real? If so what’s the url?

I'm building a custom macOS installer for my software, primarily using the builtin tools of codesign, pkgbuild, productbuild and xcrun. My product consist of a list of plugins and a CEP extension for the Adobe After Effect app. All of my bundles and binaries are properly signed using a trusted Apple Developer certificate I've generated, of type Developer ID Application. My installer is a distribution pkg, and has this structure(expanding it using pkgutil --expand): SceneTools-3.4.4-osx-installer ├── Distribution ├── miscellaneous.pkg ├── plugins.aftereffects2022.pkg ├── plugins.aftereffects2023.pkg ├── plugins.aftereffects2024.pkg ├── plugins.aftereffects2025.pkg ├── preinstall.pkg ├── Resources ├── scenebuilder.pkg └── uninstaller.pkg Each child pkg would install parts of my product in different locations in the target macOS disk(this is why I'm using that kind of style of building the custom installer). Signing each and every bundle or

Trying out the new package trait support in Xcode 26.4 and it seems like the default traits for the package are being enabled even when explicitly set to disabled. At first I thought it was something wonky in the Xcode UI around the new support for traits. I've been able to replicate the issue with just two Swift packages, so no Xcode UI for setting the traits. Feature package // swift-tools-version: 6.3 import PackageDescription let package = Package( name: MyAwesomeFeature, platforms: [ .macOS(.v26) ], products: [ .library( name: MyAwesomeFeature, targets: [MyAwesomeFeature] ) ], traits: [ .trait(name: SomeBetaFeature), .default(enabledTraits: [SomeBetaFeature]), ], targets: [ .target( name: MyAwesomeFeature ), ], swiftLanguageModes: [.v6] ) For the sake of testing I've given it a simple object that just prints if the trait is enabled Inside MyAwesomeFeature public struct SomeObject { func printTraitStatus() { #if SomeBetaFeature print(Beta feat

Hi, I try to add the Firebase requirements to my iOS application. I launched the package manager, at first, nothing was loading, therefore I deleted and recreated my Github account, and the previous packages now appears. When I try to paste the url for Firebase in the search bar, there is an infinite loading loop and it never appears. I tried to restart Xcode several times, to disconnect and reconnect from wifi etc. Can anyone help me solve this please?

I have Xcode 14.3 and have tried deleting derived data, changing build location to default and resolving packages. I uninstalled the firebase sdk and am now hanging on preparing to validate. Any solutions would be lovely When running the command xcodebuild -resolvePackageDependencies I get the following error: Resolve Package Graph Could not initialize package support: encountered an I/O error (code: 1) while reading /Users/jackderemiah/Library/org.swift.swiftpm/configuration/mirrors.json

IMPORTANT I’m very pleased to report that, due to the hard work of a number of folks at Apple, this DevForums post has been replaced by official documentation: Packaging Mac software for distribution. I’m leaving this post in place as a historical curiosity, but please consult the official documentation going forward. This post is one of a pair of posts, the other one being Creating Distribution-Signed Code for Mac, that replaces my earlier Signing a Mac Product For Distribution post. For more background on this, see the notes at the top of Creating Distribution-Signed Code for Mac. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com Packaging Mac Software for Distribution Build a zip archive, disk image, or installer package for distributing your Mac software. Overview Xcode is a great tool for creating and distributing Mac apps. Once you’ve written your code you can upload it to the App Store with just a few

Xcode 16 seems to „forget“ a swift package within a subfolder of a root package after restart or shut-down. I have the following project structure, which also resembles the directory structure on disc: MyPackage - Package.swift - README.md - Sources - MyPackage - Tests - MyPackageTests - Tools - MyGenerator // <- after restart this folder is not visible in the Xcode project navigator - Package.swift - Sources - main.swift - Tests MyGenerator is a standalone package which is used during development of MyPackage to generate source code files for MyPackage based on text file input. Essentially an executable target script which I can run within its folder with: swift run MyGenerator someInputFile.txt MyPackage does NOT use MyGenerator as a dependency, nor do I want this tool listed as a dependency in MyPackage Package.swift file. Yet MyGenerator is part of the same Git repo, as it documents the changes to the tool on how to generate source code for MyPackage. Both packages a

I (we) am in the process of porting our day job application onto Mac. We've done most of the porting and got the product it self building so I am looking at the packaging step. Currently we have a single build output which includes 2 applications, a runtime and toolkit. I've been able to create a .app file for the runtime variant and the toolkit separately but I am not sure what is the best way to have two launch able apps? from the same package i.e. I have a file structure something likeRootcommon_filestoolkitruntimeThe toolkit is launched by running a command in the toolkit directory and the runtime is launched by running a command in the runtime directory.Whats the best way to package this up? I'm looking to have a simple drag and drop style install that you can with an app.Thanks for any advice. Fingers crossed this side project will get there in the end and I will be able to run the product on my laptop natively.

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