QnA configuration - "Object reference not set to an instance of an object."

[WTobor]

Version

branch master, commit 326026e

Browser

What browser are you using?

• Chrome
• Safari
• Firefox
• Edge

OS

What operating system are you using?

• macOS
• Windows
• Ubuntu

To Reproduce

Steps to reproduce the behavior:

1. Create bot app from template "Luis & QnA"
2. Create QnA knowledgebase
3. In Settings add valid
4. Update flow to use only Qna on start:
   
5. Open bot in Emulator

Current behaviour

Expected behavior

There is no error

Additional information

There is no error after steps:

• copy qna node from BotProject/ComposerDialog/settings/appsettings.json to BotProject/appsettings.json
• manually add missing endpointkey node in qna node

[hibrenda]

@WTobor Composer settings will be set into BotProject/ComposerDialog/settings/appsettings.json but not BotProject/appsettings.json . The latter one is for deployment usage.

1. Confirm you have input everything under "qna" setting ?
   

2. Confirm the appsetting file has been correctly set
   With this fix: QnA Maker EndpointKey is null Issue #1571 integration, "endpointkey" should be persist into disk which located in BotProject/ComposerDialog/settings/appsettings.json . If you have settings updates successfully, files will be updated as well. Please confirm the file content. If you input something wrong in settings, editor will show error with red frame so the updated contents will not be saved and you might hit errors.

[WTobor]

Yes, I can confirm.

[hibrenda]

@WTobor Updated comment to check apsettings file (see above) , by the way for your dialog step in welcome, the QnA step won't be invoked in above flow. We'd better to have tirgger intent with utterance to invoke QnA.

[VanyLaw]

Hi @WTobor I can't reproduce too. If you set those value correctly into settings, It should be persist to disk (ComposerDialog/settings/appsettings.json), and no need to manually add endpoingkey to file. Could you try again in the latest master branch?

FYI. this is the file I get in my localhost, which included endpointkey already.
.

And the property name in settings should be the same as the value you filled in the form.