Search results for

“missing package product”

52,924 results found

Post

Replies

Boosts

Views

Activity

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
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
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
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.2k
Jan ’20
Reply to UIDocumentBrowserViewController won't let me pick existing document
Looks like my problem is definitely related to it being a file package. I have a second document type that is not a file package/directory and the UIDocumentBrowserViewController calls the delegate method documentBrowser(_ controller: UIDocumentBrowserViewController, didPickDocumentURLs documentURLs: [URL]) when I tap on it.So am I doing something wrong (i.e., missing an extra step necessary for file packages) or is UIDocumentBrowserViewController broken for file packages and I need to file a bug?Thanks,Dave
Topic: App & System Services SubTopic: Core OS Tags:
Jun ’17
Reply to Notarization has stopped working for .pkg files
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.
Topic: Code Signing SubTopic: General Tags:
Oct ’19
How can you communicate that a .xcframework is a dependency OF the swift package inside Swift package definition?
I am sort of trying to do the opposite of what others are doing. I have a target called CopyFramework that creates a CopyFramework.framework within my main xcproj file. I set up this target because a specific framework (we can call it Tools.xcframework) is distributed as a binary. That framework file lives within the code. Tools.xcframework is structured like so Tools.xcframework (Coding/testBuild/DynamicToolFrameworks/Tools.xcframework) info.plist ios-arm64/ Tools.xcframework/ Tools (executable file) Tools.bundle Headers/ Info.plist Modules/ Tools.swiftmodule/ arm64-apple-ios.abi.json arm64-apple-ios.private.swiftinterface arm64-apple-ios.swiftdoc arm64-apple-ios.swiftinterface module.modulemap module.private.modulemap PrivateHeaders/ ios-arm64_x86_64-simulator/ When the CopyFramework target is run xcode does a few steps which copy the correct version of this framework to derived data. Process Tools.xcframework (iOS) Coding/testBuild/DynamicToolFrameworks/Tools.xcframework /Library/Developer/Xcode/DerivedDat
0
0
117
Jun ’25
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
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
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 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
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.2k
Activity
Jan ’20
Installing/adding packages
Hello!I want to use these utils in my OS X project. How to properly install/add this package to my project? Should work with this code afterwards.Have spent hours of trying. Seems that I'm missing something here. Thank you for your time!
Replies
0
Boosts
0
Views
666
Activity
Apr ’18
Reply to UIDocumentBrowserViewController won't let me pick existing document
Looks like my problem is definitely related to it being a file package. I have a second document type that is not a file package/directory and the UIDocumentBrowserViewController calls the delegate method documentBrowser(_ controller: UIDocumentBrowserViewController, didPickDocumentURLs documentURLs: [URL]) when I tap on it.So am I doing something wrong (i.e., missing an extra step necessary for file packages) or is UIDocumentBrowserViewController broken for file packages and I need to file a bug?Thanks,Dave
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
Jun ’17
Reply to ApplicationPath in organizer archive incorrect. How to fix?
Solved: Go to Build settings then Packaging, change product name to what you want. Hope this saves someone else time.
Topic: Programming Languages SubTopic: Swift Tags:
Replies
Boosts
Views
Activity
Oct ’20
Reply to code sign looking at wrong bundle identifier
Ah. Seems to be caused by this same issuehttps://forums.developer.apple.com/message/136160#136160Changing bundle identifier in info.plist did not change it under packaging in build settings, Manually changing the Product Bundle Identifier under packaging to ${CustomAppBundleId} fixed my issue.
Replies
Boosts
Views
Activity
May ’16
Package localization export is broken
Steps: Create a new clean Swift package in Xcode 14.3 Add a defaultLocalization value to the package manifest Add a platform to the package manifest: platforms: [.iOS(.v16)] Run Product -> Export Localizations and the following error appears: Version 14.3 (14E222b) macOS 13.1 (22C65) Feedback FB12183400
Replies
1
Boosts
0
Views
914
Activity
May ’23
Reply to Notarization has stopped working for .pkg files
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.
Topic: Code Signing SubTopic: General Tags:
Replies
Boosts
Views
Activity
Oct ’19
Are packages deprecated?
Apple seems to have archived its documentation for making PKG packages, and PackageMaker hasn't been seen since 2012. Are packages deprecated, or are there new ways for creating them?
Replies
0
Boosts
0
Views
866
Activity
Mar ’22
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 value of DTXcodeBuild from 9C40b to 9C40Re-submit and it will work
Replies
Boosts
Views
Activity
Dec ’17
Reply to ITMS-90427
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.
Replies
Boosts
Views
Activity
Apr ’22
How can you communicate that a .xcframework is a dependency OF the swift package inside Swift package definition?
I am sort of trying to do the opposite of what others are doing. I have a target called CopyFramework that creates a CopyFramework.framework within my main xcproj file. I set up this target because a specific framework (we can call it Tools.xcframework) is distributed as a binary. That framework file lives within the code. Tools.xcframework is structured like so Tools.xcframework (Coding/testBuild/DynamicToolFrameworks/Tools.xcframework) info.plist ios-arm64/ Tools.xcframework/ Tools (executable file) Tools.bundle Headers/ Info.plist Modules/ Tools.swiftmodule/ arm64-apple-ios.abi.json arm64-apple-ios.private.swiftinterface arm64-apple-ios.swiftdoc arm64-apple-ios.swiftinterface module.modulemap module.private.modulemap PrivateHeaders/ ios-arm64_x86_64-simulator/ When the CopyFramework target is run xcode does a few steps which copy the correct version of this framework to derived data. Process Tools.xcframework (iOS) Coding/testBuild/DynamicToolFrameworks/Tools.xcframework /Library/Developer/Xcode/DerivedDat
Replies
0
Boosts
0
Views
117
Activity
Jun ’25