bukinoshita/taskr

Error: Could not get code signature for running application

yeskunall opened this issue ยท 5 comments

screen shot 2018-01-06 at 8 21 32 am

Hey ๐Ÿ‘‹

As you can see, the binary crashes because you are using the autoUpdater API on a non-codesigned application.

Maybe there's a few steps missing in the README? ๐Ÿ˜…

Hey, my bad.

Can you try this?

If you have issues in the codesign step when running yarn run dist on macOS, you can temporarily disable code signing locally by setting export CSC_IDENTITY_AUTO_DISCOVERY=false for the current terminal session.

All right @bukinoshita, what you suggested should have worked, but I'm still getting the same error, although it does emit a message saying CSC_IDENTITY_AUTO_DISCOVERY was disabled. So I'm not sure what's going on there. I'll investigate a bit more.

I had a question of my own tho, that came up by playing around with macOS yesterday (I recently switched over to macOS, so it's all a bit new to me ๐Ÿ˜…): any reason why a binary needs to be created before we can test the app in development?

If you want to just run locally you can run yarn start and it should open the app. yarn dist you are actually creating the binaries.

@yeskunall were you able to run?

I can run yarn start, so I can set up a dev workflow, but setting that flag to false didn't seem to work for me. I'm gonna close this until I can come back to you with more on this. Thanks @bukinoshita ๐Ÿ’–