Open chriscrutch opened 1 month ago
I'm not familiar with the Buzkill app, so I can't tell you what's going on underneath.
I can tell you, however, that if the application notification is simply swiped from the foreground notifications (hiding the notification, not killing it), the app continues to work (the notification is still present in the notifications curtain with the second swipe).
On the contrary, if the process is killed to completely eliminate the application then I think it is normal for Tempo to stop working.
Sorry, I reread what you wrote: you continue to use the application but even when you click on a track it doesn't play.
The app is made up of two components, the actual app and a service that acts in the background (with foreground notification) that manages the player. Buzzkill appears to act on the notification, killing the service.
I have to investigate further.
Describe the bug
I use an app called Buzzkill in order to automatically dismiss notifications. When it's active, Tempo will not play. If I deny Tempo access to notifications it works fine, but if Buzzkill is actively dismissing notifications Tempo will not play, whether it has access to notifications or not.
Expected behavior
Since notification access isn't a requirement to play music in the app, dismissing notifications using a third-party app should not affect the ability of Tempo to play music.
To Reproduce
Install and set up Tempo with a working server Install Buzzkill and set up any condition that will immediately dismiss notifications from Tempo. Try to play a track in Tempo and see it not work. Turn off Buzzkill's dismissing of notifications and see Tempo be able to play again.
Environment