aws-amplify / aws-amplify/amplify-hosting
AWS Console has broken pages for projects with unsuccessful builds
- Dominant language
- Dockerfile
- Stars
- 481
- Forks
- 123
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the bug**
For the past couple weeks, I have noticed many of our amplify builds (Gatsby projects) getting stuck at the "Provisioning" stage. When that happens, I would need to click on the "Build" link, then click the "Cancel" button, and then click the "Redeploy This Version" button.
I'm still seeing many builds stuck in the provisioning stage, but now when I click on the "Build" button, the AWS Console page is broken, and doesn't render all the way. I've reproduced this on Safari and Chrome. There's an error in the browser's javascript console that says:
`TypeError: null is not an object (evaluating 'r.summary.startTime.getTime')` in `main.js`
**To Reproduce**
See above
**Expected behavior**
You should see a page like this that has the indicated button:

**Screenshots**
Here's a screenshot of the pages with the error above:

**Desktop (please complete the following information):**
- OS: Mac OS 10.15.7
- Browser: Chrome and Safari
Contributor guide
Research direction
Start by reproducing an unsuccessful Gatsby build that remains in Provisioning, then inspect the browser error in main.js while opening the Build page in AWS Console. Done means the page renders fully and exposes the Cancel and Redeploy This Version buttons without the null startTime error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, javascript
- Domain
- ci-cd, cloud
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100