search

zidoro / pomatez

Stay Focused. Take a Break.
https://zidoro.github.io/pomatez/
MIT License
3.88k stars 161 forks source link

Bug Report: 1.3.0 Javascript error #411

Closed DoctorDinosaur closed 8 months ago

DoctorDinosaur commented 9 months ago

Updated from 1.2.3

Now, upon launching, I get this popup:

image

DoctorDinosaur commented 9 months ago

I turned on and off the new "Open at Login" slider and the error went away. So I assume it's related.

roldanjr commented 9 months ago

Hi @CptDinosaur did you try to turn on the Open at Login and check if the error persists?

DoctorDinosaur commented 9 months ago

Turning on Open at Login doesn't bring the error back.

Though, turning it off didn't actually remove its startup entry image

rafa-fiedo commented 9 months ago

I had a similar situation,

reproduce steps:

after turning off the 'open at login' the app stills open so I manually deleted it from startup apps (windows 11)

Now everything working fine. ps. greeeat app!

davidbgonz commented 9 months ago

I have the same error on Arch Linux with Nodejs v18.17.0 (using nvm). There is no "Open on Login" option for the Linux version. When I first updated the application, the "Notification Types" section got reset with no default selected. When I selected one of the types it was okay, but only for that session. Today when I started up the app the same error popped up again.

sekwah41 commented 9 months ago

@davidbgonz on linux there should be an on start list, I know on manjaro with plasma its quite easy but not too sure about your specific setup.

davidbgonz commented 9 months ago

I’m running i3. I specify start on boot in the config in i3. I was just giving extra information that the error still appears despite there being an open in login option.

sekwah41 commented 9 months ago

This is an issue with an underlying library. I am going to create a safe wrapper to ensure the errors to not propagate.

https://github.com/ipfs/ipfs-desktop/issues/2336 this is the same issue

sekwah41 commented 9 months ago

Sorry for not releasing this, it should be in the next update.

sekwah41 commented 8 months ago

I believe this is fixed