Testing with the Inspector
Inspect SDK calls without writing live analytics or cloud saves.
On this page
Run a test
Open Inspector, paste your externally hosted HTTPS game URL, then load it. The host must allow framing by the current platform origin. This tool does not upload or approve your game. Test on phones and desktop too. For a localhost platform wrapper, initialize with the exact origin:
await ZUQ.init({parentOrigin: "http://localhost:8788"});Use the default production origin for the submitted build. Parent origin changes should be an explicit development configuration.
Read the log
The log shows method, arguments, result/error and time for the latest 100 calls. Exercise loading, readiness, gameplay start/stop, JSON saves, room codes and no-op ads. Saves stay in memory for this mounted test frame and reset on reload. track returns tracked:false with test:true. Room methods do not send actual invites here.
Troubleshooting
- No init event: check the SDK script path, parentOrigin, framing headers and browser console.
- Timeout: verify the origin exactly, await init, and reduce message frequency.
- Save errors: ensure JSON serialization and the request size limit.
- The Inspector does not certify performance, language, content safety or tracker absence; staff still review.