Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

After update: "Could not get code signature for running application" #357

Open
mitchhentges opened this issue Dec 30, 2017 · 1 comment
Open
Labels
Milestone

Comments

@mitchhentges
Copy link
Member

To reproduce:

  1. Install the .dmg for 2.0.0-beta.1
  2. Start James
  3. Wait until "restart to update" text appears with green cloud
  4. Click the "restart to update" text
  5. James will restart
  6. Upon loading, James will show "unable to update". Hovering over the error will show the message "Could not get code signature for running application".
  • Restarting James again (command-Q, start James) makes the error go away, and the v2.0.0-beta.2 version is showed as expected

Note:
If, for step 4, you command-Q and restart James, James will behave properly. It's just when you click the "restart to update" text that it fails.

Acceptance criteria

  • Clicking "restart to update" doesn't cause errors on OSX
@mitchhentges mitchhentges added this to the 2.0 Baby milestone Dec 30, 2017
@tomitm tomitm mentioned this issue Dec 30, 2017
6 tasks
@tomitm tomitm changed the title [osx] After update: "Could not get code signature for running application" After update: "Could not get code signature for running application" Dec 30, 2017
@tomitm
Copy link
Contributor

tomitm commented Jan 4, 2018

I thought this error was a bit familiar... Turns out this is the same error that happened last time. 🤔

@mitchhentges mitchhentges modified the milestones: 2.0 Baby, 2.1 Jan 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants