Operation returned an invalid status code 'NotFound' when calling TeamsOperations.FetchChannelListWithHttpMessagesAsync

What project is affected?

latest BF

What language is this in?

C#

What happens?

Operation returned an invalid status code ‘NotFound’ at Microsoft.Bot.Connector.Teams.TeamsOperations.GetResponseAsync[T](String url, Boolean shouldTrace, String invocationId, Dictionary2 customHeaders, CancellationToken cancellationToken) at Microsoft.Bot.Connector.Teams.TeamsOperations.FetchChannelListWithHttpMessagesAsync(String teamId, Dictionary2 customHeaders, CancellationToken cancellationToken) at Microsoft.Bot.Connector.Teams.TeamsOperationsExtensions.FetchChannelListAsync(ITeamsOperations operations, String teamId, CancellationToken cancellationToken) at GetChannelList(CancellationToken cancellationToken) in C:.…\TeamsContext\TeamsContext.ChannelExtensions.cs:line 46

What are the steps to reproduce this issue?

Called the above function to retrieve some teams info and hit this error.

What were you expecting to happen?

Success.

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

Above. Also This is the post from previous UpdateActivity that was successful (from ngrok) POST /api/skills/v3/conversations/19:[e-mail]2;messageid=1611212147390-l_Icm-msteams-skillconvo/activities/1611212147390
200 OK This corresponds to the failure (above) GET /api/skills/v3/teams/19:[e-mail]2/conversations
404 Not Found

Any screenshots or additional context?

[Virtual-Josh]

@ipraveenMS as far as I’m aware the TeamsInfo class has never worked with skills in any version of the SDK. If you have an example of a version of the SDK where it does work can you tell us what version? The reason it doesn’t work is due to the delegated turn context not having the required pieces to use TeamsInfo. This means there aren’t any simple workarounds currently available.

If you’re determined to do a work around I have one idea which seems reasonable, but I have not tested to confirm it works. You could setup some logic so the skill calls back to the parent when it wants to use the methods in TeamsInfo and have the parent forward the data back. If you wanted to follow this path then the parent would need to be installed in Teams so it would have access to data.

As for timelines that’s a good question. We are currently wrapping up our current cycle and will start planning work for our next cycle imminently. It’s possible that this gets picked up in our next cycle, but I’m not in a position to tell you it will definitely be in the next release.

[ipraveenMS]

Even var details = await TeamsInfo.GetTeamDetailsAsync(turnContext, turnContext.Activity.TeamsGetTeamInfo().Id, cancellationToken); hit the same NOT found error. With same REST path in ngrok