Search results for

“missing package product”

55,590 results found

Post

Replies

Boosts

Views

Activity

SwiftUI previews fail with a very simple SwiftPM package
I already filed feedback FB13777941 for this, but wanted to ask if anyone has the same problem, since I can't find anything on google or SO. I created a new package in Xcode (15.3) and added this to it: import SwiftUI struct Test: View { var body: some View { Text(Hello world) } } #Preview { Test() } The package builds, tests can run. Previews don't work. This is more or less the error I get from the diagnostics button (formatted for readability): LoadingError: failed to load library at path ”PATH_TO_DERIVED_DATA/Build/Intermediates.noindex/Previews/macos/PACKAGE_NAME/Products/Debug/PackageFrameworks/PACKAGE_NAME_63097C4A372B9C87_PackageProduct.framework/PACKAGE_NAME_63097C4A372B9C87_PackageProduct”: Optional(dlopen(PATH_TO_DERIVED_DATA/Build/Intermediates.noindex/Previews/macos/PACKAGE_NAME/Products/Debug/PackageFrameworks/PACKAGE_NAME_63097C4A372B9C87_PackageProduct.framework/PACKAGE_NAME_63097C4A372B9C87_PackageProduct, 0x0000): tried: 'PATH_TO_DERIVED_DATA/Build/Interme
5
0
1.7k
May ’24
PKG Installer Fails Notarytool Submission Process
I am trying to get a PKG installer through the Apple codesign and notarytool process. When I submit the PKG installer I get a status message of Invalid and when I review the log file it has 2 errors. For status summary it says: Archive contains critical validation errors, and for message it says The binary is not signed. The installer contains a flat file that is installed in the Users/Shared folder via the PKG installer. Here are the steps I've taken to get the installer through the codesign and notarytool process. codesign the file that's placed in the Users/Shared folder: codesign --options=runtime --sign 'Developer ID Application: XYZ' -v /Users/.../Documents/folder/flat file which I get a message saying signed generic. Create the PKG installer with the signed flat file. Sign the PKG installer containing the signed flat file: codesign --options=runtime --sign 'Developer ID Application: XYZ' -v /Users/.../Documents/folder/flat file which I get a message saying s
1
0
619
Feb ’25
"Package.resolved" Error with local packages
Let's say you're creating two packages on a local drive, package 'A' and package 'B'. Is it possible, in A's Package.swift file to read (from a JSON or XML file) the path to B, and then add it as a Package.Dependency? I've written my Package.swift script to do so (actually I'm resolving an alias file instead of getting the path from JSON). The problem is: although A's script definitely can read the correct relative path to B (I've logged it to the console and it's fine), no matter what I do, the build always errors out: the Package.resolved file is most likely severely out-of-date and is preventing correct resolution; delete the resolved file and try again This happens so reliably that I assume it's either the (1) script timing out, or (2) some kind of sand-boxing. Either way, the message is pretty useless. I've checked .swiftpm and I see no trace of any Package.resolved file. Deleting .swiftpm doesn't fix the issue. Can anyone shed some light? I'm out of ideas.
2
0
1.3k
Jun ’20
Package platforms not working
I am writing a package in Swift using Xcode 16.1 (swift-tools-version: 6.0) and am trying to use features that became available in later versions of macOS and iOS. The following line naturally causes a compiler error when compiling against 'My Mac': let match = test-string.firstMatch(of: /-(.+)/)! 'firstMatch(of:)' is only available in macOS 13.0 or newer I can of course fix this by using @available(macOS 13.0, *), but there are dozens of methods and I would prefer to use the platforms property in the Package file like this: platforms: [ .macOS(.v10_13), .iOS(.v16) ], However for reason that are not clear, this does not work and the compiler errors remain. I have tried cleaning, removing derived data etc. What I am doing wrong?
2
0
516
Dec ’24
.app is alright but .pkg file can't be uploaded.
macOS 10.15.5 Pycharm 2019.3.4 PyQt 5.14.0 Before packaging into .app, I installed certificates and bundled Add ID...everything was normal and .app run correctly. Then I tried to generate a .pkg file: productbuild --product path/to/info.plist --component path/of/My.app /Applications path/to/save/My.pkg things went weird. Transporter says it Failed to get App Bundle ID, while Application Loader 3.7.2 says The Info.plist indicates a Mac app, but submitting an ipa. Whai should I try to fix this? Since PyQt5 is getting popular for Mac Developers, I guess at least my issues will help others. Thank you everybody!!!!!
1
0
449
Jul ’20
macOS 15.6: Opened package is not the same at install time
I've created an installation package and it is failing to install on macOS 15.6. The package is, I believe, properly notarized, since it will install correctly on other macOS versions, including 15.5 The only clue I have is the output from installer: installer[8015] : Opened package is not the same at install time installer[8015] : Unable to use PK session due to incompatible packages. Terminating. installer[8015] : Install failed: The Installer could not install the software because there was no software found to install. The installer consists of a a single component package, and the outer product package. The component package is present, and I can successfully run installer manually to install it, so I don't think the component package is corrupt. Has anyone else encountered this? Are there any tools available to help me diagnose the issue? The logging is not helpful.
2
0
272
Aug ’25
Unable to expand package by the Application Loader
Hi,I want to upload our software to the Apple Store. Although it is not an easy task, I managed to fill all the required fields but I get stuck at uploading our software. When using the Application Loader in Xcode to upload our PKG (created by Packages, a program from Stephan Sudre) the following message appears:The package could not be unpacked because of the following error: Unable to expand package. Please make sure /Users/renedekruijf/Documents/BIMcollab ZOOM 1.0 r3.pkg is a valid installer package.I tried a number of things but I cannot find the reason why Application loader is unable to expand my package!Our program is freeware and you can download it from our own website at http://www.bimcollab.com/downloads/BIMcollab_ZOOM_1-0-7-30.dmgI appreciate it a lot if anyone can help me...Regs, René
0
0
573
Apr ’18
Are Swift Packages supported by String Catalogs?
Hello, do the String Catalogs (new in Xcode 15) support Swift Packages? I've tried adding a new Localizable.xcstrings (string catalog) file to my package's resources folder. Great! I then see this screen: All good so far. I then try to go and build my Swift Package... and nothing changes. The string catalog is never populated and I'm left with the same screen as above. So, do string catalogs not support packages at this time or am I doing something wrong? I was really hoping String Catalogs would work and save the day since Export Localizations also does not work for Swift packages that don't support macOS. 😔
9
0
6k
Jun ’23
.pkg still says 'unidentified developer' after Productsign
Hi all, anyone with experience in signing .pkg files for distribution OUTSIDE of the App Store?I'm aware this isn't the right forum, but I couldn't see an appropriate section -sorry in advance.Set up the required private key and installer certificates through the Apple Dev site.Created a .pkg with the WhiteBox Packages software.Note: the content is NOT a standard .app file - it is a set of 3 plug-in files: .component, .vst, and .vst3, which are each moved into their required location upon install.(During this stage, I used the 'identifier' provided on the Apple Dev site: e.g com.companyname.productname)Built the .pkg with no issues.Signed the .pkg using the terminal command:productsign --sign developer-ID-number /path-to-file/xyz.pkg /path-to-new-file/xyz_signed.pkgThis was successful, and the correct information comes up when using the pkgutil --check-signature command.The signed .pkg works perfectly when not quarantined, and behaves as expected.However,
2
0
845
Jun ’15
Error: Product ID already in use
Hi everyone, I created an IAP When I filled a the information in the require database, my internet was broken. When the internet in working normally, I create it again (I didn't save it before I lost my internet) The system reported an error The Product ID you entered is already being used by another in-app purchase associated with this app. Question: Why can't I reuse a Product ID that I haven't saved before? Please reply to me soon, Thank you so much
1
0
1.6k
May ’24
SPM Build tool not running when adding package to project
I have created a new project and added this Swift Package to it: https://github.com/laevandus/SwiftExampleToomasKit If I build the project it fails to compile the SPM Package saying MyGeneratedEnum is missing. This enum is generated by build tool attached to the plugin. If I open the Package.swift for the above repo and build, the enum gets generated and the framework compiles as it should. Any idea why the build tool is not executed when attaching the package to an iOS project ?
0
0
673
Mar ’23
Reply to Bundle Identifier Change Core Data Lost
This took me a while to figure out but here is how I fixed the issue.1. Change your product name under Build Settings -> Packaging -> Product Name to the desired product name. This will change you Bundle Identifier to the desired name.2. Clean your project by selecting Product -> Clean.3. Select your CoreData model in the project navigator and then select the Data Model Inspector in the Inspector tab. Change the project name under class to the new class name. I got stuck here since I did not know Spaces, dashes, . are all replaced by underscores. You can see that my Product Name is FLO-Cycling and the CoreData class is FLO_Cycling.4. If you have imported the Swift bridging header file anywhere make sure to update it.I hope this can help someone.Take care,Jon
Jun ’15
SwiftUI previews fail with a very simple SwiftPM package
I already filed feedback FB13777941 for this, but wanted to ask if anyone has the same problem, since I can't find anything on google or SO. I created a new package in Xcode (15.3) and added this to it: import SwiftUI struct Test: View { var body: some View { Text(Hello world) } } #Preview { Test() } The package builds, tests can run. Previews don't work. This is more or less the error I get from the diagnostics button (formatted for readability): LoadingError: failed to load library at path ”PATH_TO_DERIVED_DATA/Build/Intermediates.noindex/Previews/macos/PACKAGE_NAME/Products/Debug/PackageFrameworks/PACKAGE_NAME_63097C4A372B9C87_PackageProduct.framework/PACKAGE_NAME_63097C4A372B9C87_PackageProduct”: Optional(dlopen(PATH_TO_DERIVED_DATA/Build/Intermediates.noindex/Previews/macos/PACKAGE_NAME/Products/Debug/PackageFrameworks/PACKAGE_NAME_63097C4A372B9C87_PackageProduct.framework/PACKAGE_NAME_63097C4A372B9C87_PackageProduct, 0x0000): tried: 'PATH_TO_DERIVED_DATA/Build/Interme
Replies
5
Boosts
0
Views
1.7k
Activity
May ’24
PKG Installer Fails Notarytool Submission Process
I am trying to get a PKG installer through the Apple codesign and notarytool process. When I submit the PKG installer I get a status message of Invalid and when I review the log file it has 2 errors. For status summary it says: Archive contains critical validation errors, and for message it says The binary is not signed. The installer contains a flat file that is installed in the Users/Shared folder via the PKG installer. Here are the steps I've taken to get the installer through the codesign and notarytool process. codesign the file that's placed in the Users/Shared folder: codesign --options=runtime --sign 'Developer ID Application: XYZ' -v /Users/.../Documents/folder/flat file which I get a message saying signed generic. Create the PKG installer with the signed flat file. Sign the PKG installer containing the signed flat file: codesign --options=runtime --sign 'Developer ID Application: XYZ' -v /Users/.../Documents/folder/flat file which I get a message saying s
Replies
1
Boosts
0
Views
619
Activity
Feb ’25
"Package.resolved" Error with local packages
Let's say you're creating two packages on a local drive, package 'A' and package 'B'. Is it possible, in A's Package.swift file to read (from a JSON or XML file) the path to B, and then add it as a Package.Dependency? I've written my Package.swift script to do so (actually I'm resolving an alias file instead of getting the path from JSON). The problem is: although A's script definitely can read the correct relative path to B (I've logged it to the console and it's fine), no matter what I do, the build always errors out: the Package.resolved file is most likely severely out-of-date and is preventing correct resolution; delete the resolved file and try again This happens so reliably that I assume it's either the (1) script timing out, or (2) some kind of sand-boxing. Either way, the message is pretty useless. I've checked .swiftpm and I see no trace of any Package.resolved file. Deleting .swiftpm doesn't fix the issue. Can anyone shed some light? I'm out of ideas.
Replies
2
Boosts
0
Views
1.3k
Activity
Jun ’20
autoAdjustmentFilters missing?
Seems the method for -(NSArray *)autoAdjustmentFilters has gone missing from CIImage in iOS 9.0 SDK? Or is it just me...
Replies
1
Boosts
0
Views
382
Activity
Jun ’15
How can I keep Installer from relocating packages?
If there's another version of our app on the volume, it'll relocate the installed one there. This is particularly delightful, since nothing will work if it's not in /Applications. We use pkgbuild and productbuild to create the .pkg file.
Replies
4
Boosts
0
Views
1.7k
Activity
Jan ’24
Swift Package Manager and AWS
I am trying to create a simple Swift package that uses AWS SDK for Swift but I get an error that says it can't import one of the modules, actually any of the modules. I researched this for a couple of days but can't figure out how to get this working. Any help would be appreciated.
Replies
1
Boosts
0
Views
274
Activity
May ’25
Package platforms not working
I am writing a package in Swift using Xcode 16.1 (swift-tools-version: 6.0) and am trying to use features that became available in later versions of macOS and iOS. The following line naturally causes a compiler error when compiling against 'My Mac': let match = test-string.firstMatch(of: /-(.+)/)! 'firstMatch(of:)' is only available in macOS 13.0 or newer I can of course fix this by using @available(macOS 13.0, *), but there are dozens of methods and I would prefer to use the platforms property in the Package file like this: platforms: [ .macOS(.v10_13), .iOS(.v16) ], However for reason that are not clear, this does not work and the compiler errors remain. I have tried cleaning, removing derived data etc. What I am doing wrong?
Replies
2
Boosts
0
Views
516
Activity
Dec ’24
.app is alright but .pkg file can't be uploaded.
macOS 10.15.5 Pycharm 2019.3.4 PyQt 5.14.0 Before packaging into .app, I installed certificates and bundled Add ID...everything was normal and .app run correctly. Then I tried to generate a .pkg file: productbuild --product path/to/info.plist --component path/of/My.app /Applications path/to/save/My.pkg things went weird. Transporter says it Failed to get App Bundle ID, while Application Loader 3.7.2 says The Info.plist indicates a Mac app, but submitting an ipa. Whai should I try to fix this? Since PyQt5 is getting popular for Mac Developers, I guess at least my issues will help others. Thank you everybody!!!!!
Replies
1
Boosts
0
Views
449
Activity
Jul ’20
macOS 15.6: Opened package is not the same at install time
I've created an installation package and it is failing to install on macOS 15.6. The package is, I believe, properly notarized, since it will install correctly on other macOS versions, including 15.5 The only clue I have is the output from installer: installer[8015] : Opened package is not the same at install time installer[8015] : Unable to use PK session due to incompatible packages. Terminating. installer[8015] : Install failed: The Installer could not install the software because there was no software found to install. The installer consists of a a single component package, and the outer product package. The component package is present, and I can successfully run installer manually to install it, so I don't think the component package is corrupt. Has anyone else encountered this? Are there any tools available to help me diagnose the issue? The logging is not helpful.
Replies
2
Boosts
0
Views
272
Activity
Aug ’25
Unable to expand package by the Application Loader
Hi,I want to upload our software to the Apple Store. Although it is not an easy task, I managed to fill all the required fields but I get stuck at uploading our software. When using the Application Loader in Xcode to upload our PKG (created by Packages, a program from Stephan Sudre) the following message appears:The package could not be unpacked because of the following error: Unable to expand package. Please make sure /Users/renedekruijf/Documents/BIMcollab ZOOM 1.0 r3.pkg is a valid installer package.I tried a number of things but I cannot find the reason why Application loader is unable to expand my package!Our program is freeware and you can download it from our own website at http://www.bimcollab.com/downloads/BIMcollab_ZOOM_1-0-7-30.dmgI appreciate it a lot if anyone can help me...Regs, René
Replies
0
Boosts
0
Views
573
Activity
Apr ’18
Are Swift Packages supported by String Catalogs?
Hello, do the String Catalogs (new in Xcode 15) support Swift Packages? I've tried adding a new Localizable.xcstrings (string catalog) file to my package's resources folder. Great! I then see this screen: All good so far. I then try to go and build my Swift Package... and nothing changes. The string catalog is never populated and I'm left with the same screen as above. So, do string catalogs not support packages at this time or am I doing something wrong? I was really hoping String Catalogs would work and save the day since Export Localizations also does not work for Swift packages that don't support macOS. 😔
Replies
9
Boosts
0
Views
6k
Activity
Jun ’23
.pkg still says 'unidentified developer' after Productsign
Hi all, anyone with experience in signing .pkg files for distribution OUTSIDE of the App Store?I'm aware this isn't the right forum, but I couldn't see an appropriate section -sorry in advance.Set up the required private key and installer certificates through the Apple Dev site.Created a .pkg with the WhiteBox Packages software.Note: the content is NOT a standard .app file - it is a set of 3 plug-in files: .component, .vst, and .vst3, which are each moved into their required location upon install.(During this stage, I used the 'identifier' provided on the Apple Dev site: e.g com.companyname.productname)Built the .pkg with no issues.Signed the .pkg using the terminal command:productsign --sign developer-ID-number /path-to-file/xyz.pkg /path-to-new-file/xyz_signed.pkgThis was successful, and the correct information comes up when using the pkgutil --check-signature command.The signed .pkg works perfectly when not quarantined, and behaves as expected.However,
Replies
2
Boosts
0
Views
845
Activity
Jun ’15
Error: Product ID already in use
Hi everyone, I created an IAP When I filled a the information in the require database, my internet was broken. When the internet in working normally, I create it again (I didn't save it before I lost my internet) The system reported an error The Product ID you entered is already being used by another in-app purchase associated with this app. Question: Why can't I reuse a Product ID that I haven't saved before? Please reply to me soon, Thank you so much
Replies
1
Boosts
0
Views
1.6k
Activity
May ’24
SPM Build tool not running when adding package to project
I have created a new project and added this Swift Package to it: https://github.com/laevandus/SwiftExampleToomasKit If I build the project it fails to compile the SPM Package saying MyGeneratedEnum is missing. This enum is generated by build tool attached to the plugin. If I open the Package.swift for the above repo and build, the enum gets generated and the framework compiles as it should. Any idea why the build tool is not executed when attaching the package to an iOS project ?
Replies
0
Boosts
0
Views
673
Activity
Mar ’23
Reply to Bundle Identifier Change Core Data Lost
This took me a while to figure out but here is how I fixed the issue.1. Change your product name under Build Settings -> Packaging -> Product Name to the desired product name. This will change you Bundle Identifier to the desired name.2. Clean your project by selecting Product -> Clean.3. Select your CoreData model in the project navigator and then select the Data Model Inspector in the Inspector tab. Change the project name under class to the new class name. I got stuck here since I did not know Spaces, dashes, . are all replaced by underscores. You can see that my Product Name is FLO-Cycling and the CoreData class is FLO_Cycling.4. If you have imported the Swift bridging header file anywhere make sure to update it.I hope this can help someone.Take care,Jon
Replies
Boosts
Views
Activity
Jun ’15