-
Notifications
You must be signed in to change notification settings - Fork 824
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Amplify notifications error on specific environment #14056
Comments
Hey, thank you for reaching out. The issue does appear to be similar to #13653.
|
yes i can see 'notifications' block inside 'amplify-meta.json` "notifications": {
"myXXXapp": {
"channels": [
"APNS",
"FCM"
],
"service": "Pinpoint"
}
} |
@charith-eLovu Glad to hear that it mitigated your issue. |
This issue is now closed. Comments on closed issues are hard for our team to see. |
How did you install the Amplify CLI?
No response
If applicable, what version of Node.js are you using?
No response
Amplify CLI Version
12.14.0
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
Describe the bug
Since yesterday we notice some problem with notifications on our amplify project .
When i try to switch to this environment from other env i get
Cannot read properties of undefined (reading 'Id')
amplify update notifications
throws the same error.Other environments seems fine, this env is configure for
us-west-1
which does not have pinpoint available, amplify did setup it inus-west-2
was working all fine for over a year now .i see this output when i do
amplify env checkout staging --debug
Expected behavior
Should work without any issues on this env like other env's
Reproduction steps
Not sure on how to reproduce the error, but i can say we did not make any changes to config recently .
Project Identifier
471b11adc8ed24241581a56cb8dcfb7a
Log output
Additional information
No response
Before submitting, please confirm:
The text was updated successfully, but these errors were encountered: