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

Add Web Chat FAQ #1961

Open
37 tasks
corinagum opened this issue May 3, 2019 · 2 comments
Open
37 tasks

Add Web Chat FAQ #1961

corinagum opened this issue May 3, 2019 · 2 comments
Labels
area-docs Documentation required area-mockbot Issues that need to be addressed on MockBot backlog Out of scope for the current iteration but it will be evaluated in a future release. feature-request Azure report label front-burner team-agility Reduce friction in Web Chat's development process

Comments

@corinagum
Copy link
Contributor

corinagum commented May 3, 2019

FAQs

Web Chat secret / token management

The following link provides several examples on token management: Web Chat secret management

Receive "TypeError: Super expression must either be null or a function" on < 4.6.0

In short, speech is being enabled in an environment that denied access to microphone.

For details, please read #2855.

  • Web Chat < 4.6.0: The error message was incorrectly showing "Super expression must either be null or a function". Instead, it should say, speech recognition/synthesis cannot be enabled because microphone access is denied.

  • Web Chat >= 4.6.0: We have fixed the error message.

The following environment does not support microphone access and speech should not be enabled.

  • Mobile iOS apps
  • Hosting in <IFRAME> on Chrome/Edge/Firefox without Feature Policy set
  • Hosting on insecure HTTP
  • IE11

Receive E401 when running npm install botframework-webchat on or after 4.9.2

On >= 4.9.2, running npm install botframework-webchat results in E401.

This happen if you are using a custom registry which require authentication. And you authenticate using a per-project .npmrc file.

Background

npx will pick up the registry on ./.npmrc, but it can't pick up the token there. It can only pick up the token at ~/.npmrc.

Workaround

Instead of authenticating on ./.npmrc file (local project .npmrc), please authenticate against ~/.npmrc (per-user .npmrc file).

The actual location of ~/.npmrc can be found by running npm config get userconfig.

Related issues

There is an issue filed to Azure DevOps about inconsistent handling of .npmrc file, microsoft/azure-pipelines-tasks#13265, it usually lead to this issue.

Update activity renderer

The custom activity renderer will pass multiple arguments. When sending the arguments downstream, please make sure all the arguments are sent by using rest operators. For example:

const activityMiddleware = () => next => (...args) => {
  return next(...args);
};

Questions need to formalize into a section

Do we want to provide a frequently asked questions document on this repo? Team, please add to the list below of topics that would be added to the FAQ

@cwhitten
Copy link
Member

Great idea! As part of the larger Mockbot cleanup effort (Mockbotv2) we can create a QnAMaker KB holding these FAQ's.

@corinagum corinagum added the 4.6 label Jul 31, 2019
@corinagum corinagum self-assigned this Jul 31, 2019
@corinagum corinagum moved this from Unassigned to To do in R8 Prioritization Jul 31, 2019
@corinagum corinagum removed the Triage-E label Aug 5, 2019
@cwhitten cwhitten removed the 4.6 label Sep 25, 2019
@cwhitten cwhitten removed this from To do in R8 Prioritization Sep 25, 2019
@corinagum corinagum added the backlog Out of scope for the current iteration but it will be evaluated in a future release. label Sep 25, 2019
@compulim compulim pinned this issue Oct 31, 2019
@corinagum corinagum added this to Investigate in R8 Prioritization Nov 6, 2019
@corinagum corinagum removed this from Investigate in R8 Prioritization Nov 7, 2019
@compulim compulim unpinned this issue Nov 15, 2019
@corinagum corinagum pinned this issue Nov 15, 2019
@corinagum corinagum added the area-mockbot Issues that need to be addressed on MockBot label Dec 3, 2019
@corinagum corinagum added the QOL label Dec 17, 2019
@corinagum corinagum added feature-request Azure report label team-agility Reduce friction in Web Chat's development process and removed Enhancement backlog Out of scope for the current iteration but it will be evaluated in a future release. labels Sep 23, 2020
@prakanshurockss
Copy link

can be add a virual keyboard to the bot?

@compulim compulim added the backlog Out of scope for the current iteration but it will be evaluated in a future release. label Oct 5, 2020
@corinagum corinagum added this to the Backlog milestone Oct 28, 2020
@corinagum corinagum removed this from the Backlog milestone Apr 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-docs Documentation required area-mockbot Issues that need to be addressed on MockBot backlog Out of scope for the current iteration but it will be evaluated in a future release. feature-request Azure report label front-burner team-agility Reduce friction in Web Chat's development process
Projects
None yet
Development

No branches or pull requests

4 participants