Search results for

“missing package product”

55,547 results found

Post

Replies

Boosts

Views

Activity

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
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 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
605
Feb ’20
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
Topic: Developer Tools & Services SubTopic: Xcode Tags:
0
0
238
Jun ’25
*.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
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.3k
Aug ’19
Reply to Is iTunes Connect broken or down?
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.
Topic: App Store Distribution & Marketing SubTopic: App Store Connect Tags:
Replies
Boosts
Views
Activity
Dec ’17
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!
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
0
Boosts
0
Views
668
Activity
Apr ’18
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
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
Topic: Accessibility & Inclusion SubTopic: General Tags:
Replies
1
Boosts
0
Views
936
Activity
May ’23
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.
Topic: App Store Distribution & Marketing SubTopic: General Tags:
Replies
Boosts
Views
Activity
Apr ’22
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 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 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.
Topic: Code Signing SubTopic: Certificates, Identifiers & Profiles Tags:
Replies
Boosts
Views
Activity
May ’16
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?
Topic: App & System Services SubTopic: Core OS Tags:
Replies
0
Boosts
0
Views
895
Activity
Mar ’22
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
605
Activity
Feb ’20
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
Topic: Developer Tools & Services SubTopic: Xcode Tags:
Replies
0
Boosts
0
Views
238
Activity
Jun ’25
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
*.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
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.3k
Activity
Aug ’19