sst deploy interrupted with no error: hard-reset the state snapshot in S3

What was reported: Issue anomalyco/sst#4573 (closed, 48 comments): sst deploy (ion) gets interrupted every time with no error message. Verbose logs just stop partway through initializing the project. The reporter was following the aws-nextjs example and could not tell what was wrong, since nothing in the output pointed at a cause.

What works: Community-verified hard reset. Commenter tienpvse1 fixed it by resetting SST's state in S3: go to the sst-state bucket for your app, open the snapshots folder, download the latest snapshot from when SST was still working, and use that JSON to replace the state in your local app folder. That forces a hard reset of the corrupted state and the deploy goes through. This is the fix to reach for when sst deploy dies silently and nothing in the verbose logs explains why, rather than recreating the whole stage.

In the GitHub issue, the reporter asked: sst deploy interrupted with no error: hard-reset the state snapshot in S3. The working answer that came out of the thread: Community-verified hard reset. Commenter tienpvse1 fixed it by resetting SST's state in S3: go to the sst-state bucket for your app, open the snapshots folder, download the latest snapshot from when SST was still working, and use that JSON to replace the state in your local app folder. That forces a hard reset of the corrupted state and the deploy goes through. This is the fix to reach for when sst deploy dies silently and nothing in the verbose logs explains why, rather than recreating the whole stage. Source: https://github.com/anomalyco/sst/issues/4573