-
Notifications
You must be signed in to change notification settings - Fork 2
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
Unhandled promise rejection on startup #32
Comments
If you care about your configuration, you can modify the {
"preferences": [
...
{
"name": "configuration",
"value": ""
+ },
+ {
+ "name": "fontSize",
+ "value": "1rem"
+ }
],
...
} If you don't manage to do it, just sent me this file to my email ([email protected]) and I will do it for you. In case you don't really care about your configuration, go ahead and just delete the whole I'm sorry about this inconvenience, but this is an issue with the problematic user configuration storage used in Parsify Desktop. I'm thinking about using a different solution for that in the upcoming release, so that such problems won't occur in the future :) |
Thanks! I got it to work. Also I was trying out to see if Parsify will solve equations and the input side crashes when I write solve(-any equation here-). What's up with that? |
@ecciv Glad to hear that it works 😄 Parsify currently does not support equation solving (for example |
Hi mate @xxczaki i'm prouded user of Parsify.
Do you know how can i hanndle with this? As an workaround i'm did an downgrade to 1.2.2 version |
The configuration storage was completely refactored in version |
Not sure what's up but each time I open Parsify, I get an error like this, and the input side of the app is replaced by a white box saying "An unexpected error occurred.". Can't get it to run! On 1.4.1 now, this error is new to me.
Unhandled Promise Rejection
TypeError: Cannot read property 'value' of undefined
at IpcMainImpl. (C:/Users/Victor/AppData/Local/Programs/parsify-desktop/resources/app.asar/app/background.js:1:11092)
The text was updated successfully, but these errors were encountered: