Skip to content
Everframe Docs
Documentation

User identity

Which viewer hit this crash? One call after sign-in.

Updated 

m.global.everframe.callFunc("setUser", { id: "user-123", email: "[email protected]", displayName: "Jane" })
m.global.everframe.callFunc("setUser", invalid)  ' on sign-out

Reports recorded after the call carry the user. The three fields are id, email and displayName; numbers and booleans are converted to strings, and other non-string values are dropped.

This is an unauthenticated claim — useful for recognising a crash from your own QA or a known account, but not evidence of who the viewer is. The Roku SDK has no verified identity tokens.

The user is held in memory for the session. It is not written to the registry, so a crash detected on the next launch from the exit record carries no user; crashes recorded in-process — instrumentation and captureException — do.