-
Notifications
You must be signed in to change notification settings - Fork 61
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
Multiple instanses #37
Comments
Good catch, I haven't tested that scenario, I will see if we can potentially random generate an APP ID for the notification channel so that it is unique. The problem at the moment is that a fixed notification channel is used which is always the same. |
I have a fix for this in the development branch at the moment, have implemented a UUID for the channel ID to prevent cross over. |
Great news. Waiting for the release(npm) |
weirdly I have tried with randomised channel id and notification id but they still overlap. I think because both instances are registering broadcast receivers to catch media key events. I'll try a few more things and see if I can find a way to filter this. |
How about my second option in the first message? You can pass the application name from config.xml to the client side. And we can handle messages only for the necessary app. |
Android 10.
The case:
I build 2 apps with the library. I run one song in the first app and then another one in the second. So there are two notifications with the controls. When i click on any button(at least prev/next) both apps get the event message.
I see two solutions:
const application= JSON.parse(action).application;
The text was updated successfully, but these errors were encountered: