App aborted with error: "Error launching engine: The application “Habitica Chrome.app” could not be launched because it is corrupt. The app may not have launched properly. If it did, the engine will not be properly cleaned up upon quitting." [main(665)]

Question

App aborted with error: "Error launching engine: The application “Habitica Chrome.app” could not be launched because it is corrupt. The app may not have launched properly. If it did, the engine will not be properly cleaned up upon quitting." [main(665)]

icotext opened this issue 3 years ago · 8 comments

*[33664]HabiticaC540(545)/launchapp(2883): Error launching engine: The application ‚ÄúHabitica Chrome.app‚Äù could not be launched because it is corrupt.
![33664]HabiticaC540(665)/abortreport(1155)/abort(1093): Aborting: Error launching engine: The application ‚ÄúHabitica Chrome.app‚Äù could not be launched because it is corrupt. The app may not have launched properly. If it did, the engine will not be properly cleaned up upon quitting.

Answer 1 · 2021-03-27T00:54:56.000Z

Hi @icotext, has this been happening with many of your apps, or was a a fluke that just happened once with one app? Thanks!

Answer 2 · 2021-03-27T02:13:37.000Z

Once with one app as of now. Usually after upgrading it gracefully exits and says it cannot relaunch the app and I launch again and all is fine, but this time was an abort so that was not graceful. Thanks, Dierk +1 (650) 353-2674

…

On Mar 26, 2021, 5:55 PM -0700, dmarmor ***@***.***>, wrote: Hi @icotext, has this been happening with many of your apps, or was a a fluke that just happened once with one app? Thanks! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

Answer 3 · 2021-03-28T01:10:09.000Z

Hmm, so on updating an app to 2.4.x, it generally doesn't launch correctly the first time? If possible, I'd be interested to see a log of the update run you're describing. When an app updates, it should launch normally, and show an extra page with info about the update...

Answer 4 · 2021-03-28T04:56:20.000Z

If you tell me how to pull the log I will try. Thanks, Dierk +1 (650) 353-2674

…

On Mar 27, 2021, 6:10 PM -0700, dmarmor ***@***.***>, wrote: Hmm, so on updating an app to 2.4.x, it generally doesn't launch correctly the first time? If possible, I'd be interested to see a log of the update run you're describing. When an app updates, it should launch normally, and show an extra page with info about the update... — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

Answer 5 · 2021-04-02T17:58:30.000Z

The logs are found in ~/Library/Application Support/Epichrome/Apps/<AppID>/Logs. Ideally, what I'd love to see is if you could run an app that needs updating with debugging on, so I can get a full log of the update run. You'd do this from the terminal like this:

open <YourApp.app> --args --epichrome-debug

Thanks!

Answer 6 · 2021-04-30T16:55:09.000Z

I'm going to try some different strategies with the launch code to see if I can prevent this from happening. Do these errors occur frequently for you, or is it only rarely?

Answer 7 · 2021-04-30T17:24:46.000Z

Only after upgrade

…

On Apr 30, 2021, 9:55 AM -0700, dmarmor ***@***.***>, wrote: I'm going to try some different strategies with the launch code to see if I can prevent this from happening. Do these errors occur frequently for you, or is it only rarely? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

Answer 8 · 2021-05-01T19:40:55.000Z

Version 2.4.5 will be up shortly, and I've added a retry to the launch code, in the hope that if it hits this type of error it can just make a second attempt and launch successfully. If you continue to get launch errors after updating to 2.4.5, please let me know and I'll see if there are any other things I can try. Thanks!