Amplify AWS Console bugs

[rsenchyk]

Before opening, please confirm:

• [X] I have checked to see if my question is addressed in the FAQ.
• [X] I have searched for duplicate or closed issues.
• [X] I have read the guide for submitting bug reports.
• [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

App Id

d2lcrnqmymps44

Region

eu-west-1

Amplify Hosting feature

Not applicable

Describe the bug

Created with Terraform (V 1.0.8, provider /hashicorp/aws v4.19.0) Amplify app does not work correctly through ABC Console.

1. When going to the App settings > General tab, AWS Console displays empty page
2. Info about Provision, Build, Deploy, Verify also are not accessible - AWS Console displays empty page. For example when i try to see build logs, in developer console in browser i see On prod.eu-west-1.appstate.amplifyapp.com/AppState?appId=<my_app_id> i see

{"message":"Requested app was not found"}

I tried to use it in Firefox web browser, but the result was the same. Regardless of all this, the app works properly. If i launch the new app from AWS Console, everything works properly

Expected behavior

Access to Provision, Build, Deploy, Verify and App settings information from AWS Console.

Reproduction steps

1.Apply my terraform code amplify.txt 2.Go to AWS Console 3.Run build 4.Try to access Provision or Build or Deploy or Verify or App settings information 5. Empty page

Build Settings

No response

Additional information

No response

[ghost]

Hi @rsenchyk 👋🏽 thanks for raising this issue. I was not able to reproduce this behavior. 🤔 I was able to create an Amplify app using Terraform and when I clicked around the console I saw the 404 errors but I didn't run into any blank screens. Was this a one-off case or is this behavior happening consistently?

Also is the amplify.txt your entire terraform script? If not please share the entire script if you can so I can test it out on my end as well.

[ghost]

Please provide an HAR capture for us to further investigate the blank screen behavior. Thank you!

[rsenchyk]

Was this a one-off case or is this behavior happening consistently?

It happens everytime i try to deploy the app with Terraform. I tried it on different accounts and different regions (eu-central-1, eu-west-1), but the result was the same.

Also is the amplify.txt your entire terraform script? If not please share the entire script if you can so I can test it out on my end as well.

Here is my complete script amplify.txt amplify-assume-policy.txt provider.txt variables.txt

Please provide an HAR capture for us to further investigate the blank screen behavior.

HAR Capture contains sensitive information about my account and contains thousands of lines, so i am not able to remove what i need. Maybe there are another ways to give you more information?

[ghost]

@rsenchyk thanks for providing the files. I will test this out on my end to try and reproduce the behavior. You can send the HAR capture privately to [email protected]. Please be sure to add this GH issue to your email so we can properly track all the details regarding this issue. Thank you!

[rsenchyk]

Hi, @hloriana ! how are you doing with reproducing the bug, do you have any updates?

[ghost]

Hi @rsenchyk apologies for the delay. I'm collaborating with the team to dive deeper into the issue. We received your email with the HAR capture as well. Thank you for providing these details, we will provide an update once we have more information.

[calavera]

Hi,

Our console team has made several improvements to the console and you should never see a blank page again. Thanks for opening this ticket, it's super helpful.

[github-actions[bot]]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see. If you need more assistance, please either tag a team member or open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.

[github-actions[bot]]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.