Skip to content
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

TeamsInfo.getTeamChannels returning 403 Service Error Unknown #4647

Closed
carolinedpena opened this issue Apr 16, 2024 · 2 comments
Closed

TeamsInfo.getTeamChannels returning 403 Service Error Unknown #4647

carolinedpena opened this issue Apr 16, 2024 · 2 comments
Labels
bug Indicates an unexpected problem or an unintended behavior. needs-triage The issue has just been created and it has not been reviewed by the team.

Comments

@carolinedpena
Copy link

Versions

Encountered with botbuilder v4.16.0 and the latest botbuilder v4.22.2. Encountered in Node v18 and v20.

Describe the bug

Using the TeamsInfo.getTeamsChannels is returning a 403 Unknown error. Tested with passing both the optional teams id param and without:

try { teamChannels = await TeamsInfo.getTeamChannels(context, context.activity.channelData.teamsTeamId); } catch(err) { console.log('error in getting teams channels') console.log(err) }

try { teamChannels = await TeamsInfo.getTeamChannels(context); } catch(err) { console.log('error in getting teams channels') console.log(err) }

Both return the following:
2024-04-16T13:57:39.763599244Z error in getting teams channels
2024-04-16T13:57:39.766050531Z RestError: Unknown
2024-04-16T13:57:39.766074232Z {
2024-04-16T13:57:39.766133434Z "name": "RestError",
2024-04-16T13:57:39.766140634Z "code": "ServiceError",
2024-04-16T13:57:39.766145834Z "statusCode": 403,
2024-04-16T13:57:39.766150635Z "request": {
2024-04-16T13:57:39.766155435Z "streamResponseStatusCodes": {},
2024-04-16T13:57:39.766160335Z "url": "https://smba.trafficmanager.net/amer/v3/teams/{TEAMS_ID_HERE}/conversations",
2024-04-16T13:57:39.766165535Z "method": "GET",
2024-04-16T13:57:39.766176136Z "headers": {
2024-04-16T13:57:39.766181036Z "_headersMap": {
2024-04-16T13:57:39.766185736Z "authorization": "REDACTED",
2024-04-16T13:57:39.766190536Z "user-agent": "core-http/3.0.4 Node/v14.21.3 OS/(x64-Linux-5.15.145.2-1.cm2)"
2024-04-16T13:57:39.766195536Z }
2024-04-16T13:57:39.766199736Z },
2024-04-16T13:57:39.766204237Z "withCredentials": false,
2024-04-16T13:57:39.766209037Z "timeout": 0,
2024-04-16T13:57:39.766229037Z "requestId": "fc38fe88-27cf-446f-83c4-14159da00556"
2024-04-16T13:57:39.766234038Z },
2024-04-16T13:57:39.766238538Z "details": {
2024-04-16T13:57:39.766243138Z "error": {
2024-04-16T13:57:39.766247638Z "code": "ServiceError",
2024-04-16T13:57:39.766252338Z "message": "Unknown"
2024-04-16T13:57:39.766257038Z }
2024-04-16T13:57:39.766261639Z },
2024-04-16T13:57:39.766266139Z "message": "Unknown"
2024-04-16T13:57:39.766270739Z }

Expected behavior

Nothing was changed about our code, error began yesterday afternoon. We'd expect a list of a team's channels to be returned.

@carolinedpena carolinedpena added bug Indicates an unexpected problem or an unintended behavior. needs-triage The issue has just been created and it has not been reviewed by the team. labels Apr 16, 2024
@stevkan
Copy link
Collaborator

stevkan commented Apr 19, 2024

@carolinedpena - Is this still an issue or did it resolve itself, by chance? Nothing has changed with BotFramework. I suspect that there was a change in the Teams client.

Out of curiosity, are you using new or old (classic) Teams?
What is the version of Teams you are using?
If you switch from one to the other, does the issue persist?

@stevkan
Copy link
Collaborator

stevkan commented Apr 30, 2024

Closing due to inactivity.

@stevkan stevkan closed this as completed Apr 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Indicates an unexpected problem or an unintended behavior. needs-triage The issue has just been created and it has not been reviewed by the team.
Projects
None yet
Development

No branches or pull requests

2 participants