-
Notifications
You must be signed in to change notification settings - Fork 219
Support for unsigned builds of the MacOS app #1803
Conversation
…quire Apple developer certificates setup.
I'll have to defer to @yknl on this review, as I've never done macOS builds. |
To help reviewers - here is a working TravisCI build config that uses a typical/stock MacOS environment: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey, it didn't work for me before, but I tried again and it worked! Very cool.
* Add error messaging for when the browser server script processes terminate from error
@hstove I made a considerable change to this PR with the removal of nexe. I think you should revoke the PR approval and re-review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good updates. I built the app successfully.
I'm not sure how to test the CORS proxy that is built. Any help there?
The production build is now working. I tested the CORS proxy with curl:
|
If I remember correctly, the CORS proxy works a bit differently in the windows build. We'll have to test that out as well. |
Doesn't this not touch the Windows build? |
A few new build scripts for building the native MacOS app without having the $100 Apple developer certificate or needing access to the private PBC cert.
Useful for CI automated building &
Blockstack.app
artifact publishing as well. See commit 96c5c82 for the travisCI build config, which we can PR after this one, if wanted.