notarize

MacOS Notarize - Gatekeeper does not recognize notarized app

穿精又带淫゛_ 提交于 2021-02-08 02:18:00
问题 I have a MacOS app and want to distribute to beta users as DMG file outside AppStore. I have read some articles about how to notarize an app and follow the steps to successfully notarize the DMG file without any problem. My development machine runs on MacOS 10.14, and XCode version is 10.1. However when I try to check the notarized DMG file on another testing machine which runs on MacOS 10.14.5 (by sending the file via AirDrop, or download from my website), I still see the popup from

MacOS Notarize - Gatekeeper does not recognize notarized app

不打扰是莪最后的温柔 提交于 2021-02-08 02:12:55
问题 I have a MacOS app and want to distribute to beta users as DMG file outside AppStore. I have read some articles about how to notarize an app and follow the steps to successfully notarize the DMG file without any problem. My development machine runs on MacOS 10.14, and XCode version is 10.1. However when I try to check the notarized DMG file on another testing machine which runs on MacOS 10.14.5 (by sending the file via AirDrop, or download from my website), I still see the popup from

Signing, Notarizing, hardening, etc. a macOS command-line binary?

微笑、不失礼 提交于 2021-02-07 09:27:31
问题 What are the most appropriate ways to harden, code-sign, notarize, package, etc., a command-line binary (stdin, stdout, etc., no windows or icons) to allow distribution of the binary to macOS Catalina users, so that they can run the utility with the least amount of pain/hassle? Assume the default/stock OS configuration of GateKeeper, etc. Assume the users most likely currently don't have the installed tools or skills to compile from source. Assume that a Terminal window popping up when

Signing, Notarizing, hardening, etc. a macOS command-line binary?

时光怂恿深爱的人放手 提交于 2021-02-07 09:27:23
问题 What are the most appropriate ways to harden, code-sign, notarize, package, etc., a command-line binary (stdin, stdout, etc., no windows or icons) to allow distribution of the binary to macOS Catalina users, so that they can run the utility with the least amount of pain/hassle? Assume the default/stock OS configuration of GateKeeper, etc. Assume the users most likely currently don't have the installed tools or skills to compile from source. Assume that a Terminal window popping up when

Electron notarization failed due to “The binary uses an SDK older than the 10.9 SDK.”

◇◆丶佛笑我妖孽 提交于 2021-01-28 13:17:06
问题 I'm trying to get notarization working for my electron app. Apple failed to notarize my App due to "The binary uses an SDK older than the 10.9 SDK". I assume it refers to MacOS SDK. I could not find reference in Electron documentation about how to configure MacOS SDK version being used in the building process. I'm using Xcode 10.1, Electron 4.0.0, Electron-builder 20.44.4. My question comes down to what actually controls the SDK version used by electron? Is it Xcod, Electron version or some

Electron notarization failed due to “The binary uses an SDK older than the 10.9 SDK.”

好久不见. 提交于 2021-01-28 13:11:11
问题 I'm trying to get notarization working for my electron app. Apple failed to notarize my App due to "The binary uses an SDK older than the 10.9 SDK". I assume it refers to MacOS SDK. I could not find reference in Electron documentation about how to configure MacOS SDK version being used in the building process. I'm using Xcode 10.1, Electron 4.0.0, Electron-builder 20.44.4. My question comes down to what actually controls the SDK version used by electron? Is it Xcod, Electron version or some

Notarize existing Java application for MacOS Catalina

回眸只為那壹抹淺笑 提交于 2020-08-23 06:53:46
问题 I distribute a Java application for MacOS, it is developer signed but not notarized. Not really sure where to start with this since the documentation is so biased towards creating apps with Xcode that I do not use, but I just want the simplest way to notarize my app and then move on. Reading the documentation I have a few concerns already: I am currently using Java 8, is it possible to notarize a Java 8 app or do I need to move to Java 11. I would rather not move to Java 11 because it would

Java Notarization of libAppleScriptEngine.dylib failing with The binary uses an SDK older than the 10.9 SDK

谁都会走 提交于 2020-05-16 19:15:01
问题 End of 2019 I had basic notarization of my Java 8 application working, on February 2020 Apple tightened the rules regarding notarization and this stopped my application from being notarized. Since I needed to move to Java 11 anyway I switched to Java 11 as I understood that this could be notarized ok and made necessary code changes but still having some problems. Specifically there is an option in my application to communicate with Apple Music app (formerly iTunes) using Applescript to

Java Notarization of libAppleScriptEngine.dylib failing with The binary uses an SDK older than the 10.9 SDK

纵然是瞬间 提交于 2020-05-16 19:12:50
问题 End of 2019 I had basic notarization of my Java 8 application working, on February 2020 Apple tightened the rules regarding notarization and this stopped my application from being notarized. Since I needed to move to Java 11 anyway I switched to Java 11 as I understood that this could be notarized ok and made necessary code changes but still having some problems. Specifically there is an option in my application to communicate with Apple Music app (formerly iTunes) using Applescript to

macOS notarization: altool cannot be found

好久不见. 提交于 2020-05-15 06:40:26
问题 I wanted to start building a notarization automation script. However, when I try to use the 'xcrun altool' in Terminal, I get the following error: xcrun: error: unable to find utility "altool", not a developer tool or in PATH I'm on macOS 10.14.5, Xcode 10.2.1. I then especially downloaded and installed Xcode Command Line Tools - still get same error. Other tools like stapler do work. I checked this dir and altool is not there: /Library/Developer/CommandLineTools/usr/bin Any idea what's going