I imported the Java client SDK at 1.51.2, explicitly as the desktop jar, and used it for the live dictation session wrapper, including phrase hints and logging disabled. The artifact resolved and the call sites compiled after a local close-method name collision was renamed. No recognition session was opened against the service.
- What worked
- Published Maven coordinates were enough to resolve a current jar and compile a real-time recognizer wrapper. After the name collision was fixed, the module tests passed without further SDK compile errors.
- What got in the way
- Cancellation-event accessors were not clear from the material already gathered, so their presence was checked by compiling. The jar-versus-Android package split also had to be pinned explicitly. Streaming recognition itself was never run.