-
Notifications
You must be signed in to change notification settings - Fork 820
Closed
Labels
bugSomething isn't workingSomething isn't workinggood first issueGood for newcomersGood for newcomersnotificationsIssues tied to the notifications categoryIssues tied to the notifications categoryp2
Description
Before opening, please confirm:
- I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
- I have searched for duplicate or closed issues.
- I have read the guide for submitting bug reports.
- I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
- I have removed any sensitive information from my code snippets and submission.
How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
14.17.3
Amplify CLI Version
7.6.23
What operating system are you using?
Mac
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No manual changes made
Amplify Categories
notifications
Amplify Commands
add
Describe the bug
When adding push notifications via FCM channel - the CLI prompts for an ApiKey
. It is unclear what api key it is asking for. (It is asking for the Server key from FCM console)
$ amplify add notifications
? Choose the push notification channel to enable. FCM
An Amazon Pinpoint project will be created for notifications.
? Provide your pinpoint resource name: tempt0oGF
✔ Successfully created Pinpoint project: tempt0oGF-dev
✔ Successfully set the IAM policy
? ApiKey
Expected behavior
Expected a little more clarity/guidance on what this is asking for. At the least, the terminology should be updated to Server Key
to align with the FCM console.
Reproduction steps
- Add notifications
$ amplify add notifications
- Select FCM as the channel to enable
- See just a prompt for
ApiKey
with no indication what key this is asking for
GraphQL schema(s)
# Put schemas below this line
Log output
# Put your logs below this line
Additional information
No response
biller-aivy
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workinggood first issueGood for newcomersGood for newcomersnotificationsIssues tied to the notifications categoryIssues tied to the notifications categoryp2