Welcome,
Can you show your code in the callback which is getting the score value?
BTW, just for some background, the score doesn’t have a huge amount of utility in an application because it is extremely dependent on the recording environment. I have historically made it available because it is part of the returned information with a hypothesis and it seemed unhelpful to omit it from OpenEars when it was available, but I don’t advise relying on it for anything except relative values within a single app usage session (meaning, you can use score within one session to see if something is well-recognized compared to another utterance within the same session, but shouldn’t use constants as a universal cutoff that means “good recognition” or “bad recognition” because you’ll get surprises when the user interacts with the app from a greater mic distance or in a noisier environment than you tested in.