Closed JamesPHoughton closed 3 weeks ago
In retrospect, I think this is happening in intro and exit steps, and that we successfully catch the issues during the game itself.
Nicolas suggests:
The empirica useX hooks use context internally. If you do if (!player) return
; at the top of your render tree, then player should always be available below that. This is actually what we're doing for "managed" games: https://github.com/empiricaly/empirica/blob/main/lib/%40empirica/core/src/player/classic/react/EmpiricaContext.tsx#L221-L254
Sentry Issue: DELIBERATION-EMPIRICA-79
Sentry Issue: DELIBERATION-EMPIRICA-70
Sentry Issue: DELIBERATION-EMPIRICA-6Z
Sentry Issue: DELIBERATION-EMPIRICA-6Y
Sentry is reporting errors using properties of hooks,
in exit steps:
https://watts-lab.sentry.io/issues/5212693155/events/138db482108740239371a0e251c3bcf7/