“missing package product”

When i try to install applications in my macbook pro it shows me this and m using macOS Catalina (Version 10.15.6) This package is incompatible with this version of macOS. Please Help Thank You! (:

Hi! I am wondering if there is a way to enable resources from a Swift Package to be stored with the ODR system? I have tried moving my asset catalogs to a Swift Package and while my tags for each asset were intact, the assets disappeared from the Resource Tags tab in the Project Settings. Is there any other way to make them work? I would love to be able to move these asset catalogs to a package to make the project more modular and this is a blocker for me at the moment.

My program is packaged with the package program. I want to get the current directory of the current PKG package file when PKG installs.

The incomplete app indication is a yellow clock icon labeled “Missing Metadata.” That label is so vague and doesn’t provide any guidance on what’s actually required. It would be very helpful if the indicator specified which metadata is missing, so the App Store Connect user can understand what still needs to be configured.

We verify the signature of our install pkg files using a combination of xar calls and the crypto functions in Security framework. This has worked fine for a long time, using the productsign utility on macOS 10.11 (with Xcode 7 or 8, SDK 10.11 I think).Now we are updating our build environment to Mojave, Xcode 10, and the 10.14 SDK. The pkg files that are signed in this environment no longer pass verification using our working code. This same code (built in the new Mojave/Xcode10/SDK10..14 env) can still verify the older pkg files. But files signed with the new productsign can't be verified with our code whether that code is built in our old or new env. Of course, pkgutil shows that all the pkg sigs are valid.So... what changed in the new tools that would somehow create a non-verifiable signature? Is there any documentation on how pkg files are signed? Any docs on an Apple-sanctioned method for verifying pkg signatures programmatically? I'm happy to explain

Seems the method for -(NSArray *)autoAdjustmentFilters has gone missing from CIImage in iOS 9.0 SDK? Or is it just me...

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.

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?

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?

Hi. I have a project that uses packages which have git repos. The problem is, I want to test some things before updating the master branch on the repo. How can I make Xcode use the local version so I can test? Thanks.

productsign Command Appears to Succeed but Package has No Valid Signature Category: Security, macOS, Code Signing Question: productsign command, when signing a PKG created with productbuild, appears to succeed with a success message (Wrote signed product archive to ...) but spctl verification results in rejected, source=no usable signature, indicating that the signature was not actually applied. Details: Goal: To sign a distribution package created with productbuild using a Developer ID Installer certificate. Certificate Used: Developer ID Installer: [Company Name] ([Team ID]) This certificate was issued by Previous Sub-CA and is not the latest G2 Sub-CA recommended by Apple. We cannot create a new G2 Sub-CA certificate as we have reached the limit of 5. productsign Command: productsign --sign Developer ID Installer: [Company Name] ([Team ID]) [input.pkg] [output.pkg] productsign Output: Wrote signed product archive to [output.pkg] (Appears as a success message). s