Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Testing MAS builds locally
See original GitHub issue- Version: 12.0.3
- Target: MAS
Running MAS builds locally no longer works, due to changes in Apple guidelines and electron-osx-sign documented here: https://github.com/electron-userland/electron-osx-sign/pull/105#issuecomment-260211431
Recently, the com.apple.developer.team-identifier entitlement was added to all new Mac provisioning profiles. This means that, going forward, distribution builds of Mac apps cannot be run directly; they are for submitting to iTunes Connect for app review only.
@develar’s suggestion from another issue is to provide a mas-dev build target to fix this issue: https://github.com/electron-userland/electron-builder/issues/897#issuecomment-270881631
Issue Analytics
- State:
- Created 7 years ago
- Reactions:11
- Comments:16 (11 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
At first it didn’t work for me. It did when I added the dev provisioning profile into the same folder. To create a dev profile I had to create a dev certificate and specify the UUID of the machines I want to run the app on.
I was able to build a
mastarget that runs locally by setting"type": "development"in electron-builder’s config, and placing myApp_Development.provisionprofilein the project directory. 🎉However, I also had to remove all but one “Mac Developer” key from my keychain, or else electron-builder would attempt to use the wrong identity, and setting CSC_NAME did not work.