Ben Jeater
Ben Jeater
@ykethan Here you go: ``` { "dev": { "awscloudformation": { "AuthRoleName": "amplify-productname-dev-144015-authRole", "UnauthRoleArn": "arn:aws:iam::465234467934:role/amplify-productname-dev-144015-unauthRole", "AuthRoleArn": "arn:aws:iam::465234467934:role/amplify-productname-dev-144015-authRole", "Region": "eu-west-1", "DeploymentBucketName": "amplify-productname-dev-144015-deployment", "UnauthRoleName": "amplify-productname-dev-144015-unauthRole", "StackName": "amplify-productname-dev-144015", "StackId": "arn:aws:cloudformation:eu-west-1:465234467934:stack/amplify-productname-dev-144015/48dc14b0-b1c1-11ec-a163-02844adf795f", "AmplifyAppId": "doocypzu2klhi", "AuthTriggerTemplateURL": "https://s3.amazonaws.com/amplify-productname-dev-144015-deployment/amplify-cfn-templates/auth/auth-trigger-cloudformation-template.json"...
I first tried `amplify checkout env demo` ``` % amplify checkout env demo Please pass in a valid environment name. Run amplify env list to get a list of valid...
@ykethan I can confirm that the settings in `local-aws-info.json` for the profileName match with a profile name available in my AWS credentials file. I can also confirm that the profile...
Hey @ykethan; no, I am using the "connect branch" button on the app hosting environments page in the AWS console to create the new environments.
Hey @lazpavel, the project identifier is `0a2c62eccf8d3ac5d53ed152c8cb193b`. Running `amplify pull --appId --envName demo` in an empty directory resulted in a successful pull of the environment data. I then ran an...
@ykethan I bumped the `package.json` patch version
Hey @edwardfoyle, I can confirm that the `secretsPathAmplifyAppId` exists in the `dev` environment of my `team-provider-info.json` file. 👍🏻 The environment created locally (`dev`) is fine, but this problem is for...
@josefaidt Reproduction steps 1-5 are the same, but step 6 is where my methodology differed. My steps would be: 1. `amplify init` > environment name `main` 2. create a git...
I found that if you have an empty `turbopack` object in your `next.config` file, then you get this warning. Adding a `resolveExtensions` key and value to the `turbopack` object fixed...
I'm not sure if it's counted as a minimal reproduction of the issue, but the same issue can be seen on the Mui documentation page for the [DateRangePicker](https://mui.com/x/react-date-pickers/date-range-picker/#use-a-multi-input-field) field on...