Is this working stable currently?

[fabulias]

Hi,
I'm creating a bot for Microsoft teams, I have created a bot in https://dev.botframework.com/bots/new, I have my APP_ID and my APP_PASSWORD (the last created in Secret and Keys page).

When I try to run an example of msbotbuilder-go\samples\echobot and try to test the bot from testing page

I obtained an error in ngrok and my service.

ngrok

HTTP Requests                                                                                                           -------------                                                                                                                                                                                                                                   POST /api/messages             400 Bad Request 

example

PS C:\Users\fabulias\go\src\github.com\infracloudio\msbotbuilder-go\samples\echobot> go run .\main.go
Starting server on port:3978...
Failed to process request Failed to create Activity context.: Activity type conversationUpdate not supported yet
Failed to process request Failed to send response.: HTTP error 401: invalid response.

I'm working on Windows 10 Pro edition.

Please, I arrived here because I thought that this is a client for Microsoft bots apps, help me a few.

[PrasadG193]

Hey @fabulias,
Have you set APP_ID and APP_PASSWORD creds in env vars? The SDKs are still in development. We don't support all Activity types yet. That's why you see logs like Activity type * not supported yet. Echo example should work once you set creds.

[fabulias]

Yeah, I have my envs vars OK, but the activity type that I tried is from the test from page from Microsoft, what kind of activities are you supporting?

[bmorton]

I was having the same problem and then was able to get some debug output that was throwing this:

AADSTS700016: Application with identifier 'xxx-xxx-xxx' was not found in the directory 'botframework.com'. This can happen if the application has not been installed by the administrator of the tenant or consented to by any user in the tenant. You may have sent your authentication request to the wrong tenant.

I was able to fix this by toggling the setting on my app to allow this directory. I pulled up my app settings on Azure, went to the "Authentication" tab and changed "Accounts in this organizational directory only" to "Accounts in any organizational directory" and everything's working for me now.

It looked like if the call to get a token fails, the next request will be attempted with no bearer token and that's why I was seeing the 401.

[PrasadG193]

@fabulias as mentioned by @bmorton, you need to choose "Accounts in any organizational directory" account type while registration.