Introduce an iOS-only method for verifying the push notification permissions
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- firebase, ios, javascript
- Domain
- mobile-dev
Research direction
The issue names no repository files or tests. Start by locating the iOS implementation of the Firebase notification plugin and compare its permission APIs with the referenced diagnostic methods. Done means exposing checks for remote-notification registration and notification-banner status, with coverage for both results.
Written by the indexing model from the issue text.
Description
Problem description
There is no way to check if the push notification permissions have been enabled. It is a common use case to check if the user really did grant the permission or not in order to display a corresponding message to him and would be required for apps, which primary rely on push notifications to function properly.
(Currently, this could be done using a plugin like cordova-plugin-diagnostics, however it declares generic description for various iOS permissions, which might not be desired for production apps.)
Expected behavior
-
Support a method to check if the notifications permission has been enabled, similarly to https://github.com/dpa99c/cordova-diagnostic-plugin#isregisteredforremotenotifications
-
Support a method to check if notification banners have been enabled, similarly to https://github.com/dpa99c/cordova-diagnostic-plugin#isremotenotificationsenabled.
- 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 76/100
Maintainers usually reply within 1 day
-
[BUG] npm pkg delete removes the first array item for a nonexistent propertyPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 2 days
-
feedback simulation workshop
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
githubnext/gh-aw-workshop#4755 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
videojs/video.js#9537 · 1 comment ·
Maintainers usually reply within 1 day
-
fix
Difficulty 1/5 Under an hour Newbie friendliness 72/100
idean3885/claude-ops-agent#728 ·
Maintainers usually reply within 1 day