“missing package product”

I’m packaging a Safari Web Extension using the web-based Safari Web Extension Packager in App Store Connect. The ZIP uploads successfully, the manifest is accepted, and the Packager automatically creates the related Extension identifier. However, every build fails during export with: Exporting for App Store Distribution failed. Please download the logs artifact for more information. It also shows: Exporting for Development Distribution failed. Please download the logs artifact for more information. There is no Logs, Artifacts, or Download button on the build or issue page. To isolate the problem, I tested: Manifest V2 and Manifest V3 A minimal extension containing only HTML and icons No JavaScript, permissions, host permissions, APIs, or external dependencies A completely new App Store Connect app A new explicit Bundle ID A name-matched extension ZIP Multiple version and build numbers Every test produced exactly the same export errors. The App Store Connect agreement is active, and

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

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?

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

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

Hi, I have to publish a macOS application outside the AppStore, downloadable from another a third-party website. I have to build an app say for example myapp.app and then pack it inside a package installer .pkg file users will download and run pkg to install the app. Which part in the least should be Notarized & signed, the app has to run on catalina 10.14 & newer versions Should .app and .pkg both should be signed and notarized or .pkg is enough to be signed & notarized ? if some one can direct me to any documentation on this subject along with answer, that would be great. Thanks, Ahmed