“missing package product”

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

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

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?

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

I created PKG installer in command line (see below, command's output is in italic). Installer is opening on my MBP, but after uploading on server and download by link, macOS shows TestApp.app.2.0(32).pkg” can’t be opened because Apple cannot check it for malicious software. TestApp.app is application signed by Developer ID Application certificate and notarised with Xcode. Check TestApp.app signing: codesign --verify --verbose TestApp.app TestApp.app: valid on disk TestApp.app: satisfies its Designated Requirement spctl --assess --verbose TestApp.app TestApp.app: accepted source=Notarized Developer ID Build package component pkgbuild --identifier --version '2.0(32)' --sign 'Developer ID Installer: ….’ --install-location /Applications --component TestApp.app component.pkg pkgbuild: Adding component at …../Create PKG/TestApp.app pkgbuild: Using timestamp authority for signature pkgbuild: Signing package with identity Developer ID Installer: …” from keychain …./Librar