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

Notification is not destroyed in Samsung Galaxy S21 plus lock screen #72

Open
shantanupks opened this issue Sep 30, 2021 · 2 comments
Open

Comments

@shantanupks
Copy link

shantanupks commented Sep 30, 2021

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 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({...}) call

Success Create

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)

OS Create

it looks like OS itself is creating default notification after destroy() call? (just a guess).

Any workaround for this would be appreciated, Thanks!

@srividya-sharma
Copy link

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?

@shantanupks
Copy link
Author

Yeah, OS itself is creating it. We are referring already open PR for this - #61
We were not able to find any permenant solution though!

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

No branches or pull requests

2 participants