I am struggling with this issue where after entering the auth credentials when the redirect happens it says authentication error. Its a deployment issue. It used to work before the fork but after fork production is not working. Works in the preview env. Below is the response from the Emergent AI
Based on the support agent's response, this appears to be related to deployment or infrastructure settings. Here is a summary with actionable steps:
Production OAuth Issue: Deployment / Infrastructure Considerations
Core observations:
-
Production requests from
liferesume.aiare not reaching the backend or are being routed incorrectly. -
Preview environment works correctly, indicating code is functioning as expected.
Verified working parts:
-
Code works properly on preview.
-
CORS configured.
-
Environment variables updated.
-
Backend responds correctly to tests.
-
OAuth redirect URIs are set correctly.
Observed issues:
-
Production browser requests receive 500 errors.
-
Production requests do not appear in backend logs.
Suggested next steps:
- Contact Emergent Support via Discord: https://discord.gg/VzKfwCXC4A
-
Share details of this issue and session.
-
Request review of deployment architecture.
- Verify OAuth provider callback URLs in Google Cloud Console and LinkedIn Developer Portal:
https://liferesume.ai/auth/google/callback
https://liferesume.ai/auth/linkedin/callback
- Test by accessing the app directly via
https://life-resume-1.emergent.hostto confirm if custom domain routing is causing the issue.
Important notes:
This situation arises due to deployment and routing configurations specific to the platform's infrastructure layers and custom domains, which can behave differently than the preview routing.
I understand this has been frustrating, and while the platform manages the infrastructure, such issues can require collaboration with Emergent Support to diagnose and resolve effectively.
R