Bot not working or responding after deployment about microsoft-teams-apps-icebreaker HOT 13 CLOSED

Hello,
Could you please send a screenshot of your manifest file that was used to upload the icebreaker bot to teams? This way we can double check if you have the correct values there, such as the correct bot ID and the correct app domain values. Also check if you have set the app registration to accounts in any organization.

from microsoft-teams-apps-icebreaker.

Hello,
Could you please send a screenshot of your manifest file that was used to upload the icebreaker bot to teams? This way we can double check if you have the correct values there, such as the correct bot ID and the correct app domain values. Also check if you have set the app registration to accounts in any organization.

For sure! Please see below:
{
"$schema": "https://developer.microsoft.com/en-us/json-schemas/teams/v1.3/MicrosoftTeams.schema.json",
"manifestVersion": "1.3",
"version": "1.0.0",
"id": "d55d08d9-bacb-4567-942f-afd85d632dcc",
"packageName": "com.microsoft.teams.icebreaker",
"developer": {
"name": "Starbucks",
"websiteUrl": "https://starbucks.com",
"privacyUrl": "https://starbucks.com/privacy",
"termsOfUseUrl": "https://starbucks.com/cfp&a"
},
"icons": {
"color": "color.png",
"outline": "outline.png"
},
"name": {
"short": "Icebreaker"
},
"description": {
"short": "Icebreaker is a bot that randomly pairs team members up to build team unity.",
"full": "Icebreaker is a cute little bot that randomly pairs team members up every week to help the team build trust and personal connections."
},
"accentColor": "#64A2CC",
"bots": [
{
"botId": "0b5632bd-5906-46da-9886-8836cf534690",
"scopes": [
"personal",
"team"
],
"supportsFiles": false,
"isNotificationOnly": true
}
],
"permissions": [
"identity",
"messageTeamMembers"
],
"validDomains": [
"icebreaker-5cmtqzkx2m3la.azurewebsites.net"
]
}

I checked and it is set to "app registration to accounts in any organization.

Please let me know if you need additional information

from microsoft-teams-apps-icebreaker.

Also just to confirm, make sure that you added the bot only to the team and not to the personal scope in your tenant, as it will automatically send messages to your personal scope during the matching interval.

Check your application insights resource and let me know if you face any error messages there, by accessing application insights -> search -> click here to get started -> select any of the exceptions and custom event details to view any possible errors.

from microsoft-teams-apps-icebreaker.

Hello,

Thank you. This seems to be a recurring error:

from microsoft-teams-apps-icebreaker.

Can you also expand on the exception that you got and attach a screenshot of that as well? We will get more information about what the issue is that way.

from microsoft-teams-apps-icebreaker.

yes of course. Please see below:

from microsoft-teams-apps-icebreaker.

It seems that the app domain is not receiving any messages, it is not available and so that is why it is throwing a 404 error, saying that the app domain is not available. This could be due to an incorrect or failed deployment. If you have a successful deployment and navigate to the app domain, it will throw a message like this:

Which means that the endpoint is available for sending messages. So, can you check whether you have any failed deployments by selecting the link next to deployments in your resource group? If that is the case, the next best step would be to redeploy, but to make sure you fill in the correct values in the custom deployment section.

Ensure that the bot ID matches the application ID from the app registration, and the password matches the bot secret manually created. One deployed, check on the resources created and you should get a message which says the deployment is successful, which means that the app domain has been successfully created.

from microsoft-teams-apps-icebreaker.

It seems that the app domain is not receiving any messages, it is not available and so that is why it is throwing a 404 error, saying that the app domain is not available. This could be due to an incorrect or failed deployment. If you have a successful deployment and navigate to the app domain, it will throw a message like this:

Which means that the endpoint is available for sending messages. So, can you check whether you have any failed deployments by selecting the link next to deployments in your resource group? If that is the case, the next best step would be to redeploy, but to make sure you fill in the correct values in the custom deployment section.

Ensure that the bot ID matches the application ID from the app registration, and the password matches the bot secret manually created. One deployed, check on the resources created and you should get a message which says the deployment is successful, which means that the app domain has been successfully created.

Thank you! I'll try to redeploy. Do I need to cancel the original deployment somehow?

from microsoft-teams-apps-icebreaker.

So in case of a redeployment, it is recommended that you delete the resources you created in the resource group and start again using the same resource group and also create a new app registration with a new app ID and bot secret.

from microsoft-teams-apps-icebreaker.

I redeployed and this time around, it pops up a message for take a tour but nothing else after that. Even going directly to the app there's no chatbox

I went to application insights and saw the below, Im not sure what they mean:

from microsoft-teams-apps-icebreaker.

Nevermind! It actually worked when I brought my teammates in and they were able to see the Pause Matches option.

from microsoft-teams-apps-icebreaker.

Thank you for submitting this issue, as we work to ensure consistent responses with items logged in our issues list, we are working to address these items that did not get responses. Please let us know if you are still facing this issue and require assistance and we will be happy to discuss. If no further action is needed at moment and no response is received, we will close out the issue in 3 business days. You may also always open a new issue or respond here if something does come back up. Thank you!

from microsoft-teams-apps-icebreaker.

i do not know why my deployent refuses to pair up

can someone help?

from microsoft-teams-apps-icebreaker.