missing package product

I work with a number of enterprise clients and one thing we often do is have various frameworks that are optional depending on what type of build we are doing. A common example being to include a framework that contains an embedded server for testing, demo or debugging purposes. Prior to SPM we would link those frameworks as Optional and run a script phase after the build that removed them from the Frameworks directory of the app if it was a Release build. Now I have an Xcode project that includes a number of SPM package, one of which is an embedded server which in turns references several other packages I'd like to exclude form a Release build. But I cannot figure out how to do this. Can I make the inclusion of a package optional? Or somehow remove it after linking? In Swift I can write #if canImport(MockServer) but I cannot see how to actually make MockServer an optional include. Any ideas?

Hello, I submitted a Request for a Deployment Package. However, I have not received any emails yet. Could you please let me know when I can expect a confirmation message? Thank you.

I wonder if its possible to get target based dependency using Swift Package Manager without Xcode resolving all dependency in package. I have a package like this: // swift-tools-version:5.3 // The swift-tools-version declares the minimum version of Swift required to build this package. import PackageDescription let package = Package( name: ReCaptcha, platforms: [ .iOS(.v9) ], products: [ .library( name: ReCaptcha, targets: [ReCaptcha]), .library( name: ReCaptchaRx, targets: [ReCaptchaRx]) ], dependencies: [ .package(url: https://github.com/ReactiveX/RxSwift.git, from: 6.0.0), .package(url: https://github.com/JakubMazur/AppSwizzle.git, from: 1.3.2), ], targets: [ .target( name: ReCaptcha, dependencies: [], path: ReCaptcha/Classes, exclude: [Rx], linkerSettings: [ .linkedFramework(UIKit) ] ), .target( name: ReCaptchaRx, dependencies: [ ReCaptcha, .product(name: RxSwift, package: RxSwift) ], path: ReCaptcha/Classes

I'm notarizing my .pkg installer and even stapling the ticket after, but I still get rejected after checking it with the following command:spctl -vvv --assess --type install path/to/my/notarized.pkg path/to/my/notarized.pkg: rejected origin=3rd Party Mac Developer Installer: My Certificate Name (XXXXXXXXX)My pkg is being created with the packages app and then signed using pkgutils. Then it's notarized and after the success response from Apple I'm stapling the ticket into it. The pkg contains an app that is also signed of course.How can I find more information about what's going on? Is there a log somewhere?Thanks in advance.

A month ago I joined a team and cloned the project from git, and when building the project in Xcode 13 (which I had recently installed) I ran into build issues: I reviewed my integration with git (ssh keys) and after I ran File>Packages>Reset Package Caches everything started working. Not sure whether the package cache reset fixed it, but all is good. Until I just got my new 16 M1 MacBook pro. I did a time machine backup, restored to the new machine, and the same problem is back. Except that I can't get past the issue. The other Xcode source functions work (fetch, change branch, etc.) but no luck with authenticating to pull the packages. I don't consider myself a git guru - I prefer to use GitHub Desktop over the command line, but I use the command line when I need to. In Xcode File>Preferences>Accounts the GitHub account is set up there. So what am I missing? Any help appreciated.

I made a pkg install my APP but failed to install to other macbooks because of digital signature invalid warning : Signed.pkg can't be installed because its digital signture is invalid. I signed again,but failed to install again with same warning. bogon:Desktop tanhuang$ productsign --timestamp --sign Developer ID Installer: Tan Huang (NGMD5RC85D) HuionDriver.pkg Signed.pkgproductsign: using timestamp authority for signatureproductsign: signing product with identity Developer ID Installer: Tan Huang (NGMD5RC85D) from keychain /Users/tanhuang/Library/Keychains/login.keychain-dbproductsign: adding certificate Developer ID Certification Authorityproductsign: adding certificate Apple Root CAproductsign: Wrote signed product archive to Signed.pkgbogon:Desktop tanhuang$ codesign -dvvv Signed.pkgSigned.pkg: code object is not signed at allbogon:Desktop tanhuang$ spctl --assess -v Signed.pkgSigned.pkg: rejectedsource=no usable signaturebogon:Desktop tanhuang$ spctl --assess -v --type instal

I'm building a package for my custom fonts. But not be able to register custom .ttf file in a Swift Package. Any recommendations for this?

Hi, I am trying to install a swift package and I keep getting this error. Error When I install it any other way, I get this error: Error Any ideas on how to fix it?

I have created my own SPM through File -> New -> Package Package.swift looks like: // swift-tools-version: 5.10 // The swift-tools-version declares the minimum version of Swift required to build this package. import PackageDescription let package = Package( name: MyPackage, platforms: [.iOS(.v16), .macCatalyst(.v16), .macOS(.v14)], products: [.library(name: MyPackage, targets: [MyPackage]),], dependencies: [ .package(path: ../external-package) ], targets: [ .target(name: MyPackage, path: Sources), .testTarget(name: MyPackageTests, dependencies: [MyPackage]), ] ) When I run swift build the error says: '.../MyPackage/.build/arm64-apple-macosx/debug/external-package.build/external-package-Swift.h' not found and surely, when I go to directory: .../MyPackage/.build/arm64-apple-macosx/debug/external-package.build/ there are only 2 files in there: module.modulemap & output-file-map.json All source files from external-package a

I am running into an issue mainly on my CI, but the issue is present either way. I have a project with multiple Swift Packages as dependancies, most are remote but i have a couple that are local swift packages. On first load of xcode, it will fail to fetch the local packages, if i keep xcode open, around 10 minutes later, it will automatically try and fetch the packages but this time will succeed. Has anybody had this issue? Apart from deploying these packages remotely, is there any other solutions? xcode 13, 13.1, 13.2 all tried and have the same behaviour. Thanks!