Inconsistencies in Amplify init framework selection flow

[ykethan]

How did you install the Amplify CLI?

No response

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

No response

Amplify CLI Version

12.4.0

What operating system are you using?

Mac

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

no

Describe the bug

When running init a empty folder, the following occurs
when selecting angular as framework the init fails with and error about a missing file

while the other frameworks allows you to create the env.

while selecting say ios as app which requires xcode the cli fails at the end not start

Expected behavior

consistency in flows and document requirements

Reproduction steps

1. amplify init
2. select angular as framework

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.

[josefaidt]

Confirmed this is a bug. Note for fix, we can likely remove this validation to align with other frameworks such as react