Teams toolkit Hello World Bot with SSO, show command not working - botframework

I am trying out the Hello World Bot with SSO sample which comes with the Teams toolkit.
"Show" command is not working as expected for me, getting a response as
There is an issue while trying to sign you in and retrieve your profile photo, please type "show" command to login and consent permissions again.
or
"We need to ask for additional permissions. You should only need to do this once for MyApplication" with two buttons "Cancel" and "Continue".
On clicking "Continue" no action is happening.
On debugging found that, tokenResponse.ssoToken is not getting set.
Any pointer on how to overcome it?

Related

How to show popup message in msbot after adding it to a teams channel (nodejs)

I am trying to show a popup message to user asking him to login after adding my bot to teams channel. Like how trello and polly does.Here is the pic of trello how it is asking user to login after adding it to teams channel.
Is there any way that I can achieve something like that?
Any help would be really thankful
If you want to open a popup to allow a user to login you could do that by implementing Authentication for your Bot. If you want to open a popup to show a card/Html page you could try using TaskModule.
This sample maybe helpful, it shows Auth window
https://github.com/microsoft/BotBuilder-Samples/tree/master/samples/javascript_nodejs/52.teams-messaging-extensions-search-auth-config

Intermittent "The API developer key is invalid" error

We have a live application that gives the "The API developer key is invalid" intermittently.
The normal flow:
User clicks "Import from Google Drive"
Gets an OAuth screen
Selects a user (if there are more than one)
Gets prompted with the Google Picker
Picks a file
File gets imported
But for some users, after selecting a user in point 3 (or automatically if there is only one user) the Picker dialog doesn't open, but gets prompted with an "In order to select an item from your online storage, please sign in" message on black background with red Sign in button on it. (see screenshot)
Sign in screen
Then after clicking "Sign in", the user receives the "The API developer key is invalid" error message, and the flow stops. (see screenshot again)
API key error screen
For the majority of the users everything works fine. Seems to be a per user issue, because we have an affected user that has multiple gmail addresses signed in into Chrome, and this issue happens with one email address, but doesn't happen with the other.
Any ideas?
After a long search, I found a workaround. I had to replace the gapi.auth2.init and gapi.auth2. signIn calls with gapi.auth2.authorize and it started to work for those affected users too. Submitted a report to Google about it, but at the time of writing, there was not much reply: https://github.com/google/google-api-javascript-client/issues/613

Unable to connect Web App Bot to Cortana Channel

I'm trying to add the Cortana channel to a bot I've been working on today. However, when the page loads, the entire form is greyed out except for the knowledge.store Register button, and the Cancel button.
I've read elsewhere that people have managed to get past this by clicking really quickly on the Save button that appears briefly as the page loads, but I've had no luck with that. The (very helpful) tech support guy suggests it could be due to special characters or numbers in the bot name, but I have the exact same issue with a bot name that's just lowercase letters.
UPDATE: I can now see my knowledge.store organisations in a dropdown next to the Register button. Clicking the Register button throws a "Failed to create bot module" error. I am able to connect the channel successfully on another bot I made to test the issue.

Creating a chat connector for communicating with the Bot Framework Service

I am trying to implement a bot in my website using the botbuilder framework for node.js. The function builder.ChatConnector() get the parameters appId and appPassword, does any one knows where can i found these appId and appPassword? It isn't clear for me in the microsoft documentation. The function is shown above:
function builder.ChatConnect
BotFramework documentation
You can find this information when you create your bot in Azure Bot Service, or when you proceed to register your bot at the dev portal.
Here's a brief walkthrough for registering through the dev portal with the minimum requirements. You'll need to fill out the name, bot handle and description for the bot as indicated below:
After this, you can scroll down and click on the button that says "Create Microsoft App ID and password".
Once you click on the button you'll be taken to a page with your bot name, your newly-generated App ID, and another button that allows you "Generate a password to continue".
After you click the button a small window will pop up with your password which you need to keep track of as it is only shown once!
NOTE: For developing and testing using the Emulator, you don't need this information just yet. You only need the AppID and password when you are making your bot public facing/deploying it.
You need to register your bot in https://dev.botframework.com/ and there you will get those values. Check this article that explains how to do that.

Adding Facebook Messenger channel trigger a JS bug in the "My Bots" page

I've tried to add a Facebook Messenger channel to one of my bots. I've entered e app/page ID, app secret and page token of my FB app and page (that, BTW, I use in another bot).
Everything checked out: after hitting "Resubmit" in https://facebook.botframework.com/Dev, I got the success message
Credentials have been validated.
However, when clicking on
"I'm done configuring Facebook Messenger"
button and going back to my bot page, everything between the Bot Framework Preview and the 'contact us' footer is gone.
I did some debugging and found that in all.js?v=121 the code should be updated to if (aa && aa.length>0) to account for HtmlLink without <a> tag.
Any ideas if there are workarounds?
Thanks!
We had this problem two days ago, but have since resolved it. If it's not resolved for you, let us know as your scenario might be different.

Resources