missing package product

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

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.

in my xcode project, i created a new package by going through File > New > Package, just like they said in https://developer.apple.com/documentation/xcode/organizing-your-code-with-local-packages I have a package, but the problem is, whenever I made any changes in the package's source code, it never showed in the main project. I can import the package just fine, but the package does not show anything. no added apis, functions, nothing. Im using Xcode 26.0.1

I am unable to find MacOS 11.5.1 Beta updates after installing the profile.During installation, I get the warning that The package was signed with a certificate that has expired. If you acquired this package recently, it may not be authentic. Do you want to continue with the installation anyway? I continued and it seemed to install correctly - however Software Update has not found the beta 3 update for the past 2 days. I have wiped and reinstalled the Macbook Air three times. I also get the same warning when installing - SF Pro Fonts- SF Symbols AppI am a member of an active Apple Developer account.

Hi there, I installed tensorflow-metal as per this tutorial.. That installation process seems to have worked fine. However, I'm now having trouble creating new Conda envs. The problem seems to be with the version of Conda -- Miniforge -- which Apple's tutorial instructed me to install. So, this command: conda create --name my_env python=3.7 -c defaults -c conda-forge --file requirements/conda.txt Results in this error: PackagesNotFoundError: The following packages are not available from current channels: - keras==2.3.1 - python=3.7 - scikit-geometry[version='>=0.1.2'] - tesserocr[version='>=2.5.1'] Current channels: - https://repo.anaconda.com/pkgs/main/osx-arm64 - https://repo.anaconda.com/pkgs/main/noarch - https://repo.anaconda.com/pkgs/r/osx-arm64 - https://repo.anaconda.com/pkgs/r/noarch - https://conda.anaconda.org/conda-forge/osx-arm64 - https://conda.anaconda.org/conda-forge/noarch When I was using Miniconda, I had no problems installing these packages

Hi moderators,Since yesterday we've been experiencing failures in payments on Production due to an issue with the App Store payment system.I've spoken to about half a dozen people at Apple, but there seems to be NO information anywhere as to an acknowledgement this is occurring or any timescale with regard to a fix.This isn't just our application either - this is occurring on many applications in the App Store since yesterday.I've filed a bug: 31366677Please can someone give us an update on this - we are losing a SIGNIFICANT amount of money!Col.

In Xcode 11.5, removing a Swift package dependency from Xcode workspace does not delete the checkout data in the DerivedData. Is this behavior expected? If not, has it been fixed in Xcode 12? Should I file a radar?

I would very much like to store some additional data in my SwiftData document package, outside of SwiftData. Metadata about the document that doesn't lend itself well to the underlying RDBMS nature of SwiftData. Is that possible?

I noticed the following message when creating a pkg installer: [WARNING]: Specifying [allow-external-scripts='true'] is deprecated. Having this in your distribution will break the installability of this product in an upcoming release of macOS. Apple reserves the right to reject notarization of any product with this option. I have a couple of questions about that: Which upcoming release? Ventura? I am trying to figure out the timeline here. Whats the replacement for this feature? We are depending on it in our installers. I tried googling the answers but came up empty so I would appreciate some input on this from Apple.

I'd like to know if there is a new property we can use in the definition of a Swift Package in the new Xcode 26, where we can set the whole package to run on Main Actor, as we have it in our apps for Xcode 26.

I think I understand notarization:It sends binary to AppleApple performs automatic verificationIf verification succeeds, (and perhaps this is the wrong terminology) a Notarization Ticket is stored on Apple's serversWhen an end user goes to use the Notarized Binary, macOS requests a Notarization Ticket for the binary, and if this succeeds, then all is good. This, of course, requires a network connection on the end user's machine when the binary is (first?, always?) accessed. It seems pretty clear from the staple tool that the ticket is cached locally, so while it may be verified every time, it only needs to be downloaded once.Stapling is a post-process step that downloads the Notarization Ticket and attaches it to the binary (before distribution) so that the end user's machine can verify the Notarization without a network connection back to Apple being available at all.As of 10.14.5, kexts MUST be notarized in order to be loaded. Again, it is not clear if this verification is on every load, or only the first l

My project has an iOS and WatchOS app. I added a package dependency, which supports both iOS and WatchOS, though I have only added the library to my iOS app. I can compile and run both apps just fine but when I try to use one of the WatchOS app views in Canvas preview I get errors saying different properties defined in the packages files are not available on watchOS. These blocks of code that give errors are wrapped in: if TARGET_OS_IPHONE. I have selected the Watch Target and a watch device in the run selector as well as in the canvas. Why is this failing and how can I get it working? Thanks

I have an app that uses SPM. One of my packages contains resources (.xib files). While trying to upload the app to TestFlight I get an error which is a known issue, pointed here: https://developer.apple.com/news/releases/?id=06232020a as a last bullet: Apps that use Swift packages containing resources are not successfully imported. As a workaround, manually remove the CFBundleExecutable keys from the Info.plist files of the embedded resource bundles. My question is how to use that workaround? My packages don't contain an Info.plist file.