Unable to pull backend #2280
Labels
Comments
|
Hey @muratcali, thank you for reaching out. From the logs provided the error message stands out: |
|
Hi @ykethan, Thanks for your message. Ive deleted the whole amplify folder to do a clean pull so there is right now no amplify folder available in my project. So its not possible for me to da a push right now. If I download and open the Ive noticed that there are a lot of duplicate files. 
|
|
Hey @muratcali, is the project in a google/icloud drive folder? as the issue appears to be similar to aws-amplify/amplify-cli#13335, to mitigate this you can download the |
|
Hi @ykethan , Thanks for your message. Ive tried the option you mentioned and now im getting the following error: As mentioned in the error before it returns: But this file exists inside the S3 bucket see image: Also ive mentioned alot of other directories inside this S3 bucket which i never saw before. Here is a picture from the bucket. Are these required files? Or is something wrong here? |
|
Hey @muratcali, just to ensure this isnt the case. Could you download the The files at the root of the S3 bucket are expected as they get utilized by services such as Amplify Studio. |
|
@ykethan Ah that makes sense. That problem is fixed but im still getting the See image: |
|
Hey @muratcali, interesting. could you try zipping the |
|
Hi @ykethan, Thanks for your help. It solved the pull problem but now im not able to push. After doing the solution you provided and pulling the backend it worked as usual but after running After this problem, everytime i run |
|
Hey @muratcali 👋 if you check the CloudFormation console for this stack, do you see the previous deployment failure and reason (under the "Events" tab)? Does it show a reason for the rollback failure? |
|
@josefaidt Thanks for your message. I see the following errors: 
|
|
Hey @muratcali , apologies on the delay in a response. Transferring the issue to our API repository for additional assistance as the error appears to be an error on the GraphQL API resource. |
|
Hi @muratcali, thanks for attaching the CFN log screenshot. I you see the bottom most |
dpilch
added
theme:dynamodb-iterative-deployments
bug
|
This issue is now closed. Comments on closed issues are hard for our team to see. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
v20.10.0
Amplify CLI Version
12.10.1
What operating system are you using?
MacOS 14.2.1
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
We are not able to pull the amplify backend. When we run the pull command with or without app ID it failes with error:
Failed to pull the backendwithout any further information. This happens on all of the laptops of our developers. Even when we try to build the project in amplify it failes with the same error. So we are also not able to build and publish something on Amplify. Ive added the error log when we run theamplify pull --appId *** --envName *** --debugcommand.Deleting the Amplify folder doesnt solve the problem and when we run amplify init (with or without AppID) it doesnt recognise the backend. Also running
amplify pull --appId *** --envName *** --debugin an empty folder doesnt work. Pulling new created environments works but pulling the existing one is not possible.Looks like there is somewhere a bug which prevents us and AWS Amplify systems for pulling the backend from this environment.
Here a picture from the failed build:
Expected behavior
I expect the backend to be pulled from AWS Amplify.
Reproduction steps
amplify pull --appId *** --envName *** --debugFailed to pull the backendon all devices + AWS Amplify buildProject Identifier
No response
Log output
Additional information
No response
Before submitting, please confirm:
The text was updated successfully, but these errors were encountered: