Failed to pull the backend.

[GrowingCompany]

How did you install the Amplify CLI?

npm

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

18.20.4

Amplify CLI Version

12.14.0

What operating system are you using?

Mac Sequoia 15.1.1

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

no

Describe the bug

I have a published service in the web and work on making a new project with the same amplify server.
While I'm setting up the project, amplify pull has been failed.

Expected behavior

Succeed pull the backend

Reproduction steps

1. remove all related files,

• aws-exports.js
• amplifyconfiguration.json

2. command amplify pull

3. put credentials
   ? Please choose the profile you want to use default
   ? Which app are you working on? ###
   ? Pick a backend environment: master
   ? Choose your default editor: Visual Studio Code
   ✔ Choose the type of app that you're building · javascript
   Please tell us about your project
   ? What javascript framework are you using react
   ? Source Directory Path: src
   ? Distribution Directory Path: build
   ? Build Command: npm run-script build
   ? Start Command: npm run-script start

4. got failed

Project Identifier

76cd9fdb-58cf-4b29-bc4b-ad21fb9b3f02

Log output

Do you plan on modifying this backend? Yes
⠴ Fetching updates to backend environment: master from the cloud.Overrides functionality is not implemented for this category
✔ Successfully pulled backend environment master from the cloud.
✖ There was an error initializing your environment.
🛑 Failed to pull the backend.

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

PullBackendFault: Failed to pull the backend.
at attachBackend (/snapshot/amplify-cli/build/node_modules/@aws-amplify/cli-internal/lib/attach-backend.js:55:15)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async Object.run (/snapshot/amplify-cli/build/node_modules/@aws-amplify/cli-internal/lib/commands/pull.js:64:9)
at async Object.executeAmplifyCommand (/snapshot/amplify-cli/build/node_modules/@aws-amplify/cli-internal/lib/index.js:194:9)
at async executePluginModuleCommand (/snapshot/amplify-cli/build/node_modules/@aws-amplify/cli-internal/lib/execution-manager.js:139:5)
at async executeCommand (/snapshot/amplify-cli/build/node_modules/@aws-amplify/cli-internal/lib/execution-manager.js:37:9)
at async Object.run (/snapshot/amplify-cli/build/node_modules/@aws-amplify/cli-internal/lib/index.js:121:5)

Unable to parse aws-exports.js. Has this file been modified?
Error: Unable to parse aws-exports.js. Has this file been modified?
at getCurrentAWSExports (/snapshot/amplify-cli/build/node_modules/@aws-amplify/amplify-frontend-javascript/lib/frontend-config-creator.js:301:13)
at getAWSExports (/snapshot/amplify-cli/build/node_modules/@aws-amplify/amplify-frontend-javascript/lib/frontend-config-creator.js:158:35)
at createAWSExports (/snapshot/amplify-cli/build/node_modules/@aws-amplify/amplify-frontend-javascript/lib/frontend-config-creator.js:150:31)
at Object.createFrontendConfigs (/snapshot/amplify-cli/build/node_modules/@aws-amplify/amplify-frontend-javascript/index.js:49:16)
at AmplifyToolkit.onCategoryOutputsChange (/snapshot/amplify-cli/build/node_modules/@aws-amplify/cli-internal/lib/extensions/amplify-helpers/on-category-outputs-change.js:49:37)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async initializeEnv (/snapshot/amplify-cli/build/node_modules/@aws-amplify/cli-internal/lib/initialize-env.js:143:9)
at async onSuccess (/snapshot/amplify-cli/build/node_modules/@aws-amplify/cli-internal/lib/attach-backend.js:81:17)
at async attachBackend (/snapshot/amplify-cli/build/node_modules/@aws-amplify/cli-internal/lib/attach-backend.js:50:9)
at async Object.run (/snapshot/amplify-cli/build/node_modules/@aws-amplify/cli-internal/lib/commands/pull.js:64:9)
at async Object.executeAmplifyCommand (/snapshot/amplify-cli/build/node_modules/@aws-amplify/cli-internal/lib/index.js:194:9)
at async executePluginModuleCommand (/snapshot/amplify-cli/build/node_modules/@aws-amplify/cli-internal/lib/execution-manager.js:139:5)
at async executeCommand (/snapshot/amplify-cli/build/node_modules/@aws-amplify/cli-internal/lib/execution-manager.js:37:9)
at async Object.run (/snapshot/amplify-cli/build/node_modules/@aws-amplify/cli-internal/lib/index.js:121:5)

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.

