Skip to content

Kill on destroy#25

Open
mattveraldi wants to merge 3 commits into
voximplant:masterfrom
mattveraldi:kill-on-destroy
Open

Kill on destroy#25
mattveraldi wants to merge 3 commits into
voximplant:masterfrom
mattveraldi:kill-on-destroy

Conversation

@mattveraldi

Copy link
Copy Markdown

Hi,
I needed to add this behaviour to my react-native app, so I implemented this notificationConfig.
Feel free to merge it if you think it's useful.
Best regards.

@hazelf42

hazelf42 commented Feb 2, 2021

Copy link
Copy Markdown

+1 would like this added

@esinanturan

esinanturan commented Feb 16, 2021

Copy link
Copy Markdown

@mattveraldi It's killing the notification but when I checked the app status on the app info it seems app still working in the background and the option 'force stop' is available. And I checked it starting the service causing this without foreground service when I kill the app there is no 'force stop' option available. I think it's not exactly killing the service.
I had to add

android.os.Process.killProcess(android.os.Process.myPid());
System.exit(0);

to the onHostDestroy method of the module

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

Successfully merging this pull request may close these issues.

3 participants