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

Stretchly app crashed. Unable to reinstall #155

Closed
jt007 opened this issue Dec 3, 2017 · 5 comments · Fixed by #190
Closed

Stretchly app crashed. Unable to reinstall #155

jt007 opened this issue Dec 3, 2017 · 5 comments · Fixed by #190

Comments

@jt007
Copy link

jt007 commented Dec 3, 2017

I guess the app crashed because I chose to disable both the break features. I needed to do this temporarily. Then the app crashed, and I had to uninstall the whole app from the Windows 10 settings. When I try to reinstall it, I get this feedback. Please see enclosed printscreen file.

Stretchly printscreen.docx

(windows 10, Stretchly 12.0)

@jt007
Copy link
Author

jt007 commented Dec 3, 2017

Just in case you can't open the filetype, this is the text in the error message:

[Window Title]
Error
[Main Instruction]
A JavaScript error occurred in the main process
[Content]
Uncaught Exception:
TypeError: Cannot read property 'plan' of null
at BreaksPlanner.nextBreak (C:\Users\jontore\AppData\Local\Programs\stretchly\resources\app.asar\breaksPlanner.js:78:19)
at App.loadSettings (C:\Users\jontore\AppData\Local\Programs\stretchly\resources\app.asar\main.js:247:16)
at emitTwo (events.js:111:20)
at App.emit (events.js:194:7)
[OK]

@hovancik
Copy link
Owner

hovancik commented Dec 4, 2017

Hi, you can disable breaks for infinite time from tray menu, no need to disable both type of breaks.

The quick fix for you would need to find config.json and make

  microbreak: true,
  break: true,

Don't have any win 10, but should be in %APPDATA% (https://github.com/electron/electron/blob/master/docs/api/app.md#appgetpathname)

@sxmanton
Copy link
Contributor

sxmanton commented Dec 5, 2017

While the disable breaks is definitely the right way to accomplish the intended behavior, it would probably still be a good idea to add some null checks to safeguard against it crashing, possibly pulling in default values or something.

@hovancik
Copy link
Owner

hovancik commented Dec 6, 2017

Yeah, I'm planning to fix this, but I'm still working on translations right now.

I guess the fix will be not allowing to disable both types of breaks.

@jt007
Copy link
Author

jt007 commented Dec 9, 2017

Thanks, problem solved :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants