electron-osx-sign | Codesign Electron macOS apps | Dektop Application library
kandi X-RAY | electron-osx-sign Summary
kandi X-RAY | electron-osx-sign Summary
electron-osx-sign minimizes the extra work needed to eventually prepare your apps for shipping, providing the most basic tools and assets. Note that the bare necessities here are sufficient for enabling app sandbox, yet other configurations for network access etc. require additional work. Check out electron-osx-sign guide for suggestions on setting up your environment and workflow for distribution or development. Please visit our wiki for walk-throughs, notes and frequently asked questions from past projects shipped with electron-packager and electron-osx-sign. It is worth noting as well that starting from Electron v1.1.1, a new mechanism was introduced to allow IPC in App Sandbox (see electron#5601); wish to have full support of legacy Electron versions, please utilize opts.version, which option brings less hassle with making default settings among Electron builds. We are trying to keep updated to the latest Electron specs; please file us an issue if having any suggestions or experiencing difficulties code signing your products.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of electron-osx-sign
electron-osx-sign Key Features
electron-osx-sign Examples and Code Snippets
Community Discussions
Trending Discussions on electron-osx-sign
QUESTION
My Electron app is made up of a frontend process and a backend child process. On macOS, the backend requires some capabilities on macOS, such as accessing user Desktop and microphone. The backend is built through Xcode and codesigned using the same developer ID separately.
Upon first run, user will be asked to give permissions according to the capabilities. On subsequent launches, the app should run smoothly without user intervention. Before codesigning through Electron that works fine.
I'm ready to codesign the app through electron-osx-sign
and expect that the app would behave normally.
When signing with Electron, I use the documented electron-forge
option this way
ANSWER
Answered 2020-Sep-30 at 03:22Solved it myself.
The problem is neither with the existing entitlement entries nor with the package.json
options, but rather a missing entitlement entry:
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install electron-osx-sign
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page