While trying to sign in via Facebook on the jobseeker portal of letmibd.com, a fatal production error was encountered, exposing backend code and stack traces. This raises multiple QA red flags.
- URL:
https://letmibd.com/login/jobseeker/facebook - Method: GET
- Status:
500 Internal Server Error - Error Message:
Class 'Socialite' not found File: app/Http/Controllers/Auth/LoginController.php Line: 50
- Visit
https://letmibd.com - Navigate to Jobseeker > Login
- Choose "Sign in with Facebook"
- You are redirected to an error page showing exposed stack trace and file paths
- Missing Laravel Socialite Package: The
Socialiteclass is being called but not available. - Debug Mode Enabled in Production: Full stack trace and file paths are publicly visible.
- Critical Route Failure: Facebook OAuth login is broken for jobseekers.
- Jobseekers are unable to log in via Facebook, potentially losing candidates
- Backend paths and framework stack traces exposed publicly (security risk)
- Unhandled errors lower trust in the platform for first-time users
- Risk of SEO indexing error pages which may harm brand image
- Install Socialite and properly register its service provider in
config/app.php - Set
APP_DEBUG=falsein.envfor production environment - Implement fallback error pages and proper exception handling
- Include social auth routes and services in automated test coverage
Issue discovered on: 2025-08-06
Reported to platform (letmibd.com): [Pending / Awaiting response]
This is a perfect example of why production-readiness checks and QA validations must never be skipped. A broken login not only affects UX, but also raises trust and credibility issues.
Software Engineer (QA) | HealthTech | Passionate about testing, tools, and UI quality.
