Hi there,
Since this morning Nylas won't open and keeps trying to open. All I can see is the launching screen with the message "Please wait while we prepare new features", then it crashes.
Before last update (0.4.25) everything was going well. I tried rebooting, running with debug flags but nothing worked...
Is anyone else having the same issue?
Here's the screen I have for a short time : https://cldup.com/rq63MpZkgL.png
In fact, how can I reinstall N1 without losing my mail rules and preferences?
+1
Even i am facing the same issue. It keeps crashing and restarting continuously.
+1 Same problem here
What platform are you running N1 on? This issue appeared before on Linux because of a dependency issue, but it can also occur from database inconsistency.
Having this problem on Arch Linux. Installed using this https://aur.archlinux.org/packages/n1/. I have 2 email accounts enabled but the problem only occurs in 1, and only sometimes.
@ryanpineo What version of freetype2 is installed? You are using 0.4.25 correct, which contains a newer Electron version that fixes the freetype2 2.6.3 issue.
n1 version 0.4.25-1 and freetype2 version 2.6.3-1
@ryanpineo Could you run /usr/bin/nylas -f give the output in a gist?
I'm on OS X El Capitan (10.11.4).
I tried that but I only got 3 lines. I'm assuming you were expecting more? https://gist.github.com/ryanpineo/26c111fcf97340e4196243c234e13d8d
@ryanpineo Yes more output. Not the output from the /tmp files, but from /usr/bin/nylas -f.
Should be something like:
[9257:0425/112607:INFO:CONSOLE(379)] "%c %cSCAN TABLE%c Category for %cSELECT%c %c`Category`%c.%c`data`%c %cFROM%c %c`Category`%c ", source: /usr/share/nylas/resources/app.asar/src/flux/stores/database-store.js (379)
[9257:0425/112607:INFO:CONSOLE(38)] "Backing off after sync failure. Will retry in 3 seconds.", source: /usr/share/nylas/resources/app.asar/internal_packages/worker-sync/lib/nylas-sync-worker.js (38)
[9257:0425/112609:INFO:CONSOLE(18)] "Window load time: 4482ms", source: file:///usr/share/nylas/resources/app.asar/static/index.js (18)
[9257:0425/112609:INFO:CONSOLE(379)] "%c %cSCAN TABLE%c Category for %cSELECT%c %c`Category`%c.%c`data`%c %cFROM%c %c`Category`%c ", source: /usr/share/nylas/resources/app.asar/src/flux/stores/database-store.js (379)
Not seeing anything like that when I run that command. Only thing I see is this:
Streaming log data to /tmp/Nylas-N1-19116.log
App load time: 720ms
WindowManager: Preparing a new 'composer' window
WindowManager: Preparing a new 'composer' window
Same issue - OSX 10.11.4
Hey. Thank you everyone for the reports and debug info. We're actively looking into this now.
hmm that's weird that you aren't seeing any other logs @ryanpineo. @Federfleisch or anyone else on mac, could you open a Terminal window and run the following command:
/Applications/Nylas\ N1.app/Contents/MacOS/Nylas --enable-logging
That should run Nylas N1 and you should see a bunch of logs in the Terminal window. Could you send those logs in a gist as @mbilker mentioned earlier?
thanks!
@jstejada @mbilker I ran the above command and got logs. Please find them attached. Exception at every point it crashes.
nylas-crash.txt
I am on El Capitan BTW.
@jstejada Here you go https://gist.github.com/Federfleisch/519e5035400495ee620293a9cef2230a
thanks @mohitkhanna, @Federfleisch , will look into this
@Federfleisch N1 is reporting disk I/O errors. Is anything up with your hard drive? Seems strange that N1 reported that error on your computer, but @mohitkhanna 's log does not report it.
@jstejada Do you know why people keep seeing navigator is not defined errors?
EDIT: See next comment.
I just realized that the ErrorReporter is being run from the main process and not the renderer, causing the error.
@mbilker Just ran an Onyx test and a "S.O.S" test from Disk Utility, hard drive seems to be okay... Also repaired permissions, erased the app with AppCleaner, reinstalled it but the problem remains.
It's weird but I tried downgrading to N1 0.4.19 and it works fine.
@Federfleisch If you do not care about mail rules, nuke ~/.nylas/edgehill.db*. There may have been an upgrade inconsistency between 0.4.19 and 0.4.25.
@Federfleisch this is unrelated to this issue,but the package N1-Filters seems to be causing an error because it can't find the Less variable @border-color. This definitely should not be causing N1 to restart continuously, but the N1-Filters package probably needs to be updated. What is the repo for that package?
EDIT: Updated comment above and removed disk I/O comment
@Federfleisch scratch my previous disk I/O comment. I just looked at the logs more closely and it is the same issue @mohitkhanna is having, related to an invalid delta streaming cursor.
It seems N1 is continuously falling back to reading an invalid cursor from your ~/.nylas/config.cson file causing the app to continuously clear the local database and restart. As a temporary fix, you can remove any cursor fields you have inside your config.cson and this should fix the issue. The cursor field should be located here in the file:
...
nylas:
<accountId>:
cursor: "..."
...
We will push a fix to this issue in the next release so it doesn't happen again. @Federfleisch, @mohitkhanna , let me know if this works for you.
@jstejada No problem. I have rolled back Nylas version so not blocked for now. Can't upgrade till the issue gets resolved.
Meanwhile I will try the temp fix you gave and report back.
@jstejada The workaround worked. Nylas working when I removed the cursor config. Thanks!
@jstejada Great, works fine too. Thank you!
good to know, we are addressing it in https://github.com/nylas/N1/commit/04cebd51f26540ae435643eac5e4cff51fbc28bf
Most helpful comment
@Federfleisch scratch my previous disk I/O comment. I just looked at the logs more closely and it is the same issue @mohitkhanna is having, related to an invalid delta streaming cursor.
It seems N1 is continuously falling back to reading an invalid cursor from your
~/.nylas/config.csonfile causing the app to continuously clear the local database and restart. As a temporary fix, you can remove any cursor fields you have inside yourconfig.csonand this should fix the issue. The cursor field should be located here in the file:We will push a fix to this issue in the next release so it doesn't happen again. @Federfleisch, @mohitkhanna , let me know if this works for you.