Optional Amplify Console UI changes

[hackmajoris]

How did you install the Amplify CLI?

No response

If applicable, what version of Node.js are you using?

No response

Amplify CLI Version

11.0.5

What operating system are you using?

Mac, Windows, Linux

Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

No

Describe the bug

The new Amplify Console design should be optional and not mandatory.
Some features such as: build stages, Cypress integration are gone, and it's inadmissible to push such changes without noticing them in advance.

Expected behavior

The new UI is optional in respect for the projects which uses Amplify Gen 1 and the migration to Gen 2 is impossible because of unstableness of Amplify.

Reproduction steps

1. Check Amplify Console.

Project Identifier

No response

Log output

# Put your logs below this line

Additional information

No response

Before submitting, please confirm:

• I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
• I have removed any sensitive information from my code snippets and submission.

[dorutiuga]

In the new UI, there are some issues when trying to open a previous deploy.

Recording.2024-05-07.094516.mp4

[dorutiuga]

Another issue: Openning custom headers on an application is not possible

then, trying to navigate to all apps is not working. It changes only the url, staying on the same page

[dorutiuga]

Another issue:

this is randomly appearing on different pages

[swaminator]

Another issue: Openning custom headers on an application is not possible

then, trying to navigate to all apps is not working. It changes only the url, staying on the same page

@dorutiuga are you using Safari?

[Jay2113]

Another issue: Openning custom headers on an application is not possible

then, trying to navigate to all apps is not working. It changes only the url, staying on the same page

@dorutiuga we are unable to reproduce this behavior. Can you share some reproduction steps for this issue? Also, are you consistently observing it?

[TenetMax]

Another issue: Openning custom headers on an application is not possible

then, trying to navigate to all apps is not working. It changes only the url, staying on the same page

I am also seeing this issue. As far as I can tell the steps to reproduce are simply to have had custom headers set up prior to the new UI having rolled out. As mentioned, simply clicking the link to view the headers results in this error:

The console error itself is:

TypeError: JSON.parse(...).map is not a function

This maps to the following code:

            var t = {
                customHeaders: JSON.parse(e).map((function(e) {

This is happening because e here is an object, not an array:

It seems that after parsing it is expecting to match the application, then key in on .customHeaders

[Jay2113]

@TenetMax @dorutiuga Can you share your Amplify app id on which you are observing the custom headers issue?

[dorutiuga]

@TenetMax @dorutiuga Can you share your Amplify app id on which you are observing the custom headers issue?

Sure, d6myjg10lg61f

[hackmajoris]

Navigating through the Amplify console with Safari is nearly impossible. After clicking on different sections (such as attempting to view previous builds and checking the logs), the UI freezes, and only refreshing the page helps.

[TenetMax]

@TenetMax @dorutiuga Can you share your Amplify app id on which you are observing the custom headers issue?

d1rmomz2jsmjjk

[gongora92]

I can't change the production branch in the new interface. I don't get any error, it just does not update

Screen.Recording.2024-05-08.at.11.59.02.mov

[hackmajoris]

@Jay2113 Is there a reason to not have the new Amplify Console UI as optional, at least for a while?. Every AWS service provided an option to choose between new UI and old one. Why Amplify can't?