Troubleshooting Launch Issues

Most launch failures come down to four things: readiness, identifiers, auth, or using the wrong public surface for the job.

Widget not ready

If open(), prefetch(), or prerender() fails early, make sure:

• createClient({ apiKey }) ran before you called the command
• client.load() has run if you enabled disableAutoLoad
• the API key belongs to the environment you are testing

Flow requires identity

If the flow expects identity, call identify() before opening it. This is one of the most common reasons a flow works locally and fails in a production-shaped environment.

Wrong or stale identifiers

Check that the same app owns all of these:

• the public API key
• the flow or survey ID
• the published flow version you submit against

If you use advanced handles with prerender() and custom containers, keep the same client instance and flow handle for the full open and close lifecycle.

JWT failures

When App Security is enabled, the usual causes are:

• wrong issuer
• wrong JWKS URL
• token minted for the wrong audience

The expected audience is https://api.getuserfeedback.com.

If the failure only appears during direct API submission, continue to Submit a Response.