Ujjwol Shrestha

We were having same issue with a docker on version 3.5.0 which uses chromium 124.0.0.0 We've been able to run our tests by forcing the version to chromium 124.0.6367.60-r0 from...

> Hi @ujjwol05 this might be related to aws-amplify/amplify-backend#1069 Can you try installing the latest beta versions of @aws-amplify/backend and @aws-amplify/backend-cli and see if that resolves the issue? ok upgrading...

@renebrandel ``` { "name": "test", "version": "0.1.0", "private": true, "scripts": { "dev": "next dev", "build": "next build", "start": "next start", "lint": "next lint", "sandbox-delete": "npx amplify sandbox delete", "sandbox": "npx...

> Hi @ujjwol05, good to know that the upgrade resolved your issue with list queries. For the other snippet you shared i.e > > > const {data} = await client.models.Todo...

> @ujjwol05 can you please try the above steps and see if that works for you as well? Thanks Did all the steps except the last 2 steps and i...

> The [quickstart vite-react app](https://docs.amplify.aws/gen2/start/quickstart/vite-react-app/) does not build succesfully due to type error of `Schema["Todo"]`; I am using 1.0.0 version of `@aws-amplify/backend`, the type of `Schema["Todo"]` does not match the...

@milosevicd ```TS2353: Object literal may only specify known properties, and resourceGroupName does not exist in type FunctionProps``` It seems that FunctionProps is missing resourceGroupName

@milosevicd The type issue seems to be resolved after the upgrade. However, the main issue still persists. I'm trying to inject TABLE_NAME as an environment variable programmatically using both: backend..addEnvironment()...