Closed BobWs closed 4 years ago
@BobWs can you run the app from console with added ELECTRON_ENABLE_LOGGING=true
environment variable and then see if there is something useful posted to console?
Then I downloaded version (4.0.0) installed it and this version is working.
There are few possibly major macOS differences come with 4.2.0 in comparison with 4.0.0:
So these would be a points need to digged into first of all.
According to https://api.github.com/repositories/115260146/releases at the moment v4.2.0 macOS packaged got downloaded 107 times. So I wonder is there someone who runs macOS and gets v4.2.0 working well.
e2e tests got passed on CI so I guess the problem happens only with packed version. On CI by design e2e tests get executed before the app got packed.
4.2.0 macOS package prepared on https://www.appveyor.com
According to https://www.appveyor.com/docs/macos-images-software/ the macos
image is based on macOS 10.15 "Catalina" and XCode 11.2.1 (the app goes with macos image).
but previously was used https://travis-ci.org.
Here/v4.0.0 macOS High Sierra 10.13.6 and XCode 9.4.1 was used.
This looks like a huge difference in general which though I'm not sure is supposed to affect the package preparing process.
@BobWs
This looks like a huge difference in general which though I'm not sure is supposed to affect the package preparing process.
What I could do for now is preparing the 4.2.0 package on Travis CI like it was happening before and then we see if it helps.
By the way, can someone, like @joshirio / @Imparium / @andrewkdinh / @BBaoVanC / @bit-for-byte / @ylluminate respond with v4.2.0 running status on macOS if you tried this release already (please include the used macOS version in response)? Does it crash?
@BobWs can you run the app from console with added
ELECTRON_ENABLE_LOGGING=true
environment variable and then see if there is something useful posted to console?
Sorry, but I'm not quite sure what you mean and how I'm suppose to do that?
I have found this in the console logs from yesterday when I tried to install version 4.2.0:
Process: ElectronMail [877]
Path: /Applications/ElectronMail.app/Contents/MacOS/ElectronMail
Identifier: github.comvladimiryElectronMail
Version: 4.2.0 (4.2.0.298)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: ElectronMail [877]
User ID: 501
Date/Time: 2020-01-27 10:36:54.436 +0100
OS Version: Mac OS X 10.13.6 (17G65)
Report Version: 12
Anonymous UUID: AA502188-D46F-8C6D-5AA3-908CA9F96746
Time Awake Since Boot: 4600 seconds
System Integrity Protection: enabled
Crashed Thread: 22
Exception Type: EXC_CRASH (SIGKILL)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Reason: DYLD, [0x4] Symbol missing
Dyld Error Message:
Symbol not found: ____chkstk_darwin
Referenced from:
/Applications/ElectronMail.app/Contents/Resources/app.asar.unpacked/node_modules/sodium-native/build/Release/libsodium.dylib (which was built for Mac OS X 10.15) Expected in: /usr/lib/libSystem.B.dylib
@BobWs, thanks, this is helpful.
Dyld Error Message: Symbol not found: ____chkstk_darwin Referenced from: /Applications/ElectronMail.app/Contents/Resources/app.asar.unpacked/node_modules/sodium-native/build/Release/libsodium.dylib (which was built for Mac OS X 10.15) Expected in: /usr/lib/libSystem.B.dylib
libsodium
is a native library the app uses for encryption needs. For v4.2.0 release it was compiled from the sources on macOS 10.15 Catalina and XCode 11.2.1
environment but apparently should be compiled on the macOS version you run the app. So I'm going to prepare DMG packages assembled on different macOS versions and then will ask you to try all of them.
By the way, can someone, like @joshirio respond with v4.2.0 running status on macOS if you tried this release already (please include the used macOS version in response)? Does it crash?
yes I can confirm same crash on macOS high sierra
Ok, then v4.2.0 presumably starts without crash only on Catalina and possibly on Mojave (not confirmed yet).
ElectronMail 4.2.0 works fine for me
macOS Catalina 10.15.2
@BobWs, can you try running the electron-mail-4.2.1-mac-high-sierra.dmg
package uploaded here? Anyone else is also welcomed to try the updated macOS packages. If it works well I then will be preparing the v4.2.1 release.
@BobWs, can you try running the
electron-mail-4.2.1-mac-high-sierra.dmg
package uploaded here? Anyone else is also welcomed to try the updated macOS packages. If it works well I then will be preparing the v4.2.1 release.
Thanks for the quick response and update I will give it a try and get back to you.
Just another question, did you drop the Tutanota support in the app? Because I couldn’t find the ability to add an Tutanota account. I only have the ability to add ProtonMail.
Just another question, did you drop the Tutanota support in the app?
Tutanota support was deprecated since July 2019. The visual/in-the-app deprecation message added in Sep 2019 with v3.8.0. Support for it got completely dropped in v4.0.0.
I can confirm that the update (electron-mail-4.2.1-mac-high-sierra) is working properly no crashes. Thanks!
Great, new release is on the way then.
Just another question, did you drop the Tutanota support in the app?
Tutanota support was deprecated since July 2019. The visual/in-the-app deprecation message added in Sep 2019 with v3.8.0. Support for it got completely dropped in v4.0.0.
Okay, Sorry I overlooked the changelog ;-)
Hi, So I start testing your great developed desktop app for ProtonMail and it is looking greast so far. But unfortunately updating to version 4.2.0 is not working, it keeps crashing on startup.
First time I installed the latest version (4.2.0) but it was crashing immediately. Then I downloaded version (4.0.0) installed it and this version is working. Then I tried to update to version (4.2.0) and it keeps crashing.
I'm on OSX 10.13.6 (High Sierra)
Any thoughts how to solve this problem?