chris
chris
Hello, we are currently investigating this issue and will report back soon. Apologies for the inconvenience. In the meantime, I am transferring this issue to the CLI repo as the...
Just to clarify, when you say "build" do you mean you are building the amplify app locally with the command `amplify build` or are you referring to the build step...
@rwmorton Wasn't able to reproduce this exact error with a new amplify project using CRA v5 but that tutorial does look outdated. The getting started guide from the amplify docs...
Hey @ahansson89 👋 apologies for the delay here. Since this issue speaks to the documentation specifically, I'm going to transfer it to the docs repo so that we can add...
Hi 👋 Closing this as we have not heard back from you. If you are still experiencing this issue and in need of assistance, please feel free to comment and...
> it does not seem deterministic which one is there. I'm not exactly sure what you mean, the record that is synced and persisted to the client should always be...
Hi @frankarnaud 👋 could you try following this documentation to allow your IAM user to access the GraphQL API in the AppSync console? https://docs.amplify.aws/cli/graphql/authorization-rules/#use-iam-authorization-within-the-appsync-console Also, please try changing the auth...
@frankarnaud yeah, you're correct. After digging into this further last week, you would've received an unauthorized error response from AppSync if your IAM role/user didn't have access in the console....
Can you share the `cli.json` file in your amplify folder as well as the request and response resolvers for `listArticles` in your `amplify/api/build/resolvers` folder?
Looks like you're on an older version of the amplify CLI. Would you be able to upgrade to the latest version, make a small change to the schema, and then...