Search results for

“missing package product”

53,787 results found

Post

Replies

Boosts

Views

Activity

Reply to Previews for SwiftUI views in Packages don't work in Xcode 26.4
I was able to replicate this issue in a very simple way, within a new project created with the standard Xcode template, to which I added a Swift Package as a library (MyLibrary). This is the Package definition: // swift-tools-version: 6.3 // The swift-tools-version declares the minimum version of Swift required to build this package. import PackageDescription let package = Package( name: MyLibrary, platforms: [.iOS(.v18)], products: [ // Products define the executables and libraries a package produces, making them visible to other packages. .library( name: MyLibrary, targets: [MyLibrary] ), ], targets: [ // Targets are the basic building blocks of a package, defining a module or a test suite. // Targets can depend on other targets in this package and products from dependencies. .target( name: MyLibrary, path: Sources/MyLibrary ), ], swiftLanguageModes: [.v6] ) If the target name is equal to library name
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Mar ’26
Notarizing a Flat Package containing another Flat Package?
Hello!This isn't so much a Developer issue, but developers are far more knowledgable about Notarization than anyone else, so here I am! :-)I'm creating a pkg with another (signed, notarized) pkg as its payload and a postinstall.sh to install that pkg (using /usr/sbin/installer) with particular configuration options. I can sign the resulting pkg just fine, but it has yet to pass Notarization. The original pkg installs fine with no warnings, but a pkg containing that original pkg fails Notarization with The executable does not have the hardened runtime enabled errors.Does anyone have any ideas on how to achieve what I'm trying to do? I'd really rather not have to re-package the original pkg's payload, likely having to edit its preinstall and postinstall scripts to add my configuration options. Is it possible that I'm just getting caught in the timeline issue with original apps and pkgs that were Notarized before Feb 1, 202
Topic: Code Signing SubTopic: General Tags:
2
0
598
Feb ’20
Reply to Framework built on Xcode9 are not working on Xcode8
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
Topic: Developer Tools & Services SubTopic: General Tags:
Sep ’17
Notarizing a package/pkg with multiple libraries and bundles
We have a set of questions about Notarization. We create plug-ins for various 3rd party software. Our plug-ins operate under the 3rd party software. So for example Photoshop (our is not a typical Mac App store app - we make these also so we know how Mac App store code-signing etc works).Our infrasturcture is something like plug-ins for each version of Photoshop we support (which gets installed in the Photoshop plug-ins folder). Then component libraries that are installed in Library/Application Support/OurProduct folder and the Applications folder (we also create a folder in the Applications folder and stick in various other parts and libraries, readme, userguide etc). So its basically a set of libraries really thats all over.Then we take all of those components and we package (using Package Maker under 10.11.6) it and create flat package installers (which contain installer plug-ins at the end) which we deliver to our end user. The final installer are signed using th Apple 3rd party
Topic: Code Signing SubTopic: General Tags:
15
0
6.2k
Aug ’19
*.pkg Not compatible with your MacOS
Hello,Is there any way to debug why my pkg is nt compatible with my MacOS?I was building the *.app using Qt and deploy by `macdeployqt`. After check every Frameworks and plugins paths the next step was:- `pkgbuild --component <NAME>.app --install-location /Application <APP_NAME>.pkg`and`sudo productbuild --package <APP_NAME>.pkg --content <APP_NAME>.app --sign Developer Install ID: (XXXXX) <SIGNED_APP_NAME>.pkg `I was trying to Install <SIGNED_APP_NAME>.pkg but Instaler throws me an error: This package is incompatible with your version of MacOS.I'm using MacOs 10.15. + I found also that there is no codesign folder in my bundle is that might be a reason?Maybe I missed something?
Topic: Code Signing SubTopic: General Tags:
3
0
2.6k
Apr ’20
Sharing package between Xcode project and Swift Package
I'm trying to share a dependency between my the target of my Xcode project and a Swift Package (part of the same project) but I'm getting a duplicate symbols error with both dynamic and static targets. I have 3 targets: App - Cocoa Touch, Module A - Static Framework, Module B - Static Framework, and a Swift Package called shared (produces a static library). I'm trying to share Framework A between all the targets and the shared package. Is there any recommended approach for this? Also, I'm curious if dynamic or static frameworks are recommended in general.
Topic: Developer Tools & Services SubTopic: Xcode Tags:
0
0
576
Jul ’20
Reply to Using playgrounds in local swift packages -- Bundle.module throws fatal error
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
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Apr ’21
productbuild: notarize .pkg with non-binary sub package
Hi, we have .pkg install package consisting of various sub packages. One of them contains presets and needs to be installed the the default preset location /Library/Audio/Presets. If this non-binary preset package is the only one in a .pkg choice notarization fails with: logFormatVersion: 1, jobId: *, status: Invalid, statusSummary: Archive contains critical validation errors, statusCode: 4000, archiveFilename: mypackage.pkg.zip, uploadDate: 2024-08-22T21:24:03.251Z, sha256: *, ticketContents: null, issues: [ { severity: error, code: null, path: mypackage.pkg.zip, message: Package mypackage.pkg.zip has no signed executables or bundles. No tickets can be generated., docUrl: null, architecture: null }, { severity: warning, code: null, path: mypackage.pkg.zip/mypackage.pkg, message: bInvalid component package: mypackage_vstpreset Distribution file's value: #com.mycompany.mypackage.vstpreset.pkgn, docUrl: null, architecture: null } ] } Not sure, but m
Topic: Code Signing SubTopic: Notarization Tags:
3
0
818
Aug ’24
Swift package with resources for iOS and tvOS
I'm in the process of converting my local frameworks to local Swift packages. Things are (mostly) working well but I'm struggling with one of the packages: Package MyKit is used by an iOS and a tvOS app. It includes a storyboard for each platform. What is the most appropriate way to describe this in Package.swift? Xcode complains about iOS storyboards not being supported on tvOS so I moved them to their own targets, like this: let package = Package( name: MyKit, defaultLocalization: en, platforms: [ .tvOS(.v13) ], products: [ // Products define the executables and libraries a package produces, and make them visible to other packages. .library( name: MyKit, targets: [MyKit]), ], dependencies: [ // Dependencies declare other packages that this package depends on. // .package(url: /* package url */, from: 1.0.0), ], targets: [ // Targets are the basic building blocks of a package. A targe
Topic: App & System Services SubTopic: Core OS Tags:
2
0
1.7k
Nov ’20
Reply to Previews for SwiftUI views in Packages don't work in Xcode 26.4
I was able to replicate this issue in a very simple way, within a new project created with the standard Xcode template, to which I added a Swift Package as a library (MyLibrary). This is the Package definition: // swift-tools-version: 6.3 // The swift-tools-version declares the minimum version of Swift required to build this package. import PackageDescription let package = Package( name: MyLibrary, platforms: [.iOS(.v18)], products: [ // Products define the executables and libraries a package produces, making them visible to other packages. .library( name: MyLibrary, targets: [MyLibrary] ), ], targets: [ // Targets are the basic building blocks of a package, defining a module or a test suite. // Targets can depend on other targets in this package and products from dependencies. .target( name: MyLibrary, path: Sources/MyLibrary ), ], swiftLanguageModes: [.v6] ) If the target name is equal to library name
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
Boosts
Views
Activity
Mar ’26
Notarizing a Flat Package containing another Flat Package?
Hello!This isn't so much a Developer issue, but developers are far more knowledgable about Notarization than anyone else, so here I am! :-)I'm creating a pkg with another (signed, notarized) pkg as its payload and a postinstall.sh to install that pkg (using /usr/sbin/installer) with particular configuration options. I can sign the resulting pkg just fine, but it has yet to pass Notarization. The original pkg installs fine with no warnings, but a pkg containing that original pkg fails Notarization with The executable does not have the hardened runtime enabled errors.Does anyone have any ideas on how to achieve what I'm trying to do? I'd really rather not have to re-package the original pkg's payload, likely having to edit its preinstall and postinstall scripts to add my configuration options. Is it possible that I'm just getting caught in the timeline issue with original apps and pkgs that were Notarized before Feb 1, 202
Topic: Code Signing SubTopic: General Tags:
Replies
2
Boosts
0
Views
598
Activity
Feb ’20
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
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
Boosts
Views
Activity
Dec ’17
Reply to Framework built on Xcode9 are not working on Xcode8
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
Topic: Developer Tools & Services SubTopic: General Tags:
Replies
Boosts
Views
Activity
Sep ’17
Notarizing a package/pkg with multiple libraries and bundles
We have a set of questions about Notarization. We create plug-ins for various 3rd party software. Our plug-ins operate under the 3rd party software. So for example Photoshop (our is not a typical Mac App store app - we make these also so we know how Mac App store code-signing etc works).Our infrasturcture is something like plug-ins for each version of Photoshop we support (which gets installed in the Photoshop plug-ins folder). Then component libraries that are installed in Library/Application Support/OurProduct folder and the Applications folder (we also create a folder in the Applications folder and stick in various other parts and libraries, readme, userguide etc). So its basically a set of libraries really thats all over.Then we take all of those components and we package (using Package Maker under 10.11.6) it and create flat package installers (which contain installer plug-ins at the end) which we deliver to our end user. The final installer are signed using th Apple 3rd party
Topic: Code Signing SubTopic: General Tags:
Replies
15
Boosts
0
Views
6.2k
Activity
Aug ’19
*.pkg Not compatible with your MacOS
Hello,Is there any way to debug why my pkg is nt compatible with my MacOS?I was building the *.app using Qt and deploy by `macdeployqt`. After check every Frameworks and plugins paths the next step was:- `pkgbuild --component <NAME>.app --install-location /Application <APP_NAME>.pkg`and`sudo productbuild --package <APP_NAME>.pkg --content <APP_NAME>.app --sign Developer Install ID: (XXXXX) <SIGNED_APP_NAME>.pkg `I was trying to Install <SIGNED_APP_NAME>.pkg but Instaler throws me an error: This package is incompatible with your version of MacOS.I'm using MacOs 10.15. + I found also that there is no codesign folder in my bundle is that might be a reason?Maybe I missed something?
Topic: Code Signing SubTopic: General Tags:
Replies
3
Boosts
0
Views
2.6k
Activity
Apr ’20
Sharing package between Xcode project and Swift Package
I'm trying to share a dependency between my the target of my Xcode project and a Swift Package (part of the same project) but I'm getting a duplicate symbols error with both dynamic and static targets. I have 3 targets: App - Cocoa Touch, Module A - Static Framework, Module B - Static Framework, and a Swift Package called shared (produces a static library). I'm trying to share Framework A between all the targets and the shared package. Is there any recommended approach for this? Also, I'm curious if dynamic or static frameworks are recommended in general.
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
0
Boosts
0
Views
576
Activity
Jul ’20
Reply to Xcode 7 beta 3: Missing current version declaration
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?
Topic: App & System Services SubTopic: iCloud Tags:
Replies
Boosts
Views
Activity
Jul ’15
Reply to SwiftUI Previews in Xcode 14 failed to run with SettingsError: noExecutablePath(IDESwiftPackageStaticLibraryProductBuildable)
Removing type: parameter in package products helped me fix SwiftUI previews: .library( name: MyLib, // type: .static, targets: [MyLib] )
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
Jul ’22
Reply to Using playgrounds in local swift packages -- Bundle.module throws fatal error
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
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
Boosts
Views
Activity
Apr ’21
Is there any npm package to fulfil missing tvml js imports while using webpack?
I was wondering if there is any npm module for tvml js which we can use to import functions like: 'userDefaults', 'getAdvetisementId' for linting purposes?Thanks
Topic: App & System Services SubTopic: General Tags:
Replies
3
Boosts
0
Views
830
Activity
Dec ’19
Reply to SwiftUI Preview Runtime linking failure
Ah this is a good piece of info I was missing before. What is the dependency that is importing GoogleMaps on your behalf? Is it a public package that I could use to try to reproduce?
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
Mar ’25
productbuild: notarize .pkg with non-binary sub package
Hi, we have .pkg install package consisting of various sub packages. One of them contains presets and needs to be installed the the default preset location /Library/Audio/Presets. If this non-binary preset package is the only one in a .pkg choice notarization fails with: logFormatVersion: 1, jobId: *, status: Invalid, statusSummary: Archive contains critical validation errors, statusCode: 4000, archiveFilename: mypackage.pkg.zip, uploadDate: 2024-08-22T21:24:03.251Z, sha256: *, ticketContents: null, issues: [ { severity: error, code: null, path: mypackage.pkg.zip, message: Package mypackage.pkg.zip has no signed executables or bundles. No tickets can be generated., docUrl: null, architecture: null }, { severity: warning, code: null, path: mypackage.pkg.zip/mypackage.pkg, message: bInvalid component package: mypackage_vstpreset Distribution file's value: #com.mycompany.mypackage.vstpreset.pkgn, docUrl: null, architecture: null } ] } Not sure, but m
Topic: Code Signing SubTopic: Notarization Tags:
Replies
3
Boosts
0
Views
818
Activity
Aug ’24
Reply to Library/SPM issue with latest Xcode 11.4 beta
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.
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
Boosts
Views
Activity
Mar ’20
Swift package with resources for iOS and tvOS
I'm in the process of converting my local frameworks to local Swift packages. Things are (mostly) working well but I'm struggling with one of the packages: Package MyKit is used by an iOS and a tvOS app. It includes a storyboard for each platform. What is the most appropriate way to describe this in Package.swift? Xcode complains about iOS storyboards not being supported on tvOS so I moved them to their own targets, like this: let package = Package( name: MyKit, defaultLocalization: en, platforms: [ .tvOS(.v13) ], products: [ // Products define the executables and libraries a package produces, and make them visible to other packages. .library( name: MyKit, targets: [MyKit]), ], dependencies: [ // Dependencies declare other packages that this package depends on. // .package(url: /* package url */, from: 1.0.0), ], targets: [ // Targets are the basic building blocks of a package. A targe
Topic: App & System Services SubTopic: Core OS Tags:
Replies
2
Boosts
0
Views
1.7k
Activity
Nov ’20