Fix: Preventing the google,facebook login crash when env files are missing #85
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
📌 Linked Issue
Closes #78
🛠 Changes Made
handleGoogleLoginandhandleFacebookLogininLogin.jsxto prevent execution if API keys are missing.REACT_APP_GOOGLE_CLIENT_IDorREACT_APP_FACEBOOK_APP_IDare undefined or set to default placeholders.🧪 Testing
.envkeys): Clicked "Sign in with Google". Verified that the app stays on the login page and shows the red error alert instead of redirecting.📸 UI Changes (if applicable)
📝 Documentation Updates
✅ Checklist
💡 Additional Notes
This fix ensures the application remains stable and professional in production environments (like Netlify/Vercel) even if the maintainer has not yet configured the OAuth secrets. It prevents the "Invalid Client" crash that was reported in Issue #78.