Skip to content
This repository has been archived by the owner on Nov 1, 2022. It is now read-only.

Support PushService start/stop #2603

Closed
jonalmeida opened this issue Apr 2, 2019 · 0 comments
Closed

Support PushService start/stop #2603

jonalmeida opened this issue Apr 2, 2019 · 0 comments
Labels
<push> Components: concept-push, lib-push-adm, lib-push-firebase, feature-push, feature-sendtab

Comments

@jonalmeida
Copy link
Contributor

jonalmeida commented Apr 2, 2019 •
edited by data-sync-user
Loading

Currently our Firebase implementation is started from a service automatically so we don't have direct ownership of the PushService itself. This makes it difficult to add actions to the service that can be controlled from the PushProcessor.

┆Issue is synchronized with this Jira Task
@jonalmeida jonalmeida added the <push> Components: concept-push, lib-push-adm, lib-push-firebase, feature-push, feature-sendtab label Apr 2, 2019
@jonalmeida jonalmeida mentioned this issue Apr 8, 2019
Closed
3 tasks
@data-sync-user data-sync-user changed the title Support PushService start/stop FNX2-16376 ⁃ Support PushService start/stop Jul 31, 2020
@data-sync-user data-sync-user changed the title FNX2-16376 ⁃ Support PushService start/stop FNX3-22257 ⁃ Support PushService start/stop Jul 31, 2020
@st3fan st3fan changed the title FNX3-22257 ⁃ Support PushService start/stop Support PushService start/stop Aug 5, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
<push> Components: concept-push, lib-push-adm, lib-push-firebase, feature-push, feature-sendtab
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jonalmeida @data-sync-user