Missing information for configuring app
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- android, firebase, javascript
- Domain
- documentation, mobile-dev
Research direction
Start with the linked Firebase messaging documentation and inspect the plugin's existing notification setup instructions. Clarify how an app obtains and uses its registration token, and update the Firebase Console delivery steps to match the current interface, including any needed screenshots. Done means a newcomer can configure the app and send a test notification without unanswered registration questions.
Written by the indexing model from the issue text.
Description
The documentation does not clearly explain how to "register" a tabris app on firebase server to enable the app to receive notifications:
Send to a single device
From Firebase console Notification section, click New Message.
Enter the text of your message in the Message Text field.
Set the target to Single Device.
Check the logs for the InstanceID token, copy and paste it into the Firebase console Token field.
If you cannot find the token in your logs, click on the LOG TOKEN button in the application and the token will be logged in logcat.
Click on the Send Message button.
If your application is in the foreground you should see the incoming message printed in the logs. If it is in the background, a system notification should be displayed. When the notification is tapped, the application should return to the quickstart application.
Is the app registered by "token"? Is there a single token for each tabris app or is there a single token for developer app? How to access/generate these tokens?
Or does it register by its url/name? (com.my.app.whatelse)
There is no (more) "send message" in firebase console, there is "new campaign" with many variants and options, some screenshots would help.
- Dominant language
- JavaScript
- Stars
- 6
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Getting set up
We have not checked this project's setup files yet. 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
-
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 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
eclipsesource/tabris-plugin-firebase#63 · 4 comments ·
All issues in eclipsesource/tabris-plugin-firebase
Similar issues
-
Add: Digi 4K LogoOpencheck:passed logos:add
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
component/administration domain/framework needs-triage Platform(Default) priority/low
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
semantic-release/gitlab#1032 ·
-
agent/guide documentation hive/hosted-available-lke648397-260827-5n31
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
agentic-workflows
Difficulty 1/5 Under an hour Newbie friendliness 85/100
githubnext/gh-aw-workshop#3933 ·
Maintainers usually reply within 2 days