update channel error Resource not found NotFoundException: Resource not found when amplify add notifications

[marcojr]

Note: If your issue/bug is regarding the AWS Amplify Console service, please log it in the
Amplify Console GitHub Issue Tracker

Describe the bug
Error message: update channel error
Resource not found

Amplify CLI Version
4.27.0

To Reproduce

• execute amplify add notifications
• Choose APNS or APNS Sandbox
• This will generate with no issues
• Now, execute the same step, but choose FCM
• You will be prompted with ApiKey
• Copy the key from Firebase Console / Project Overview / Gearbox Icon / Project Settings Menu Options / Cloud Messaging Tab / Project Credentials / Server Key (exactly like the official doc asks)

Expected behavior
Settings to be stored at /amplify/*

Screenshots

Desktop (please complete the following information):

• OS: MAC
• Node Version. v12.18.2

[jcbdev]

I have this exact same issue

[jcbdev]

@SwaySway I have lost a week to issues with notification and analytics since trying to add it to an existing project. It is totally broken at the moment (see my other issue too - #5063). I have managed to hack around it by destroying and recreating environments and copying backend folders from existing pulls but there is something fundamentally broken after analytics is added to a project.

I really cannot see how I would get this into production at the moment.

[attilah]

@marcojr @jcbdev I tried to reproduce this issue with 4.27.2 (the latest version as of now) and I was not able to do it. Both notifications were successfully added. Try with the latest version and get back to me with the results.

Based on the stacktrace that error happens when Amplify CLI tries to retrieve a given pinpoint resource but cannot succeed. Are you using admin credentials or a scoped down user when executing the CLI commands?

[jcbdev]

@attilah I think I was able to fix it my end and it's potentially due to the other bug I am having with notifications/analytics.

I had added analytics but it failed for a different reason (see other issue) so I removed analytics by switching envs (created a "devb", switched, destroyed "dev", recreated "dev", switched back, removed "devb"). This was the only way I could get back to a deployable version. The other issue is this - #5063

Anyway, I noticed yesterday that after re-adding analytics when I got around my other issue that when it gets added the "appId" for pinpoint does not change from the previous values (the original attempt to add them) in the following files: parameters.json and nested-cloudformation-stack.yml

If I update these files with the correct new appId from the new stack it works. There seems to be a bug where if the values already exist it does not update them.

[ahtokca]

Got the same issue. Stuck not able to switch between envs

so now amplify status gives me Current Environment: dev
but aws-exports point to tst resources
and every time I do amplify env checkout dev
it asks me for ApiKey for FCM and creates a tst pinpoint app and then fails with 'Resource Not Found'

For some reason amplify drop my dev pipoint project. After creating the project manually and changing its id in team-provider-info.json i managed to checkout environment

[github-actions]

This issue has been automatically locked since there hasn't been any recent activity after it was closed. Please open a new issue for related bugs.

Looking for a help forum? We recommend joining the Amplify Community Discord server *-help channels for those types of questions.