“missing package product”

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?

Hi,I have this problem when i try to get products:2017-09-28 12:06:33.990805+0200 InAppPurchases[3546:1660532] RMStore: products request received response 2017-09-28 12:06:33.990956+0200 InAppPurchases[3546:1660532] RMStore: invalid product with id singolaPartitaSerieCAnyone can help me?Thanks

I spend days figuring out the proper steps to make it work. Can anyone give hints? Using xcode's Manage Certificate I'm creating a Mac Installer Distribution certificate but while I run the command security find-identity -p codesigning -v I see nothing. However, if I create any other certificate I can see it using that command. Due to the problem with cert generation I receive an error in Transporter : The product archive package's signature is invalid. Ensure that it is signed with your 3rd Party Mac Developer Installer certificate I already deleted all and recreated it using xcode, and also created using https://developer.apple.com/account/resources/certificates/list and downloaded it. What should I do?

I'm using CoreData+CloudKit. It works fine in development, so I deployed to production. But I cannot see the data in CloudKit DataBase in a testflight version. I don't know where I missed. Can I just run in Release mode to check it works?

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,

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.

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 ?

I am getting the following error when trying to submit a package to iTunesConnect. Unable to process validateAssets request at this time due to a general error (1017) Any issues in Apple?

Out iOS app consists of a main project and several swift packages under a workspace. Every time I open the workspace, I end up with Xcode 14 being unusable for 10+ seconds, being stuck on Resolving package graph Adding/renaming/deleting files to any of the swift packages we have seems to trigger this as well. Has anyone experienced this as well?

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!!!!!

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é