Troubleshooting
1. Bot returns 'You are not authorized to access this Bot. Please contact administrator.'
-
Please verify account you are using in Microsoft Teams is of same tenant.
-
Check whether tenant ID mentioned in application settings section of configuration menu for bot app service matches Microsoft Teams account tenant. Ref: https://docs.microsoft.com/en-us/azure/app-service/configure-common
1. Error when attempting to reuse a Microsoft Azure Active Directory application ID for the bot registration
Bot is not valid. Errors: MsaAppId is already in use.
- Creating the resource of type Microsoft.BotService/botServices failed with status "BadRequest"
This happens when the Microsoft Azure application ID entered during the setup of the deployment has already been used and registered for a bot.
Fix
Either register a new Microsoft Azure Active Directory application or delete the bot registration that is currently using the attempted Microsoft Azure application ID.
1. Client app packages restoration failure for first build
Once repository is cloned and you try to build the solution in Visual Studio, build fails due to multiple NPM packages fails to install.
Fix
If you have cloned using Visual Studio, please retry building solution after closing and re-opening the Visual Studio.
If you still get errors, navigate to 'ClientApp' folder in project directory using file explorer. Open command prompt at this location and type 'npm install'. This will install app the packages for client app. Once it is done, try rebuild solution from Visual Studio.
Didn't find your problem here?
Please, report the issue [here](https://github.com/OfficeDev/microsoft-teams-apps-openbadges