You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
we are using this plugin to show media controls notification, but we are seeing some issues in destroying the notification in Samsung OS (model: Samsung Galaxy S21 plus).
Even after calling MusicControls.destroy(onSuccess, onError);, we are getting success callback, But still the notification can be seen on Lock screen
We get notification like this on lock screen after MusicControls.create({...}) call
However when we call MusicControls.destroy(onSuccess, onError);, we see a different kind of notification (the config object in create does have these properties set)
it looks like OS itself is creating default notification after destroy() call? (just a guess).
Any workaround for this would be appreciated, Thanks!
The text was updated successfully, but these errors were encountered:
We are also facing similar issue where the Music Controls are shown even after the app is force closed.
Sometimes, the controls go away when app is closed, but reappear after few seconds...
"it looks like OS itself is creating default notification after destroy() call? (just a guess)." -- seems to be the case for me also.
Were you able to find a solution or workaround for this?
Hi,
we are using this plugin to show media controls notification, but we are seeing some issues in destroying the notification in Samsung OS (model: Samsung Galaxy S21 plus).
Even after calling
MusicControls.destroy(onSuccess, onError);
, we are getting success callback, But still the notification can be seen on Lock screenWe see similar issues reported here - https://us.community.samsung.com/t5/Note20/Can-t-remove-media-controls-from-lock-screen-after-One-UI-3-0/td-p/1628685
Exact same call works in other android devices.
We get notification like this on lock screen after
MusicControls.create({...})
callHowever when we call
MusicControls.destroy(onSuccess, onError);
, we see a different kind of notification (the config object in create does have these properties set)it looks like OS itself is creating default notification after destroy() call? (just a guess).
Any workaround for this would be appreciated, Thanks!
The text was updated successfully, but these errors were encountered: