Skip to main content
Participant
December 4, 2025
Question

Meta Voice SDK does not display intents in Understanding Viewer

Hey, I am on a test project in Unity 6.1 with Meta Voice SDK and Wit.ai integration.

Sound detection, Wit configuration and Wit training are all set up and work fine, but the Understanding Viewer does not list the (well) trained intents (shows 0 with confidence=0), but lists the trained entities correcly with confidence=1. 

Without proven link to intents, the response matcher does not work reliably: when adding it from the Viewer's listing by clicking on the intents, the response matcher shows an empty field for the intent.

I do not use dictation, conduit is checked and the general procedure for voice control works (best with response events in App Voice Experience). I also retrained the intents several times with at least 5 variations for each utterance. But the intents never show up in Voice Understanding. Any idea? 

5 replies

joccoAuthor
Participant
December 4, 2025

Edit: I am actually on Unity 6.2 with Meta Voice SDK v81

Meta Employee
December 5, 2025

Hi there jocco!

I understand you're having trouble with the Voice SDK, and I understand how that could be frustrating. Since you're a START partner, I would suggest you reach out to the START support team as they're best suited to help with your issue.

-G

joccoAuthor
Participant
December 5, 2025

Hi there, thanks for your hint. Your link needs me to connect my account with START which does not seem to work (Salesforce error message). I could enter via Discord link and sent a request to the support. Thank you

 

Meta Employee
December 8, 2025

Hey jocco, thanks for letting me know.

If that link is not working for you, I'd suggest you reach out to our developer support portal. You can do that by visiting (https://developers.meta.com/horizon/support), select "Submit a request", and then select "New" to create a new case. 

Hope this helps, and let me know if you have any questions!

-G

New Participant
January 11, 2026

This sounds like a Viewer sync or cache issue rather than training itself, some users have seen intents fail to populate until the app voice experience is re-initialized or the Wit app is re-linked, oddly similar to how edge-case workflows like pet shipping to germany require very specific configuration paths to surface correctly.