Deck Docs

Troubleshooting

Common Feedback SDK integration issues and how to fix them.

Troubleshooting

SymptomWhat to check
Submissions never appear in DeckWidget ID and publishable key belong to the same org. Confirm the key is pk_… and not revoked.
401 / unauthorizedMistyped key, revoked key, or secret dk_… used instead of publishable pk_….
Client error user.id is requiredPass a non-empty user.id on DeckProvider / low-level options.
Client error widgetId is requiredPass a non-empty widgetId on the component or submit call.
No insights after submitMessage was empty (raw only); still waiting for the next weekday batch window; or org is out of synthesis credits.
Feedback missing from Project tabWidget was not linked to that Project at submit time. Relinking only affects future submissions.
Wrong product surface in DeckConfirm widgetId and optional context on the component.
Dialog styles look unthemedEnsure headless is not set if you want built-in styles; or set colorScheme / theme on the provider.
useDeckFeedback / useSubmitFeedback throwsComponent is outside DeckProvider.
Server import fails / React pulled into NodeImport from @deck-io/feedback/server, not the default entry.
Server submit missing URL metadataExpected — pass meta.url / meta.userAgent explicitly; the server client does not read window.
Package not found on installInstall @deck-io/feedback (not @deck/feedback). Ensure version ≥ 0.2.0 for the /server entry.

Debug checklist

  1. Log SDK_VERSION from the package to confirm the installed version (expect 0.2.0 or later for server support)
  2. Confirm the env var is present where you submit: client bundle for React, server env for /server
  3. Submit once, then open Manage → Widgets → [widget] for a raw row
  4. If free-text is present, wait for the next weekday batch (or check credits)
  5. If Project routing matters, verify the widget’s Project link before testing

Package