Amplify Init asks for code.

[qwikag]

this screen is offered, but there is no code to compare it to:

[reesscot]

Transferring to CLI, as this issues is related to amplify init

[josefaidt]

Hey @qwikag 👋 where are you seeing this?

[qwikag]

@josefaidt

2 parts to my response,

1. I answer your question.

2. the fix that is required.

Because of all of the issues I have been having, I started again from the beginning.
Followed the guide to the letter.
and ran into all of the same problems with CLI Auth, setup of APIs and App Auth, and Lambda access to Graphql.

Where did I see it this sccreenshot:
When using the Config file setup you advised in that other ticket 4488#issuecomment-1607961390

[profile profile1]
sso_session=mysso
sso_account_id=0123456789435
sso_role_name=AdminAmplify
region=ap-southeast-2
output=json
credential_process=aws sso login --profile profile1

[sso-session mysso]
sso_start_url=https://domain.awsapps.com/start
sso_region=ap-southeast-2
sso_registration_scopes=sso:account:access

This is what the result looks like (which includes the screenshot I previously supplied and hence this answers your question:"

amplify init
Note: It is recommended to run this command from the root of your app directory
? Enter a name for the project test
The following configuration will be applied:

Project information
| Name: test
| Environment: dev
| Default editor: Visual Studio Code
| App type: javascript
| Javascript framework: none
| Source Directory Path: src
| Distribution Directory Path: dist
| Build Command: npm.cmd run-script build
| Start Command: npm.cmd run-script start

? Initialize the project with the above configuration? Yes
Using default provider awscloudformation
? Select the authentication method you want to use: AWS profile

For more information on AWS Profiles, see:
https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-profiles.html

? Please choose the profile you want to use profile1
🛑 Failed to get profile credentials
Unexpected token A in JSON at position 0

Learn more at: https://docs.amplify.aws/cli/project/troubleshooting/

Session Identifier: bbbbbbbb-eeee-4444-9999-1111aaaa2222

Hence not only did I get a browser screen prompt that is factually inaccurate but also it does not work.

[qwikag]

What is fundamentally missing is the info about having process-level environment variables.

If those are missing then the browser requests access, as per picture.

[qwikag]

Hey @josefaidt ,
And if we follow the guide and do >amplify configure , it setups up the creds in the credentials file, which are completely useless.

It is just all over the place.

I plan to get my head into the cli code and see if I can add some value because I feel quite invested at this point.

And I want this (Amplify) to be a better place.

[josefaidt]

Hey @qwikag apologies for the delay here. If you currently have AWS credentials set locally you do not need to run amplify configure, and can instead bypass this step in favor of selecting an existing AWS profile during amplify init

In the original screenshot it appears to have attempted to authorize with Amplify Studio, which is the default behavior when Amplify Studio is enabled for an Amplify application.

From the previous error log:

? Please choose the profile you want to use profile1
🛑 Failed to get profile credentials
Unexpected token A in JSON at position 0

Can you check the ~/.amplify/admin/config.json file for a leftover record for this App ID? It is possible there is a stray artifact in this file that is causing the CLI to attempt to authorize with Studio

[josefaidt]

Closing due to inactivity

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please 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.