Skip to content

A page throws an "invalid identifier" error only when opened from a specific lobby or shortcut, not when opened directly — why would the path matter?

Answer

The two routes can pass different context or parameters into the same page, so the page's query logic may be receiving something it doesn't handle from one path — compare the exact parameters each route sends rather than assuming the page itself is broken.

← Browse Developer Studio, deployment, and upgrades questions