“missing package product”

ITMS-90237: The product archive package's signature is invalid. Ensure that it is signed with your '3rd Party Mac Developer Installer' certificate. How can I solve? I've revoked my mac installer distribution certificate and re-download or did many things but the same error occurs several times.

I created a new Package with Xcode and incorporated a dependency, however when I try to use it, I get a No such module error. How do I use the dependency in the Package sources? In a normal project, I can easily import and use AgileDB. Here's the Package: // The swift-tools-version declares the minimum version of Swift required to build this package. import PackageDescription let package = Package( name: DBCore, products: [ // Products define the executables and libraries a package produces, and make them visible to other packages. .library( name: DBCore, targets: [DBCore]), ], dependencies: [ .package(url: https://github.com/AaronBratcher/AgileDB, from: 6.4.0) ], targets: [ // Targets are the basic building blocks of a package. A target can define a module or a test suite. // Targets can depend on other targets in this package, and on products in packages this package

Hello, I have a problem to notarize my .pkg. Indeed, I have a certified certificat in .pfx format and I have a Apple Developer Program account. 1 - in the key chain, I request a certificate from a certificate authority in Keychain to have a .csr 2 - I install the .csr to have a .cert than I put in keychain to have a valide certificate 3 - I execute this command : productsign --sign Developer ID Installer: Name_of_developer_ID (Number_of_DeveloperID) name_uncertfied.pkg name_certified.pkg Finaly, I get that answer : Product sign: error: Could not find appropriate signing identity for Developer ID Installer: ** (****) then that there are a valide certificate with wrote Developer ID installer : Name_of_developper_ID (Number_of_DeveloperID). Moreover, when I execute this command : security -v find-identity -p codesigning My certificate don't appears in matching identities then he is in my Keychain et I don't know why ... My Question is, How I can notarize my .pkg ?

How do you get previews working in a swift package? This talk shows this working, however the following steps do not work. Using Xcode 13.2.1 create a new Swift Package Add a simple view with a preview to that swift package (See code below) Attempt to run the preview. code: import SwiftUI @available(iOS 14.0, *) public struct TestView: View { public init() { } public var body: some View { Text(Hello World) } } @available(iOS 14.0, *) struct NoDataView_Previews: PreviewProvider { static var previews: some View { TestView() } } #endif See errors: ================================== | RemoteHumanReadableError | | LoadingError: failed to load library at path /Users/fishycx/Library/Developer/Xcode/DerivedData/MyLibrary-cwtaivijrddzbkeegisudpueggjw/Build/Intermediates.noindex/Previews/MyLibrary/Products/Debug-iphonesimulator/PackageFrameworks/MyLibrary_-71ED4B7C0CDEC55C_PackageProduct.framework/MyLibrary_-71ED4B7C0CDEC55C_PackageProduct: Optional(dlopen(/Users/fishycx/Library/Deve

I've put together a Swift Package which has a binary dependency. The xcframework contained within depends on another xcframework which is in another package. I can't get the first Swift Package to bring in the second Swift Package as a dependency beyond the .testTarget. In the WWDC 2020 video Distribute binary frameworks as Swift packages - https://developer.apple.com/videos/play/wwdc2020/10147/ it shows code that looks like this: import PackageDescription let package = Package( tt name: Emoji, tt products: [ ttttt.library( ttttttt name: package, ttttttt targets: [Emoji]), tt ], tt dependencies: [ ttttt.package(url: https://github.com/JohnnyAppleSeed2020/BinaryEmoji, from: 1.0.0), tt ], tt targets: [ ttttt.target( ttttttt name: package, ttttttt dependencies: [Emoji]), tt ] ) The presenter says, If you want to use that same library as a package dependency, it also works the same way you are used to. In the package

In the talk, it was explained how to use a binaryTarget to add a .xcframework from a url, but what about a local path? Take the following Package and file structure, is this the correct way to structure and refer to the .xcFramework? | SamplePackage | - | Package.swift | - | README.swift | - | Sources | - | - | Sample | - | - | - | file.swift | - | - | SampleFramework | - | - | - | framework.xcframework | - | - | Tests | - | - | - | LinuxMain.swift | - | - | - | SampleTexts | - | - | - | - | sampleTests.swift // 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: Sample, platforms: [ .iOS(.v13), .macOS(.v10_12) ], products: [ // Products define the executables and libraries produced by a package, and make them visible to other packages. .library( name: Sample, targets: [Sample, SampleFramework]), ], targets: [ // Tar

Hi. I have an archive package that contains multiple packages. One of the pkg has a network extension app. I normally notarized the top archive package and staple it. However, when I tried to install pkg, I keep encountering gatekeeper. I notarize and stape each of the pkg inside of the archives then create achieve package again and notarize/staple it. But again, I still see the same issues. Keeps seeing the gatekeeper. Am I missing something?

When opening a pkg file on Mojave and Catalina I'm seeing following Package Authoring Errors in Installer log (/var/log/install.log):Package Authoring Error: <background> has an unsupported MIME type: image/data Package Authoring Error: <background_scaling> has an unsupported MIME type: X-NSObject/NSNumber Package Authoring Error: <background_alignment> has an unsupported MIME type: X-NSObject/NSNumber Package Authoring Error: <layout-direction> has an unsupported MIME type: X-NSObject/NSNumberwhich is weird because background is defined in pkg Distribution XML as:<background file=background.tiff alignment=bottomleft scaling=none mime-type=image/tiff/>based on specification of Distribution file in https://developer.apple.com/library/archive/documentation/DeveloperTools/Reference/DistributionDefinitionRef/Chapters/Distribution_XML_Ref.htmlSimilar problems can be seen even on pkg installers that contain no back