Downloading amplify_outputs.json from Amplify console doesn't work anymore

[vandaeldev]

Environment information

System:
  OS: Windows 11 10.0.22631
  CPU: (16) x64 AMD Ryzen 7 5800H with Radeon Graphics
  Memory: 4.74 GB / 15.35 GB
Binaries:
  Node: 22.6.0 - ~\AppData\Local\fnm_multishells\21080_1724660645126\node.EXE
  Yarn: undefined - undefined
  npm: 10.8.2 - ~\AppData\Local\fnm_multishells\21080_1724660645126\npm.CMD
  pnpm: 9.8.0 - ~\AppData\Local\pnpm\pnpm.EXE
NPM Packages:
  @aws-amplify/auth-construct: 1.3.0
  @aws-amplify/backend: 1.1.1
  @aws-amplify/backend-auth: 1.1.3
  @aws-amplify/backend-cli: 1.2.5
  @aws-amplify/backend-data: 1.1.2
  @aws-amplify/backend-deployer: 1.1.0
  @aws-amplify/backend-function: 1.3.4
  @aws-amplify/backend-output-schemas: 1.2.0
  @aws-amplify/backend-output-storage: 1.1.1
  @aws-amplify/backend-secret: 1.1.0
  @aws-amplify/backend-storage: 1.1.2
  @aws-amplify/cli-core: 1.1.2
  @aws-amplify/client-config: 1.2.1
  @aws-amplify/deployed-backend-client: 1.4.0
  @aws-amplify/form-generator: 1.0.1
  @aws-amplify/model-generator: 1.0.5
  @aws-amplify/platform-core: 1.0.6
  @aws-amplify/plugin-types: 1.2.1
  @aws-amplify/sandbox: 1.2.0
  @aws-amplify/schema-generator: 1.2.1
  aws-amplify: 6.5.2
  aws-cdk: 2.154.1
  aws-cdk-lib: 2.154.1
  typescript: 5.5.4
AWS environment variables:
  AWS_NODEJS_CONNECTION_REUSE_ENABLED = 1
  AWS_SDK_LOAD_CONFIG = 1
  AWS_STS_REGIONAL_ENDPOINTS = regional
No CDK environment variables

Description

Problem

After deploying my app to AWS Amplify, trying to download the amplify_outputs.json file from the Amplify console gives an error:

This happens in spite of every resource created fresh, as it's a first deployment.

App info

The app in question is using the latest versions (at time of writing) of the aws-amplify packages:

Besides basic auth, data and storage definitions, the app also uses a basic HTTP API created in the backend.ts file. This is included with the backend.addOutput() method, per documentation guidelines:

I don't specify a version here, because the default should be '1.1'.

Expectation

I would expect that when an app gets deployed for the first time that every resource gets created according to the same schema version and that there shouldn't be a mismatch, like the error seems to be indicating.

[Jay2113]

Hi @vandaeldev 👋 , thanks for raising this! I was able to reproduce this issue and marking as a bug.

[ioanabrooks]

Hi @vandaeldev, the fix has been deployed. Please give it a try and let us know if you encounter any other issues!

[vandaeldev]

@Jay2113 @ioanabrooks I can confirm it works again. Thanks for the quick fix and response!

[carlos-naranjo-aa]

Yesterday i was able to download amplify_outputs.json now i cannot download it anymore. whatever you did it broke at least by console ability to download it. I try to deploy in a new application and in a new region , both in the us and India and it did not work

[jshamel]

Trying to download it right now and it is not working ( in Chrome and Edge )

[dagnym]

the option to download amplify_outputs is only showing on the gen 2 docs example project - yet it is not showing up on any of my other projects, despite the backend resources being successfully deployed. any idea why this is? i'm using the same yml

[tylerlan-rhizome]

Hey all! I think I am experiencing something similar to @dagnym; I cloned the amplify-next-template and followed the Amplify Gen 2 Quickstart example to the letter. However, when it comes to the step of clicking the "Download amplify_outputs.json" button, I can't do it because the button simply is NOT PRESENT in the GUI,

I know it's not a permissions thing because I paired with the Admin and they don't see the button either.

[tylerlan-rhizome]

Hey all! I think I am experiencing something similar to @dagnym; I cloned the amplify-next-template and followed the Amplify Gen 2 Quickstart example to the letter. However, when it comes to the step of clicking the "Download amplify_outputs.json" button, I can't do it because the button simply is NOT PRESENT in the GUI,

I know it's not a permissions thing because I paired with the Admin and they don't see the button either.

✅ SOLVED: Clear browser cache, log back in, wait 10 minutes, and presto! The button re-appears.

The part of this that is still confusing to me is why my team's Admin, using his own machine--not related to my OS or browser config--was able to independently verify this issue, and yet now, having changed nothing on his end, he also sees that the button has been restored...