Blocked error! Syntax Error: Expected ":", found "@" when executing amplify push and amplify pull, also admin.amplifyapp.com/admin/.. data-manager doesnt work #2718
Labels
Comments
|
Now I tried to:
I cant use Amplify Data Manager, white blank page with errors in console Help me please ASAP |
|
After many attempts to get into the Data manager, I was able to. It opened without tables, I created a single one for testing and clicked Deploy. An error was displayed during deployment |
|
amplify pull shows this error several times: |
|
|
|
Mistake is here: |
|
Hey,👋 thanks for raising this! I'm going to transfer this over to our API repository for better assistance. But to mitigate the issue you will need to download the |
|
Hey @chirpavel, Thanks for raising this. After reviewing your field that you are trying to the model seems to be not valid GraphQL format. Can you please update the field to like below and let us know if it resovles your issue. |
|
Thank you very much for your answers!!! Yes, I know there was a typo in the model. I deleted all the bad fields at the end and packed it back into the file. Without deleting the file, I uploaded it under the same name (I enabled versioning first, just in case)
After that, the Syntax Error: Expected ":", found "@" error disappeared! To make changes to the API, I added the "name" field and run amplify push: Sending report: After these actions, the page https://eu-central-1.admin.amplifyapp.com/admin/ХХХ/staging/datastore with the data model began to open I decided to delete the SubscriptionPlan model completely. I checked before Deploying that the model disappeared in the "GraphQL schema" mode. But the deployment quickly ended with an error:
If I try not to delete, but to add 1 string field "name" in the web console, the deployment ends with such an error: Attempts to delete the model locally and execute "amplify push" finished like this (without success): amplify pull finished without error: After the amplify pull command, I added one more "name" field to the SubscriptionPlan model and ran the amplify push command, it finished with error: PS C:\Users\chirp\Downloads\SplitPay\SplitPayReact\splitpay> amplify diagnose --send-report The problem appears after the inscription "file uploading" (or something like that). And at the same time I noticed that the version of the file #current-cloud-backend.zip in the deployment bucket does not change. Maybe after I updated the file - I became its owner and the system does not have enough rights to change mine to the new one? For additional information, amplify api gql-compile --allow-destructive-graphql-schema-updates works correctly: |
|
Before uploading the file, I decided to rename the file from #current-cloud-backend.zip to #current-cloud-backend-backup .zip at the moment indicated by the red arrow But the file did not appear in the bucket, an error was displayed At the same time, it is clear that some other files have changed their version many times |
|
This issue is now closed. Comments on closed issues are hard for our team to see. |
|
The task was closed by mistake when deleting a duplicate comment. The task is very relevant! |
|
Deployment activity in Amplify Studio: |
|
I tried to amplify push without #current-cloud-backend.zip (renamed to #current-cloud-backend-backup.zip): Then I renamed to #current-cloud-backend-backup.zip to the original name: #current-cloud-backend.zip and changed the Object Ownership rules (original is yellow) and added permissions for S3 log delivery group But when I run amplify push, the error after "Uploading files..." is the same: |
|
In the bucket there is deployment-state.json, it contains: amplify-appsync-files/1d69b42f50e3cfe5208ebbf987083edb0b3bf116/states/initial-stack/deployment-meta.json in bucket contains: |
|
Maybe new ideas? |
|
Hey @chirpavel, Could you try rolling back the changes you made to the #current-cloud-backend.zip folder, run |
Hi What do you mean roll back? And I didn't find how to roll back the version of #current-cloud-backend.zip in S3. You can only download the old version and upload it again as a new file. I didn't find a direct rollback to the previous version. In any case, rolling back a version with a broken scheme does not work. |
|
The internal support team says that they has identified the root cause of the issue with the CloudFormation stack and the failed update of the 'SyncSubscriptionPlanResolver' resource. The error message indicates that the resolver is not found, which is causing the update to fail. To resolve this issue, please follow these steps:
If the 'SyncSubscriptionPlanResolver' file does not exist in the resolvers directory, it means that the resolver is missing, and that's why the update is failing. You can create the missing resolver file manually or regenerate the resolver using the Amplify CLI. To regenerate the resolver using the Amplify CLI, you can run the following command: amplify update apiFollow the prompts to update the API and generate the missing resolver. Once the resolver is created, you can try updating the CloudFormation stack again to resolve the 'UPDATE_ROLLBACK_FAILED' status. After creating or regenerating the resolver, you should be able to update the stack successfully without encountering the 'SyncSubscriptionPlanResolver' error. I don't have rewritten resolvers, the amplify\backend\api\SplitPay\resolvers folder is empty (only README.md). I successfully executed the amplify update api command, here is its log: The "amplify push" was executed with exactly the same error as before: I sent a report: Maybe the missing resolver needs to be added on the AppSync side? The advice here in the github to change the content of schema.graphql in this file helped me. We have moved one step forward. Maybe I should change something else? I can delete this SubscriptionPlan model and all its associated resolvers in AppSync. But how? |
|
@chirpavel , Are you available for a screen share tomorrow? |
|
@AnilMaktala yes, sure! For now I have some screenshots around yesterday message: The problem appears after this step: And "amplify push" error, rolled back: |
|
Hey @chirpavel, Are you on Discord? If so, could you please share your Discord username with me? |
|
Hey @chirpavel, are you still experiencing this issue? |
Yeeess, the problem is still actual |
|
Hey @chirpavel, sorry for the delay. could you please share your Discord username with me? if will help us to setup a call in Discord and do the screen share? |
|
Hey 👋 , This issue is being closed due to inactivity. If you are still experiencing the same problem and need further assistance, please feel free to leave a comment. This will enable us to reopen the issue and provide you with the necessary support. |
|
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.12.2
Amplify CLI Version
12.12.4
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 added this model:
to the end of SubscriptionPlan model and execute amplify push - nothing work:
amplify push and amplify pull return error: Syntax Error: Expected ":", found "@"
After error i tried amplify push --force and --no-gql-override flag
Nothing helps
Expected behavior
Sorting by date like in the doc:
https://docs.amplify.aws/gen1/javascript/build-a-backend/graphqlapi/best-practice/query-with-sorting/
Reproduction steps
amplify push
Change the model
amplify push
Project Identifier
Project Identifier: 70952c35bc147986b145b568d0636b2e
Log output
Additional information
Data manager doesnt work at all!
Before submitting, please confirm:
The text was updated successfully, but these errors were encountered: