microsoftgraph / microsoftgraph/microsoft-graph-comms-samples

teams-recording-bot won't start running | _botService.Initialize ();

Open
#397 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
253
Forks
275
Avg merge
1d 5h
Merged PRs (30d)
1

Description

the query is directed to the project - https://github.com/microsoftgraph/microsoft-graph-comms-samples/tree/master/Samples/V1.0Samples/AksSamples/teams-recording-bot

I try to run this example, I have everything I need for it and I followed the instructions, though. some points come to me tossed. Does anyone have experience with this and did you manage to run it into a running shoe?

My current result is that after setting all points 1-7 and running the program in Visual Studio, it crashes due to an error on /RecordingBot.Services/ServiceSetup/AppHost.cs on the line _botService.Initialize (); , where I could not solve this problem.

I should have all the parameters from Azure, NgRok and Certificate set correctly.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in RecordingBot.Services/ServiceSetup/AppHost.cs at the _botService.Initialize (); call and capture the complete exception and stack trace. Check the Azure, NgRok, and certificate parameters described in setup steps 1–7; done means the teams-recording-bot example starts successfully in Visual Studio.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, csharp
Domain
backend, cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.