Note: If your feature-request is regarding the AWS Amplify Console service, please log it in the
official AWS Amplify Console forum
I encounter this error when running amplify api gql-compile
but I don't know which file is problematic.
Can you please add an indication of which file is not serializing?
amplify version - 4.38.0
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
I get the same now on my project when running amplify push
'
I did a amplify pull
in the hope to resolve the issue, but it still occurs.
amplify cli version 4.38.0
Update:
It seems to only happen only in one of my environments, not all.
I checked the same error and tried amplify pull, but the error comes out as follows.
amplify cli version 4.38.0
Update:
I solved it by amplify delete, amplify init again in the main branch, amplify env add, and then proceed by choosing to not use the existing environment.
Seems to be related to #6097, closing in favor of that.
Reopening to gather more information on the logging error.
@ywroh That logging related error looks interesting to me, did you cleanup logging data in-between the operations or do you have any pointers on how that could have happened
@attilah Thanks for your interest in my logging information.
Unfortunately, I didn't clean up the logging data between tasks, and I'll tell you as far as I can remember why it happened.
I did amplify init in the dev branch of my hb-platform project and then moved to the test branch to create the test backend and amplify env add, but the test backend was not properly created by selecting use existing environment.
Then, when I came back to the dev branch and entered the above command, an error occurred.
Please understand that my memory may be inaccurate.
@ammarkarachi ^^^
Closing and will track as part of the other similar issue.
Still seeing this using cli version 4.39 and also in the admin ui. Looks like the related issue was closed out. Am I missing some steps here?
Still seeing this using cli version 4.39 and also in the admin ui. Looks like the related issue was closed out. Am I missing some steps here?
I'm getting the same issue here. CLI version 4.39.
I created the project using the admin UI but it is not working in my environment
@dacarva it does not seem like this is released yet when looking at the changelog.
Thanks @atlesp , Yes the fix hasn't been released yet. It should be out soon
Most helpful comment
@attilah Thanks for your interest in my logging information.
Unfortunately, I didn't clean up the logging data between tasks, and I'll tell you as far as I can remember why it happened.
I did amplify init in the dev branch of my hb-platform project and then moved to the test branch to create the test backend and amplify env add, but the test backend was not properly created by selecting use existing environment.
Then, when I came back to the dev branch and entered the above command, an error occurred.
Please understand that my memory may be inaccurate.