Open IsaacHarrison28 opened 5 months ago
Hi @IsaacHarrison28, Thanks for raising this. This issue seems to be duplicate of #636. Can you please try the steps mentioned here: https://github.com/aws-amplify/amplify-category-api/issues/636#issuecomment-1288164584 and let us know if it resolves your issue?
How did you install the Amplify CLI?
npm install -g @aws-amplify/cli
If applicable, what version of Node.js are you using?
v20.12.1
Amplify CLI Version
12.12.3
What operating system are you using?
Windows
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
I did not make any changes to the cloud resources in any way at the moment. However, when trying to debug, I tried creating a new API_key in the App_Sync console but because it still did not work, I deleted the key and the cloud resources are currently unchanged.
Describe the bug
My exports file contains an API_key which is not being shown in the App_sync console (The console has no API_key at all !). I tried most solutions provided from previous issues opened but none worked hence opening a new one. When I create a new API_key and try to push the changes, I receive an error that api_key not found and the key being referenced is the one that does not exist in my App_sync console but only shows in my exports file. Running "amplify update api" closes without creating a new key as well !
Expected behavior
I am expecting to find a way in which I can create a new API_key that can then remove my 401 error when accessing backend data from amplify
Reproduction steps
Project Identifier
Project Identifier: 1d7a661e2d7173d4f67a35b3860f5214
Log output
Additional information
No response
Before submitting, please confirm: