Upload failed due to an invalid BotId in your manifest.

[christophemacabiau]

Describe the bug Impossible to launch the app

To Reproduce The application is a tab/bot app created with teams toolkit. The manifest is correctly validated by developer portal.

Screenshots

VS Code Extension Information (please complete the following information):

• OS: linux
• Version 4.2.4

[ghost]

Thank you for contacting us! Any issue or feedback from you is quite important to us. We will do our best to fully respond to your issue as soon as possible. Sometimes additional investigations may be needed, we will usually get back to you within 2 days by adding comments to this issue. Please stay tuned.

[christophemacabiau]

maybe related to #7608

[nliu-ms]

Hey @christophemacabiau , from the screenshot you cannot launch the Teams app for dev env right? Does your local debug Teams app work?

7608 is concerning launch Teams app for local debug / F5 experience. So it might be different.

[christophemacabiau]

Yes, the local debug teams app works.

[msmarkglad]

I am getting the same error, just published now and that worked, but I can't open the bot in Teams.

[nliu-ms]

Thanks @christophemacabiau , @msmarkglad . Can you please provide following information:

1) Did you successfully launch this app before and it failed suddenly? Or you can never do it. 2) Can you please check if the Teams channel is correctly configured in Azure bot? Cause this error message usually comes from missing/wrong Teams channel configuration.

3) Can you please provide reproducible steps? Or your other Teams bot app works, this is the only one failing?

[christophemacabiau]

Hi @nliu-ms,

Thank you for your answer.

1. It worked at the beggining,
2. I don't know why but everytime I click on Channels/Microsoft teams, I have to agree the terms of service. Could it be the problem?

When I click on "Open in teams", it seems to work

3. How can I provide you the steps to reproduce? Do you need an access to the app?

[msmarkglad]

I have never been able to launch it. I got the error the first time I tried. Here's the steps:

[cid:dda4a0fc-7d7d-40c3-9eed-22630a86fa47]

[cid:a5ae3999-d51c-4086-a21d-70dd2256f2de]

[cid:918b07d9-e4a8-4d29-90de-bfe888f8c998]

I'm doing all this in the PVA app in teams, so I'm not actually going into Azure bot. I'm pretty new at this, so if I need to go into Azure bot to look, if you can point me to how, I can see what's there.

Thanks! Mark

---

