missing package product

Right-Click on the archive file (.xcarchive) > Show Package Contents > Products > Applications > Right-Click on the app file > Show Package Contents > Double-Click on Info.plist to edit itChange value of DTXcodeBuild from 9C40b to 9C40Re-submit and it will work

Just to add to the post, I tried notarizing again a .pkg installer that I had already notarized successfully a few weeks ago and I got the same problem, so unless I'm missing something obvious here, there was a change in Apple's side that is now causing this problem.In the meantime, I'm going to try to notarize the app first, then package it, and then notarize the .pkg file.

I'm experiencing a similar issue. How do we figure out exactly what dylibs are missing? When I look at the package contents, the folder in quests is there.

It could be a bug or incompatibility, but there are some other subtle problems in your project(s) that may be affecting you.Incidentally, there is no such thing as a static framework. A framework is a dynamic library packaged as a bundle. Perhaps you mean a private framework (a framework embedded in an app bundle, so not shared between apps, which is very common), or a static library (which is a collection of object files, a library in the Unix sense, not in the Apple sense).— One possibility is that the deployment target got changed when you converted the framework project for Xcode 9. This might result in an incompatible build product.— Another possibility is that your are not producing the framework using Archive (from the Product menu), but are trying to use the build product from a Build or Run operation. The difference is that Build might not build all of the CPU architectures that a finished (Archive'd) framework needs — the variant for arm64 might actually be missing

Same here :/ Is there any solutions ?error: Swift package product 'Disk' is linked as a static library by 'Project' and 'Widget'. This will result in duplication of library code.

This seems to work for me. I created a workspace and added a package and a playground to that workspace. I then added a resource to the package, and I was able to access that from the playground. I’ve included a lot more details below. I recommend that you retry this with a newly created workspace, package and playground, to confirm that the basics are working. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com I’m using Xcode 12.4 on macOS 11.2.3. Here’s my Package.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: MyLibrary, products: [ // Products define the executables and libraries a package produces, and make them visible to other packages. .library( name: MyLibrary, targets: [MyLibrary]), ], dependencies: [ // Depend

Hmmm... If I Show Package Contents from the Finder for my .xcdatamodeld file, i Just see only one file/directory - contents . What am i Missing?

Removing type: parameter in package products helped me fix SwiftUI previews: .library( name: MyLib, // type: .static, targets: [MyLib] )

So I finally settled on using a swift package to handle the command line tool project, which I added to the main app project using the package dependencies. This package executable product could be set as a dependency, and I added a run script build phase to sign the tool and embed it in the main app's Resources folder. The SPM executable product needs to be signed with --options=runtime to be embedded in a notarized macOS app. The script is pretty simple: #!/bin/bash devID=Developer ID Application: Me Myself (ASDF1234) toolPath=${BUILT_PRODUCTS_DIR}/MyTool codesign --force --options=runtime --sign ${devID} ${toolPath} cp ${toolPath} ${CONFIGURATION_BUILD_DIR}/${CONTENTS_FOLDER_PATH}/Resources