1回答
- 新しい順
- 投票が多い順
- コメントが多い順
0
It looks like the Amplify service team is aware and working on this issue: https://github.com/aws-amplify/amplify-hosting/issues/2846
回答済み 2年前
関連するコンテンツ
- AWS公式更新しました 10ヶ月前
- AWS公式更新しました 2年前
It looks like the Amplify service team is aware and working on this issue: https://github.com/aws-amplify/amplify-hosting/issues/2846
Deleting the custom domain and readding it worked, but still wondering how we got in this situation to begin with. Would appreciate any insight!
We're seeing exactly the same issue, and it seems to have started around when this post was made. I'd rather avoid deleting/recreating the custom domain if we can - are there any other suggestions for how to resolve this?