You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.
I have just upgraded my Meteor application from 1.5.2 to 126.96.36.199 and immediately noticed that OSX 10.11.6 is prompting "Do you want the application “node” to accept incoming network connections? Allow/Deny" every time Meteor re-starts the server application after a re-build.
I normally only see this prompt once after upgrading a Meteor version. I have not seen this behaviour on 1.5.2 or earlier versions.
Steps to reproduce:
Edit a client - only file. Save. Meteor does a client-only rebuild, no "accept incoming" prompt.
Edit a server - only file (I tried the in the /server folder). Save. Meteor does a server re-build and re-starts the server and OSX shows the "accept incoming" prompt.
Edit a client or server-side file in a local package. Save. Meteor re-builds and re-starts the server and OSX shows the "accept incoming" prompt.
The applications /.meteor/release file has "METEOR@188.8.131.52"
The text was updated successfully, but these errors were encountered:
changed the title
[osx] Meteor 184.108.40.206 Server re-builds always asking 'to accept incoming network connections?'Sep 27, 2017
It's built from the same source and has no other changes for macOS users (there were changes for Linux users; see #9068). Meteor 1.5.2 will need to be installed for this command to work, so if you receive an error when running it, just run meteor create --release 1.5.2 test-app-safe-to-delete somewhere to put the binary in place first.
I know why the error is happening every time, and it's related to the code-signing signature on the node binary included in 220.127.116.11. I've confirmed that the binary is identical to that which was built on our build Mac, but the build Mac hardware itself changed so something else happened in the compilation process. This is could be the root cause of #9136 as well.
$ codesign --verify -vv ~/.meteor/packages/meteor-tool/1.5.2_1/mt-os.osx.x86_64/dev_bundle/bin/node
/Users/jesse/.meteor/packages/meteor-tool/1.5.2_1/mt-os.osx.x86_64/dev_bundle/bin/node: invalid signature (code or signature have been modified)
In architecture: x86_64
$ codesign --verify -vv ~/.meteor/packages/meteor-tool/1.5.2/mt-os.osx.x86_64/dev_bundle/bin/node
/Users/jesse/.meteor/packages/meteor-tool/1.5.2/mt-os.osx.x86_64/dev_bundle/bin/node: valid on disk
/Users/jesse/.meteor/packages/meteor-tool/1.5.2/mt-os.osx.x86_64/dev_bundle/bin/node: satisfies its Designated Requirement
More details and a fix with a test to prevent this in the future coming soon.
Just FYI, I ran into delays initially because SourceForge downloads were down and they host the ICU (International Components for Unicode) dependencies necessary to build node, but later on due to some bizarre codesign issues. The full fix is still being investigated, but we hope to have an answer soon.