aws-amplify / aws-amplify/amplify-cli

Amplify hosting not detected

Open
#13,230 8 comments 0 reactions 0 assignees View on GitHub
bug hosting p3
Dominant language
TypeScript
Stars
2.9k
Forks
825
Avg merge
11d 23h
Merged PRs (30d)
2

Description

### How did you install the Amplify CLI?

npm

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

v18.17.1

### Amplify CLI Version

12.4.0

### What operating system are you using?

Windows 10

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

Amplify hosting MAYBE was added from console?

### Describe the bug

I have changed my application from angular to plain JS

The build and deploy works fine and I can see the new files, but I can fetch the old files from the angular version.

I have executed
```
amplify publish -c
🛑 Add hosting to your project before publishing your project
Command: amplify hosting add
```

It's and old Amplify inhalation and I'm not sure how the hosting was added.

Hosting add not works

```
amplify hosting add
√ Select the plugin module to execute · Hosting with Amplify Console (Managed hosting with custom domains, Continuous deployment)
You have already connected branches to your Amplify Console app. Please visit the Amplify Console to manage your branches.

```

### Expected behavior

Some way to sync hosting options with `amplify pull`

### Reproduction steps

I can't reproduce the error.

### Project Identifier

e2a6b48c5b48584b6f1162da36d4e8de

### Log output

```
# Put your logs below this line

```

### Additional information

_No response_

### Before submitting, please confirm:

- [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.

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the reported `amplify publish -c`, `amplify hosting add`, and `amplify pull` flows, then reproduce the existing Amplify Console hosting state described in the issue. Done means an existing hosted project is detected consistently and publishing no longer reports that hosting must be added.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.