Make it possible to consume pending notifications when opening the app manually
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- android, firebase, javascript
- Domain
- mobile
Research direction
No files, tests, or entry points are named. Start by tracing how the plugin handles notification opens and how pending notifications are represented when the app is opened manually; done means an optional mechanism can read those pending notifications and remove them from the system UI.
Written by the indexing model from the issue text.
Description
Problem description
When notifications get received while the app has been in the background or killed and it gets opened not through tapping on one of those notifications (e.g. clicking on the app icon or selecting it in the multitasking screen), there is currently no way to consume these notifications. They can only be consumed when the app gets opened through tapping on a notification.
Expected behavior
A mechanism should be provided which enables optionally reading the data of those pending notifications and removing them from the system UI when the app gets opened.
- Dominant language
- JavaScript
- Stars
- 6
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from eclipsesource/tabris-plugin-firebase
-
broken linkOpen
Difficulty 1/5 Under an hour Newbie friendliness 65/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
eclipsesource/tabris-plugin-firebase#76 · 2 comments ·
-
bug ios
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
eclipsesource/tabris-plugin-firebase#65 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
eclipsesource/tabris-plugin-firebase#64 · 1 comment ·
All issues in eclipsesource/tabris-plugin-firebase
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
documentation good first issue help wanted
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
zmo2s/agent-toolbox#23 ·
-
[Bug]: [MCP/CLI] Bare loopback IP addresses (127.0.0.1:port) and hosts with ports fail to navigate due to erroneous scheme inferencePossibly taken @alok-108 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
microsoft/playwright#43263 ·
Maintainers usually reply within 1 day