[ykethan]

Hey @GrowingCompany, thank you for reaching out. Wanted to get some additional information on this. were there any changes in the amplify/.config folder?
additionally, is the aws-exports.js file currently empty?

[GrowingCompany]

Thanks for the reply.

Yes. While pull the backend, generate amplify/.config and apparently filled in aws-export.js.
For your information, the generated aws-exports.js is the same from the other project using same amplify backend.

[ykethan]

Hey @GrowingCompany, wanted to reconfirm the information provided. On running a pull were the correct config and aws-exports files were generated?
Additionally, could you provide us your use case?
if you are looking to add a new environment you can run amplify add env <env-name> or run amplify init and select if you would like to reuse an existing environment or create a new environment.

[GrowingCompany]

I'm pulling an existing environment on aws-amplify.
As I attached, I made it with ' Successfully pulled backend environment master from the cloud.' when try pull request.
aws-config, amplify folder are apparently made with pull request.
Several tries that removing all files(aws-config, amplify folder) and re-pull had same issues.

[GrowingCompany]

Update.

I've just pulled amplify and got same issue.
I did amplify diagnose --send-report and Project Identifier: 28559d110853dd1193389e8652ee6996.
I think this report let you easily take look into this issue.

[ykethan]

@GrowingCompany thank you for the information. From the project identifier, noticed this project appears contain a unmigrated auth resource as the build CloudFormation template uses a yml file.
Could you try downgrading Amplify CLI to v10.0.0, then running a amplify pull. Do let us know if this does till throw an error message.
I would suggest updating the auth resource by running amplify update auth which should should prompt for auth resource migration. On migrating and pushing the resource you should be able to migrate to the latest version and retry the commands.
Additionally, could you provide us information on the project setup? such as frontend framework being used?

[GrowingCompany]

Finally, amplify pull done.

downgrade amplify-cli [email protected] works for the issue.

For your information, project setup specifications below,

• editor: vscode
• typeofapp: js
• framework: react

So should I keep the version of [email protected]?
Is there an issue the latest version of cli?

[ykethan]

Hey @GrowingCompany, as we are able to now pull the backend correctly. Could you try upgrading the Amplify CLI version to latest then try running amplify configure project then rerunning amplify pull in your existing project?
Do let us know if the error does still occur?

As diving into the following the code currently utilizes the environment information and project confirmation. Rerunning the command should recreate the files

amplify-cli/packages/amplify-frontend-javascript/lib/frontend-config-creator.js

Lines 278 to 283 in 2ce4283

	const { amplify, exeInfo } = context;
	const projectPath = exeInfo?.localEnvInfo?.projectPath || amplify.getEnvInfo().projectPath;
	const { config: frontendConfig } = exeInfo?.projectConfig?.[constants.Label] || amplify.getProjectConfig()[constants.Label];
	const srcDirPath = path.join(projectPath, frontendConfig.SourceDir);
	const targetFilePath = path.join(srcDirPath, constants.exportsJSFilename);
	let awsExports = {};

additional, do you have any babel configuration defined in your project?

[GrowingCompany]

Unfortunately, amplify pull failed after upgrading cli version to 12.14.2 :(

Here are configuration below.

Configuring amplify project has successfully created files below.

• aws-exports.js
• amplifyconfiguration.json

I haven't defined any babel configuration in my project.

[ykethan]

@GrowingCompany thank you for information. Would you be open to sharing us your amplify folder as zip?
This would help us to dive deeper into the issue and reproduce the behavior.
Could you provide us the zip at [email protected]. Do let us know if you are unable to send this.

[GrowingCompany]

Appreciate for your help !

However, amplify folder has all of our data structure, so it's a bit strict :(

Are There other ways to share my environment with you?

[ykethan]

I understand, information on reproducing the issue would help us in further investigating this. Do you also observe this issue on a new App? if yes, could you share a zip of repository or minimal reproduction steps?