Skip to content
This repository has been archived by the owner on Jun 30, 2022. It is now read-only.
This repository has been archived by the owner on Jun 30, 2022. It is now read-only.

System.NullReferenceException: 'Unable to locate SkillConversationIdFactoryBase in HostContext' #3743

Closed

Description

What project is affected?

Microsoft.Bot.Builder.Dialogs.Adaptive

What language is this in?

C#

What happens?

After following the instructions on this post: experimental-add-composer I get the error System.NullReferenceException: 'Unable to locate SkillConversationIdFactoryBase in HostContext' when using an trigger intent which calls a skill as part of its conversation flow.

What are the steps to reproduce this issue?

I have created a git repo to demonstrate the issue as there are many steps to reproduce.
git repo with project that demonstrates the issue

To recreate the issue:
Prerequisites
Install Bot Emulator: Emulator project link

Open the solution file
Integrate-Composer-Dialog-Using-Skill.sln

Put a breakpoint on line 72 of DefaultAdapter.cs - this is where the error can be seen

Start debugging the project
Open Bot Emulator
Connect to the bot: http://localhost:3978/api/messages
Type "Greeting"
Bot should respond with "Hello, I have recognized that you said greeting"
Type "Skill"
The breakpoint on line 72 of DefaultAdapter.cs should trigger giving details of the error

Error & stack trace can be found here: Stack Trace

What were you expecting to happen?

The skill would be called successfully

Can you share any logs, error output, etc.?

error stack trace.txt
The process I followed to setup the project to produce the error.
Detailed Instructions.docx

Any screenshots or additional context?

The goal of setting this up is to create a workflow which allows composer created dialogs to be integrated into a bot skill project.
This will allow for customizations to the bot behavior such as, logging errors & conversation to a custom database hosted on premise.
We will also be hosting the bot on premise so this structure will also allow for our CI/CD pipeline to deploy the main bot (created through the composer) & skills (created in code) to be deployed together & settings to be adjusted as the Bot moves up environments.

Thank you for your time in reviewing this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    Needs TriageNeeds to be triaged for assignmentType: BugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions