-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Intent Recognition sample app is invalid #369
Comments
Thanks for the feedback, we will investigate, @ActiveNick FYI |
Did this ever got resolved? |
@LessThan12Parsecs I just tried it again-- same error. |
Yeah, that's a pity, I tried exporting a random app from LUIS to see if there was some field missing but wasn't able to find any changes to make it work. |
@thegoldenmule We are very sorry that it didn't work yet. We figured out that the json file is currently not compatible with the latest LUIS schema as they have done some modification. We have fixed the issue. Please use the attached json file. We will publish this in the official release once we do the next release. I am closing the issue for the time being. If you face any issue, please let us know . |
should update it now, almost gave up before finding this |
The next official release, 1.10, is out tomorrow: 3/2/2020. |
haha figures |
Describe the bug
When attempting to run SCENE 2 from the https://github.com/Azure-Samples/cognitive-services-speech-sdk/tree/master/samples/unity/speechrecognizer guide, the json model provided is invalid. When you attempt to import the json file (
LUIS-App-Export-Unity-FunWithShapes.json
) you get the error:BadArgument: Character indicies 17,20 do not correspond to the start and end of a token.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The app should be created successfully.
Version of the Cognitive Services Speech SDK
N/A.
Platform, Operating System, and Programming Language
Chrome.
Additional context
The json file is valid JSON, but the website gives the error:
BadArgument: Character indicies 17,20 do not correspond to the start and end of a token.
.The text was updated successfully, but these errors were encountered: