Hello @ Meghana-MSFT,

Thank you for your reply. We tried the solution you sent us but it didn't work.

We have seen that the bot is already in developer preview mode and RSC authorization is enabled. We will double-check it and keep you informed of the results.

Thank you,
Tanguy

Hello @Meghana-MSFT ,

So as we said we were already switched on developer preview mode on Microsoft Teams. We checked that the Team we are running the apps on has the RSC permissions enabled.

We know that the problem is coming from the fact that we are using Virtual Studio Code with the Teams Toolkit to start the application because it overrides our manifest file during the compilation of the application and remove for our example the "ChannelMessage.Read.Group" permission.

We also tried one more time to create a new app with the Azure portal and to upload directly the app package with the manifest of this new application but it's still not working and the bot is only responding when mentionned.

So, did you try starting the application from the Teams Toolkit in Virtual Studio Code to see if you have the same problem as us ? Maybe could we have a call with someone of Microsoft to check with him that we did everything fine and how to fix this problem that is very annoying for the development of our project.

Thanks,
Tanguy

Hello @Meghana-MSFT,

We start the application from Teams Toolkit in Virtual Studio Code. Maybe we could have a call with someone from Microsoft to check with them that we did everything right and how to fix this problem which is very annoying for the development of our project.

Thanks,
Tanguy

Sorry I mean Visual Studio Code *

Hello,

I tried to run the project without the help of Teams Toolkit but with the help of TeamsFx CLI but it did not work either.

I started to try your solution with your sample but it is not possible to run it for a simple reason that the messages-with-RSC folder does not exist. There is also an error in the documentation.
"In a console, navigate to samples/bot-message-with-RSC/nodejs" and next line "cd samples/tab-stage-view/nodejs"

Also for the creation of a resource with Azure Portal, it says "2. In the search box enter "bot". And in the drop-down list, select Bot Channels Registration." but "Bot Channels Registration" does not appear in the list and does not exist.

I also tried another solution which was to follow this documentation: (https://github.com/OfficeDev/TeamsFx/wiki/Enable-Preview-Features-in-Teams-Toolkit). But it did not work for the TeamsFx CLI part. For the VS Code Teams Toolkit part, the documentation is not up to date because "Insider Preview" does not exist in the extension section.

Wishing you a nice day.
Tanguy

Hello,

I'm making this post to get back to you on the subject and to see if you have any new information. If you do, will it be possible to be informed?

Thanks,
Tanguy

@Meghana-MSFT - Hello, I tried the stample again using "$ npm run server", I followed all the steps exactly as mentioned in the document too. But at the end, when I try to upload the manifest.zip, I got this error. And "aka.ms/teamsdocs" does not exist.

@Meghana-MSFT - I did it and the errors come from the icons :

InvalidColorIconHeightAndWidth Color Icon is not as per the required dimension.
InvalidOutlineIconHeightAndWidth Small icon should be 32x32 with only white and transparentInvalidOutlineIconTransparency Outline icon is not transparent.It's Alpha,R,G,B: 45,73,90,107

I didn't change these icons, so they are in the wrong format in the template.

So I tried to put icons in the right format instead of the basic ones and the app studio validates the manifest without any error.

However, the "Something went wrong" problem is still present when I want to add a custom application to a team.

@Meghana-MSFT - Here is the manifest. I put 'x' in ngrok's URL so as not to share it.

160646-manifest.txt