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

PoshBot not receiving webhook information in Teams console #245

Open
ClarkRSD opened this issue Jun 2, 2022 · 8 comments
Open

PoshBot not receiving webhook information in Teams console #245

ClarkRSD opened this issue Jun 2, 2022 · 8 comments

Comments

@ClarkRSD
Copy link

ClarkRSD commented Jun 2, 2022

When setting up PoshBot with Teams, I receive no errors and the function app in Azure is reporting messages being received, but they're not showing up in the logs in PoshBot.

Expected Behavior

Based off the Discord bot, it should show the message being received in the pipeline.

Current Behavior

It doesn't show anything in the logs and the bot does not reply to any messages. I am seeing messages being received within the webhook as well as in the service queue, but messages are not being sent out.
image

Possible Solution

The only thing I can think of is to not migrate the bot from the Bot Framework over to Azure or this error within the Web Chat channel has something to do with it, but it pops up on creation of the bot every single time. I don't know why I would be getting an error 400 on something that's just being made with defaults. This is the most likely culprit, but I don't know how to fix this or why it would even be happening.
image

Steps to Reproduce (for bugs)

Follow the instructions to setup a Teams backend here. There is some minor differences now in Azure. I made sure to setup the bot as a multi-tenant as I saw that that was a problem in issue #186.

Context

I setup the Discord backend as a test to verify that the bot was working correctly in my environment and it works as expected. The only deviance I made from the instructions within the documentation is that I migrated the bot from the Bot Framework over to Azure.

image

Here is my resource group
image

Here is my message policy key information for receiving to show that it's matching
image

Here's the information for my bot's password
image

And the information for my app registration ID
image

I added some extra permissions to the app registration just in case that was the issue for Teams specifically, but I don't know that that made a difference.

The bot has the Teams channel
image

App information in Teams
image

Your Environment

  • Module version used: 0.14.0
  • Operating System and PowerShell version: Windows 10 Enterprise. Powershell version 7.2.4
@ClarkRSD ClarkRSD changed the title PoshBot not receiving webhook information in console PoshBot not receiving webhook information in Teams console Jun 2, 2022
@ClarkRSD
Copy link
Author

ClarkRSD commented Jun 4, 2022

Small update. I'm noticing that it seems to be an issue with PoshBot as far as I can tell, because viewing the messages in the service bus explorer, I'm getting back the message I'm sending on Teams.

image
image

@ClarkRSD
Copy link
Author

ClarkRSD commented Jun 4, 2022

I'm not seeing any errors in the log file.

It ends at the starting of the backend processes.
image

@devblackops
Copy link
Member

Possible related to #244

@ClarkRSD
Copy link
Author

ClarkRSD commented Jun 9, 2022

Okay I will wait for the fix to be added to main and test it out then. Thank you!

@mengdahuang
Copy link

Possible related to #244

Hi, Sir

Could you help to tell us how to resolve this issue?
I've read #244 But still do not know how to fix it base on current version of PoshBot.
Thanks a lot !

@mengdahuang
Copy link

@ClarkRSD Hi, have you resolve this issue? i got the same issue like your post. hope you can get me some reference if you resolved this. thanks a lot

@ClarkRSD
Copy link
Author

@mengdahuang no I was unable to fix the problem. I tried to use PR #248 but that did not fix it.

@mengdahuang
Copy link

@ClarkRSD Me too....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants