Unhandled Promise Rejection Warning
Opened this issue · 0 comments
TBK commented
I am getting the following warning as a popup every time jellyamp finishes playing a song a starts playing a new one.
Running v1.1.1 x86_64 appimage in a pipewire-pulse & Wayland environment.
(node:14459) UnhandledPromiseRejectionWarning: TypeError: r(...).connect is not a function
at /tmp/.mount_jellya1ueTOj/resources/app.asar/background.js:2:573127
at t.exports (/tmp/.mount_jellya1ueTOj/resources/app.asar/background.js:2:573590)
at c (/tmp/.mount_jellya1ueTOj/resources/app.asar/background.js:2:45749)
at Object.t.exports.sessionBus (/tmp/.mount_jellya1ueTOj/resources/app.asar/background.js:2:45951)
at f.init (/tmp/.mount_jellya1ueTOj/resources/app.asar/background.js:2:505417)
at new f (/tmp/.mount_jellya1ueTOj/resources/app.asar/background.js:2:505236)
at f (/tmp/.mount_jellya1ueTOj/resources/app.asar/background.js:2:505104)
at O (/tmp/.mount_jellya1ueTOj/resources/app.asar/background.js:2:652054)
at IpcMainImpl.<anonymous> (/tmp/.mount_jellya1ueTOj/resources/app.asar/background.js:2:652575)
at IpcMainImpl.emit (events.js:223:5)
(node:14459) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:14459) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.