aws-amplify / aws-amplify/amplify-cli

Amplify pull no longer working - Error initializing environment

Open
#12,997 4 comments 0 reactions 0 assignees View on GitHub
bug not-reproducible p4 platform-pull transferred
Dominant language
TypeScript
Stars
2.9k
Forks
825
Avg merge
11d 23h
Merged PRs (30d)
2

Description

### Before opening, please confirm:

- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-adminui/issues?q=is%3Aissue+).
- [X] I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-adminui/blob/main/CONTRIBUTING.md#bug-reports).
- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
- [X] I have removed any sensitive information from my code snippets and submission.

### App Id

d33mq6303fvph9

### Region

us-west-1

### Environment name

staging

### Figma File Version (if applicable)

_No response_

### Amplify CLI Version

12.1.1

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

18.15

### What operating system are you using?

Win

### Browser type?

Chrome

### Describe the bug

When trying to run Amplify Pull. I get the following error. I try all authentication methods but it doesnt go through.

amplify status = works
amplify console = works
amplify pull = error below
? Select the authentication method you want to use: Amplify Studio
? Select the authentication method you want to use: Amplify Studio
? Select the authentication method you want to use: Amplify Studio
× Fetching updates to backend environment: staging from the cloud.
× There was an error initializing your environment.
🛑 Could not initialize platform for 'staging': Stack with id... does not exist.

### Expected behavior

Should pull from AWS

### Reproduction steps

amplify pull

### Project Identifier

_No response_

### Additional information

_No response_

Contributor guide

Open the contributing guide

Research direction

Start by reproducing `amplify pull` with Amplify CLI 12.1.1, Node.js 18.15, Windows, and the stated region and environment. Trace the environment initialization path and the reported missing CloudFormation stack; done means identifying why the staging environment cannot be initialized and restoring a successful pull.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, node.js, typescript
Domain
backend, cli, cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.