Search results for

missing package product

51,818 results found

Post

Replies

Boosts

Views

Activity

Reply to sctl -a reports Rejected even Notarization Status reports Approved
This is odd. Have you tried creating a dummy Swift project (choose one of Xcode's starter template projects that uses Swift) then code-sign and notarize it using the same pipeline that you use for your normal app? This is to eliminate the issues coming from your developer account or your system. A sample project should get notarized just fine and run without gatekeeper issues.Furthermore I see that you're using a .zip file as your end product. As these can't be stapled (i.e. have embedded notarization results), is it possible to switch to either .dmg or .pkg distribution instead? Then staple the notarization results before you validate it using spctl.It is also possible that the notarization result was not yet available to Gatekeeper when you run spctl. That is, notarization talks to server A whereas Gatekeeper talks to server B. In turn A haven't told B of your just-notarized package. If you staple the notarization results into your redistributable product, Gatekeeper won'
Topic: Code Signing SubTopic: General Tags:
Mar ’20
tensorflow-metal and other Conda packages
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
2
0
4.1k
Jul ’21
Notarizing installer package; which certificate?
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
2
0
1.2k
Nov ’23
Problems with SwiftUI preview and packages
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
0
0
532
Jul ’24
Reply to how to sign my kext.
Below is the screen-shot, did I miss any steps?This sounds kinda silly but did you scroll down on that page? Developer ID is a production certificate, and thus you should expect to find it at the end of the Production list.Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1 + @apple.com
Topic: App & System Services SubTopic: Core OS Tags:
Dec ’15
Reply to MacOS application: How to become an identified developer?
I am generating the pkg file using productbuild 3rd Party Mac Developer Installer: command. That is a Mac App Store signing identity. If you want to ship outside of the Mac App Store, you must sign your package with your Developer ID Installer signing identity. For more on this and many other hints, see my Signing a Mac Product For Distribution - https://forums.developer.apple.com/thread/128166 post. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @apple.com
Topic: Code Signing SubTopic: General Tags:
Aug ’20
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
546
Feb ’25
IAP NOT WORKING IN PRODUCTION!
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.
5
0
3.1k
Mar ’17
Replace Xcode Project with Swift Package while keeping same repo?
Hi, I'm currently refactoring my Xcode project into a Swift Package with multiple modules, which I combine with a lightweight Xcode project using an XCWorkspace (kind of like Pointfree's isowords). Right now, my Xcode project is hosted on a GitHub repo. However, with this refactoring, it's the Swift Package which will be hosted on GitHub. Can I replace my Xcode project with the Swift Package on the repo, without losing all my history? Will the history of files inside my Xcode project still show up?
0
0
493
Jun ’21
Using a SwiftUI View in app from a Package
Let's say I have a public content view in a package. public struct SwiftUIView: View { public var body: some View { Text(Hello, world from within a package!).padding() } } How would I implement that in an app to replace the default ContentView. struct ContentView: View { var body: some View { Text(Hello, world!).padding() } } What I am attempting to do is have a complete logic flow within a package, and use this flow inside an app. With storyboards I am able; in the app, is to access the flow within the framework through the use of storyboard references. As the app launches the framework's view controller is launched. Is this possible in SwiftUI ? Thank you
1
0
918
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
216
Aug ’25
Reply to Network Extension for iOS and MacOS. Is there any difference?
While they share a lot of common architecture, which means you’ll be able to share a lot of code, there are significant differences between NE packet tunnel providers on macOS and iOS. Foremost is that macOS allows a packet tunnel provider to be packaged as either an app extension or a system extension, whereas iOS only supports appex packaging. Packaging as a sysex allows your product to be distributed outside of the Mac App Store. See TN3134 Network Extension provider deployment for all the details. If you stick with appex packaging then things are very similar to iOS. If you switch to sysex packaging there are significantly more changes: You need to activate your sysex with the System Extensions framework. Your provider then runs inside your sysex. Which runs as root, although still sandboxed. And that presents some exciting challenges for app-to-provider IPC. Oh, and with regards the iOS memory limits, those do not apply on macOS. Share and Enjoy — Qui
Topic: App & System Services SubTopic: Core OS Tags:
May ’23