soroush.asadi
23b3713b44
Root cause: the server sends matchFound then immediately broadcasts the first state, but the client only subscribes to state inside enterServerMatch, which runs a React effect later — so the ordered "state" message is dispatched while there are no subscribers and is dropped. The server then waits for the human hakem's trump choice that can never come → permanent freeze on the green felt. - signalr-service: cache lastState; replay it to a late onState subscriber on a microtask (after enterServerMatch resets its store); clear the cache on every fresh-match entry (startMatchmaking / createRoom / acceptInvite) so a finished game's final state is never replayed into a new match. - safety net: if no state lands within 2.5s of matchFound, the client invokes the new Resync hub method; server re-sends the current state to that player. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This is a Next.js project bootstrapped with create-next-app.
Getting Started
First, run the development server:
npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev
Open http://localhost:3000 with your browser to see the result.
You can start editing the page by modifying app/page.tsx. The page auto-updates as you edit the file.
This project uses next/font to automatically optimize and load Geist, a new font family for Vercel.
Learn More
To learn more about Next.js, take a look at the following resources:
- Next.js Documentation - learn about Next.js features and API.
- Learn Next.js - an interactive Next.js tutorial.
You can check out the Next.js GitHub repository - your feedback and contributions are welcome!
Deploy on Vercel
The easiest way to deploy your Next.js app is to use the Vercel Platform from the creators of Next.js.
Check out our Next.js deployment documentation for more details.