Aucune réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
Contenus pertinents
- demandé il y a un an
- demandé il y a un an
- demandé il y a un an
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 4 mois
We ran into probably the same issue as well (see question here: https://repost.aws/questions/QUboDhRl5DSB20Qr6qmBUGXw/amplify-console-custom-domain-shows-different-content-than-default-url). Were you able to figure out what was happening? For us, it seemed like a caching issue, since the updates are reflected in the default Amplify generated URL, but not the linked custom domain. Deleting and re-adding our custom domain 'fixed it'. But of course that isn't really a solution.