Search results for

“missing package product”

55,547 results found

Post

Replies

Boosts

Views

Activity

Safari Web Extension Packager: App Store and Development export both fail, but logs artifact is missing
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
0
0
54
3w
Reply to Stapling is not working for a package installer and hence user receives "Apple cannot check it for malicious software."
A few notes here: You mentioned that you were Notarizing your app and your pkg installer. In this case you just need to Notarize your pkg installer since this is the outer container. You mentioned that you were creating a pkg installer with a 3rd party product; what happens if you create your pkg installer with a native tool like productbuild? Does this improve the situation any? There are example at the bottom of the man page. Matt Eaton DTS Engineering, CoreOS meaton3@apple.com
Topic: Code Signing SubTopic: Notarization Tags:
Aug ’21
How to make a Swift Package, which has a binary dependency, dependent on another Swift Package?
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
0
0
1.5k
Sep ’20
Stapling flat pkg and gatekeeper
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?
1
0
861
Mar ’22
Local xcFrameworks in Swift Packages
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
4
0
9.1k
Jun ’20
Package Authoring Error when opening pkg file
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
5
0
5.3k
Jan ’20
Reply to Swift Package can be MAKE_MERGEABLE?
Unfortunately, it's NO. Currently, building and distributing the XCFramework is the only way to make your package as mergeable. When you try to configure the linkerSettings to enable MAKE_MERGEABLE, it will failed building w/ error saying The package product cannot be used as a dependency of this target because it uses unsafe build flags. even though the product was defined as .dynamic If someone has any good solution, please let me know!
Dec ’23
Which part to be notarized in a pkg, .app or pkg or both ?
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
1
0
616
Feb ’21
Reply to Use Xcode for Server Side Development
I had the same problem, i solved it like this: First, change the package.swift like this: (In fact, this is the same as WWDC Session) // swift-tools-version: 5.7 import PackageDescription let package = Package( name: MyServer, platforms: [.macOS(12.0)], products: [ .executable( name: MyServer, targets: [MyServer]), ], dependencies: [ .package(url: https://github.com/vapor/vapor.git, .upToNextMajor(from: 4.0.0)), ], targets: [ .executableTarget( name: MyServer, dependencies: [ .product(name: Vapor, package: vapor) ]), .testTarget( name: MyServerTests, dependencies: [MyServer]), ] ) Second, Find Executable menu with action Edit Scheme -> Run -> info, open the menu, you will find the target you added in Package.swift. Hope this helps !
Jun ’22
Reply to ShouldWaitForLoadingOfRequestedResource not called
To clarify, are you using production keys or not? These can be acquired via the FPS Deployment Package (see <https://developer.apple.com/contact/fps/>). You'll need production keys to attempt playback on the device.
Topic: Media Technologies SubTopic: Streaming Tags:
Replies
Boosts
Views
Activity
Aug ’15
Reply to Expected Expression Error Swiftui
.package(url: https://github.com/binarybirds/swift-html, from: 1.6.0);,import Foundation .product(name: SwiftHtml, package: swift-html);,import SwiftHtml underlined sections have errors like this. what’s wrong with this?
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
Feb ’23
Reply to Pitfalls of manual dependency management in Xcode?
Most useful thread I have found on this issue: Swift Forums: How to prevent resolve packages from stymying developer productivity
Replies
Boosts
Views
Activity
Feb ’24
Safari Web Extension Packager: App Store and Development export both fail, but logs artifact is missing
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
Replies
0
Boosts
0
Views
54
Activity
3w
Reply to StoreKit fetching product using local config file returns empty array on Mac
What am I missing that is preventing me from fetching the products from my local StoreKit config file on Mac? I was missing a Mac build in TestFlight. Once I added a mac build in TestFlight and got the build approved for external testing, I was able to fetch the products on Mac.
Topic: App & System Services SubTopic: StoreKit Tags:
Replies
Boosts
Views
Activity
Nov ’23
Reply to Stapling is not working for a package installer and hence user receives "Apple cannot check it for malicious software."
A few notes here: You mentioned that you were Notarizing your app and your pkg installer. In this case you just need to Notarize your pkg installer since this is the outer container. You mentioned that you were creating a pkg installer with a 3rd party product; what happens if you create your pkg installer with a native tool like productbuild? Does this improve the situation any? There are example at the bottom of the man page. Matt Eaton DTS Engineering, CoreOS meaton3@apple.com
Topic: Code Signing SubTopic: Notarization Tags:
Replies
Boosts
Views
Activity
Aug ’21
How to make a Swift Package, which has a binary dependency, dependent on another Swift Package?
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
Replies
0
Boosts
0
Views
1.5k
Activity
Sep ’20
Stapling flat pkg and gatekeeper
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?
Replies
1
Boosts
0
Views
861
Activity
Mar ’22
Local xcFrameworks in Swift Packages
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
Replies
4
Boosts
0
Views
9.1k
Activity
Jun ’20
Package Authoring Error when opening pkg file
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
Replies
5
Boosts
0
Views
5.3k
Activity
Jan ’20
Reply to Swift Package can be MAKE_MERGEABLE?
Unfortunately, it's NO. Currently, building and distributing the XCFramework is the only way to make your package as mergeable. When you try to configure the linkerSettings to enable MAKE_MERGEABLE, it will failed building w/ error saying The package product cannot be used as a dependency of this target because it uses unsafe build flags. even though the product was defined as .dynamic If someone has any good solution, please let me know!
Replies
Boosts
Views
Activity
Dec ’23
Which part to be notarized in a pkg, .app or pkg or both ?
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
Replies
1
Boosts
0
Views
616
Activity
Feb ’21
Reply to Use Xcode for Server Side Development
I had the same problem, i solved it like this: First, change the package.swift like this: (In fact, this is the same as WWDC Session) // swift-tools-version: 5.7 import PackageDescription let package = Package( name: MyServer, platforms: [.macOS(12.0)], products: [ .executable( name: MyServer, targets: [MyServer]), ], dependencies: [ .package(url: https://github.com/vapor/vapor.git, .upToNextMajor(from: 4.0.0)), ], targets: [ .executableTarget( name: MyServer, dependencies: [ .product(name: Vapor, package: vapor) ]), .testTarget( name: MyServerTests, dependencies: [MyServer]), ] ) Second, Find Executable menu with action Edit Scheme -> Run -> info, open the menu, you will find the target you added in Package.swift. Hope this helps !
Replies
Boosts
Views
Activity
Jun ’22
Reply to OpenAPIGenerator package requirements have a dependency that causes errors
Is your final product a package built with Swift package manager? Or are you trying to use the OpenAPI stuff from an Xcode project? Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com
Topic: Programming Languages SubTopic: Swift Tags:
Replies
Boosts
Views
Activity
Jun ’23
Reply to Xcode 9.2 app uploading broken?
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 DTXcodeBuild's value from 9C40b to 9C40 and it will work.
Replies
Boosts
Views
Activity
Dec ’17