- Newest
- Most votes
- Most comments
The main reason for this might be due to the authentication events are not being triggered as expected.
Ensure that your custom domain is configured to allow cross-origin requests, and the CORS settings for the backend services (e.g., APIs) are correctly configured. Cross-origin issues can prevent events from being triggered.
Make sure that the OAuth redirect URIs in your Amplify app are updated to include your custom domain (https://myCustomDomain.org/
).
Make sure that you are using the latest versions of the AWS Amplify libraries (@aws-amplify/core
, @aws-amplify/ui-react
, etc.). Update your dependencies to the latest versions and check if the issue persists.
In case if you are still observing the same issue, then reach out to the AWS Premium Support for further troubleshooting of the same.
Relevant content
- Accepted Answerasked 3 months ago
- asked 3 years ago
- asked 2 months ago
- asked 2 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
How do I check that?
Thank you. Your "answer" turned out to be the tip I needed to figure it out.
Turned out I had a problem in my configuration. My app is setup to serve from https://www.my-custom-domain.org/ but my Authentication was configured with https://my-custom-domain.org/ so it didn't have the www. part of the URL my browser was visiting. Updating my config w/ the www fixed it.