missing package product

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

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

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?

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.

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

I have an unreleased Mac application on iTunes Connect for which I would like to create an In-App Purchase Product. When I created the Bundle, I selected the option to allow In-App Purchases. While I can see my app as Prepare for submission, I don't have any options relating to In-App Purchase Products. Why am I missing this option?

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

Does Apple Do the Product Testing anymore? If so how to you join?

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 am having troubles notarizing an installer package. I created an installer package using the pkgbuild and productbuild, and then I tried to notarize it with notarytool, but I got an error message. The error message led me to Use a valid Developer ID certificate, which includes the statement Sign installer packages with a Developer ID Installer certificate The app is signed with the team Developer ID and is notarized (via Xcode). I signed both packages (during pkgbuild and productbuild) with a certificate created when I clicked Mac Installer Distribution in the developer portal, and it created a certificate named 3rd Party Mac Developer Installer: my company Is this the wrong certificate? If it is the wrong certificate, which one should I create in the developer portal? (I didn't see anything specified as Developer ID Installer) If it is the right certificate, any idea what I might have done wrong? Note: The reason I am trying to notarize the installer package is