{"action":"created","issue":{"url":"https://api.github.com/repos/matryer/bitbar/issues/304","repository_url":"https://api.github.com/repos/matryer/bitbar","labels_url":"https://api.github.com/repos/matryer/bitbar/issues/304/labels{/name}","comments_url":"https://api.github.com/repos/matryer/bitbar/issues/304/comments","events_url":"https://api.github.com/repos/matryer/bitbar/issues/304/events","html_url":"https://github.com/matryer/bitbar/issues/304","id":143867495,"number":304,"title":"BitBar app is unsigned and therefore will not be executed.","user":{"login":"chrisidefix","id":382555,"avatar_url":"https://avatars.githubusercontent.com/u/382555?v=3","gravatar_id":"","url":"https://api.github.com/users/chrisidefix","html_url":"https://github.com/chrisidefix","followers_url":"https://api.github.com/users/chrisidefix/followers","following_url":"https://api.github.com/users/chrisidefix/following{/other_user}","gists_url":"https://api.github.com/users/chrisidefix/gists{/gist_id}","starred_url":"https://api.github.com/users/chrisidefix/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/chrisidefix/subscriptions","organizations_url":"https://api.github.com/users/chrisidefix/orgs","repos_url":"https://api.github.com/users/chrisidefix/repos","events_url":"https://api.github.com/users/chrisidefix/events{/privacy}","received_events_url":"https://api.github.com/users/chrisidefix/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2016-03-28T01:19:42Z","updated_at":"2016-03-28T09:24:09Z","closed_at":null,"body":"BitBar releases are unsigned. Checking with `codesign -dv BitBar.app` returns: `BitBar.app: code object is not signed at all`. Of course many people can compile this themselves, but the question should be raised if you expect **everyone** to compile this themselves?\r\n\r\nIt looks like with the latest OS X upgrade to 10.11.4 Apple may have made it harder to execute unsigned code. *It used to be possible to just* **Right-Click + Open** *any app, which would then ask if you are sure you want to execute this downloaded application, but this didn't work for some reason when I installed the latest BitBar.app. I only got this Console output now when trying to start BitBar:*\r\n\r\n```\r\n28/03/2016 10:55:13.000 AM kernel[0]: OSTIARIUS: /Applications/BitBar.app/Contents/MacOS/BitBar is from the internet & is unsigned -> BLOCKING!\r\n28/03/2016 10:55:13.187 AM com.apple.xpc.launchd[1]: (com.apple.xpc.launchd.oneshot.0x1000001a.BitBar[32020]) Service exited due to signal: Killed: 9\r\n```\r\n\r\nThe way to fix it was to go into the `BitBar.app/Contents/MacOS` package folder and do the **Right Click + Open** *trick* on the executable right there. I then had to do this *again* on the `BitBar.app` to be able to run it. This seems a little complicated for average users and I was wondering if BitBar should be released with  **signed code**?\r\n\r\nI am not 100% sure about Apple's signing process, but I know you can get a certificate without paying for the developer program. You can sign apps without paying the annual fee to Apple, but I am not sure if those signatures then count as \"identified developers\". It wouldn't be complicated to do, though (just add the signature when you build the release in Xcode).\r\n"},"comment":{"url":"https://api.github.com/repos/matryer/bitbar/issues/comments/202318892","html_url":"https://github.com/matryer/bitbar/issues/304#issuecomment-202318892","issue_url":"https://api.github.com/repos/matryer/bitbar/issues/304","id":202318892,"user":{"login":"iosdeveloper","id":655921,"avatar_url":"https://avatars.githubusercontent.com/u/655921?v=3","gravatar_id":"","url":"https://api.github.com/users/iosdeveloper","html_url":"https://github.com/iosdeveloper","followers_url":"https://api.github.com/users/iosdeveloper/followers","following_url":"https://api.github.com/users/iosdeveloper/following{/other_user}","gists_url":"https://api.github.com/users/iosdeveloper/gists{/gist_id}","starred_url":"https://api.github.com/users/iosdeveloper/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/iosdeveloper/subscriptions","organizations_url":"https://api.github.com/users/iosdeveloper/orgs","repos_url":"https://api.github.com/users/iosdeveloper/repos","events_url":"https://api.github.com/users/iosdeveloper/events{/privacy}","received_events_url":"https://api.github.com/users/iosdeveloper/received_events","type":"User","site_admin":false},"created_at":"2016-03-28T09:24:09Z","updated_at":"2016-03-28T09:24:09Z","body":"We just started automating our builds using Travis CI, so we would need to look into codesigning there. FWIW, I didn't run into any issues with our release builds so far, so I'm interested to hear if this is a common problem now."}}