1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
It looks like the Amplify service team is aware and working on this issue: https://github.com/aws-amplify/amplify-hosting/issues/2846
con risposta 2 anni fa
Contenuto pertinente
- AWS UFFICIALEAggiornata 9 mesi fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
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?