numbersprotocol / numbersprotocol/capture-cam
Push Notification on Background and when App Killed
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 26
- Forks
- 7
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 10
Description
Currently, PushNotificationService can only work when app is in foreground due to the limitations of the Capacitor Plugin and Firebase. To overcome this problem, we have to change the execution flow.
- Receive a push notification
- Display a local notification
- The user click on the local notification
- Set dirty flag to the specific data persistence service according to the
datapayload - Open the app
See the docs from Firebase to know the different conditions when receiving the notification.
However, if the app is fully killed, there is no way to receive push notifications due to this open issue.
┆Issue is synchronized with this Asana task by Unito
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating PushNotificationService and reading the linked Capacitor and Firebase notification guidance, especially the different foreground, background, and killed-app conditions. Trace how the data payload maps to the relevant persistence service and define the local-notification click flow. Done means the supported background flow works and the fully killed-app limitation is explicitly handled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- firebase, typescript
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100