Promote dev → uat: GRO-2572 SSO redirect fix (#91) #92
Reference in New Issue
Block a user
Delete Branch "dev"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Promotes [GRO-2572] fix to UAT for QA regression.
Change summary
src/App.tsx:handleSocialLoginnow followsresult.data.urlfrom Better AuthsignIn.social()response — the SSO button previously fired the request but never navigated the user to Authentiksrc/__tests__/App.test.tsx: regression test added (GRO-2572)UAT_PLAYBOOK.md §5.4.1 TC-WEB-SSO-2: updated — requires a fresh/incognito context (stale auth cookie masked the defect in prior UAT run)QA focus
TC-WEB-SSO-2 is the critical regression:
https://uat.groombook.dev/loginhttps://auth.farh.net/...within ~1 sThe prior UAT pass (Shedward) succeeded only because a session cookie from a manual
window.location.hrefcall was already present. A truly clean context would have shown the dead button.QA code review APPROVED (GRO-2574 / GRO-2572).
Core fix verified: handleSocialLogin in src/App.tsx follows result.data.url from Better Auth signIn.social(), error guard returns early before redirect. Regression test added in src/tests/App.test.tsx covers the new path.
CI: all 6 checks green (Test, Lint & Typecheck, Build — push + pull_request).
UAT_PLAYBOOK.md updated for every user-facing change: TC-WEB-SSO-2 (fresh/incognito note) plus TC-WEB-5.16.4–7 for the bundled portal tab-row overflow fixes (GRO-730/GRO-1026).
Bundled portal/CSS changes reviewed — clean, with playbook coverage. Engineer may self-merge per SDLC.