Repository navigation
fix: restore Google sign-in on Cloudflare Workers - #101
Conversation
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configuration
⛔ Files ignored due to path filters (2)
📒 Files selected for processing (5)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Preview database and deployment Commit: Migration command and Cloudflare build/deploy completed successfully. There may have been no pending migrations. Migration status is inferred from the required migration hook and the overall Cloudflare result. Build logs contain the individual migration output. |
🚀 Deploying Preview to Cloudflare 🚀Preview URL: https://gurbinder-fix-google-sign-in.preview.invoicely.gg (commit e91d638)This URL reflects your latest Preview deploymentPreview Deployments by commit
|
|
Production database and deployment Commit: Migration command and Cloudflare build/deploy completed successfully. There may have been no pending migrations. Migration status is inferred from the required migration hook and the overall Cloudflare result. Build logs contain the individual migration output. |
Google sign-in on invoicely.gg stopped before redirecting to Google after #100: the auth routes returned HTTP 500 and the button stayed disabled. Reproduced with Computer Use in Dia and in the built Cloudflare Worker.
Sentry 10.76.0 imports a build helper from its server runtime entry. That helper eagerly calls
createRequire(__filename), but OpenNext supplies an empty filename inside the Worker bundle, crashing instrumentation startup before auth runs.This change:
yarn test:securityand documents when to remove the temporary patch/pin.Validation:
/api/auth/okreturns 200 JSON; unauthenticated/api/auth/get-sessionreturns 200/null; an invalid social sign-in body returns 400 JSON instead of a startup 500.No database migration or Google OAuth credential change is required for this fix. A complete Google account login on production still needs verification after deployment; the local check uses placeholder credentials and does not claim that flow completed.