From: Ning Liu @.> Sent: Wednesday, April 5, 2023 7:29 PM To: OfficeDev/TeamsFx @.> Cc: Mark Gladding @.>; Mention @.> Subject: Re: [OfficeDev/TeamsFx] Upload failed due to an invalid BotId in your manifest. (Issue #8261)

Thanks @christophemacabiauhttps://github.com/christophemacabiau , @msmarkgladhttps://github.com/msmarkglad . Can you please provide following information:

1. Did you successfully launch this app before and it failed suddenly? Or you can never do it.

2. Can you please check if the Teams channel is correctly configured in Azure bot? Cause this error message usually comes from missing/wrong Teams channel configuration. [image]https://user-images.githubusercontent.com/71362691/230254366-f1a95e80-7554-4351-9afc-6dc956c5cbf8.png

3. Can you launch other Teams bot app?

— Reply to this email directly, view it on GitHubhttps://github.com/OfficeDev/TeamsFx/issues/8261#issuecomment-1498405434, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A67GVRLXJSUIXT4HAEISDI3W7YS7BANCNFSM6AAAAAAWRDGAZ4. You are receiving this because you were mentioned.Message ID: @.***>

[nliu-ms]

Thanks @msmarkglad , sorry I cannot see the screenshots in your comments. Can you please post the steps again? [cid:dda4a0fc-7d7d-40c3-9eed-22630a86fa47]

[cid:a5ae3999-d51c-4086-a21d-70dd2256f2de]

[cid:918b07d9-e4a8-4d29-90de-bfe888f8c998]

As you're using PVA app to create the bot, then how do you use Teams Toolkit with it? Did you put that bot id into a project generated by Teams Toolkit? Thanks!

[nliu-ms]

Thanks @christophemacabiau , from the screenshots there are 3 issues in "Microsoft Teams" channel, it might be the root cause. Can you find out the exact issues and fix them to make the Teams channel healthy? Then try to launch the Teams app again to see if it works. "agree the terms of service" is no the problem.

For the workaround I'm thinking if you can create a new Azure bot. Below are the steps: 1) Create another environment 2) Provision that environment 3) Launch the new Teams app.

[christophemacabiau]

Hi @nliu-ms,

Thank you for your workaround, it worked starting from a fresh environment!

However now I have another problem: when I try to send it a notification, the bot has no installations, no members... Can you give me some hint?

[nliu-ms]

@christophemacabiau Great to hear it works!

Hey @IvanJobs , do you know the possible reasons for Christopher's issue:

Hi @nliu-ms,

Thank you for your workaround, it worked starting from a fresh environment!

However now I have another problem: when I try to send it a notification, the bot has no installations, no members... Can you give me some hint?

[ghost]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate.

[yukun-dong]

Hi @nliu-ms,

Thank you for your workaround, it worked starting from a fresh environment!

However now I have another problem: when I try to send it a notification, the bot has no installations, no members... Can you give me some hint?

Hi @christophemacabiau, could you please provide which template you are using? Is it a notification bot? That may help identify the issue, thanks.

[christophemacabiau]

Hi @yukun-dong, Thank you for your answer. I started with a tab application created by teams toolkit, and I further added the bot feature. It was never possible to make it work.

[yukun-dong]

Hi @christophemacabiau,

Sorry I didn't make my question clear, so let me clarify.

Did you select this "Notification bot"(below picture) when adding the bot feature into your tab project? I see you are using bot's installations and bot members so it should be a notification bot, but I just want to double confirm. Thanks.

[christophemacabiau]

Hi @yukun-dong yes you are right: a notification bot

[swatDong]

@christophemacabiau you mentioned that you created a tab first, then added the notification bot, right? If so, it's probably due to the same cause as this issue.

In general, it may be caused by authentication is enabled on Azure App Service or Azure Function, and the workaround is to disable Authentication settings. As described in here as well.

[swatDong]

Pinned the workaround for quick reference (https://github.com/OfficeDev/TeamsFx/issues/8527).

[hemxnt-saini]

Hi guys, I'm still facing this issue, I have created a simple bot, provision and deploy it with teamsfx commands, it passes all the validations checks and when I try to upload the appPackage on teams, it throws me this error: 'Upload failed due to an invalid BotId in your manifest' continuously.

@christophemacabiau

[VKZycus]

Hi Team, I am also facing issue from last two days.While running the bot locally we are getting

"Upload failed due to an invalid BotId in your manifest." Botid is present on developer portal also password is correct.

[adashen]

Please refer to the pinned the workaround for quick reference (https://github.com/OfficeDev/TeamsFx/issues/8527).

[pm7y]

This is happening again randomly today to an app that was already working and now it gives "Upload failed due to an invalid BotId in your manifest".

To isolate my app from the problem, I created a brand new Teams Echo Bot app using the Visual Studio template and followed the instructions and also got "Upload failed due to an invalid BotId in your manifest".

Really need this resolved ASAP.

Have started a new issue here #11146

[sarhaang]

Yep same, i have a simple chatbot running, had to reset it today and it no longer works.

• The new teams client just fails with Uncaught (in promise) SyntaxError: "[object Object]" is not valid JSON and the old teams client returns Upload failed due to an invalid BotId in your manifest.
• The manifest is correctly validated by developer portal.
• it was working just fine as of 3pm EST on March 20th.

Appreciate any help and thanks in advance for fixing this!

[nliu-ms]

This issue has been mitigated and tracked by https://github.com/OfficeDev/TeamsFx/issues/11146, close this one.