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.

Sign up for GitHub

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

Jump to bottom

Upload failed due to an invalid BotId in your manifest. #8261

Closed
christophemacabiau opened this issue Apr 3, 2023 · 25 comments
Closed

Upload failed due to an invalid BotId in your manifest. #8261

christophemacabiau opened this issue Apr 3, 2023 · 25 comments
Assignees
@swatDong @yukun-dong @nliu-ms
Labels
investigating needs attention This issue needs the attention of a contributor. TA:E2E Team Area: E2E

Comments

@christophemacabiau
Copy link

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
image

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

  • OS: linux
  • Version 4.2.4
@ghost
Copy link

ghost commented Apr 3, 2023

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
Copy link
Author

maybe related to #7608

@ghost ghost added the needs attention This issue needs the attention of a contributor. label Apr 3, 2023
@adashen adashen added investigating TA:E2E Team Area: E2E labels Apr 4, 2023
@nliu-ms
Copy link
Contributor

nliu-ms commented Apr 4, 2023

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
Copy link
Author

christophemacabiau commented Apr 4, 2023 •
edited

Yes, the local debug teams app works.

@msmarkglad
Copy link

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

@nliu-ms
Copy link
Contributor

nliu-ms commented Apr 6, 2023 •
edited

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.
    image

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

@adashen adashen added needs more info Need user to provide more info and removed needs attention This issue needs the attention of a contributor. labels Apr 6, 2023
@christophemacabiau
Copy link
Author

christophemacabiau commented Apr 6, 2023 •
edited

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?
    image

image
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?

@ghost ghost added needs attention This issue needs the attention of a contributor. and removed needs more info Need user to provide more info labels Apr 6, 2023
@msmarkglad
Copy link

msmarkglad commented Apr 6, 2023 via email

@nliu-ms
Copy link
Contributor

nliu-ms commented Apr 7, 2023

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
Copy link
Contributor

nliu-ms commented Apr 7, 2023

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
    image
  2. Provision that environment
  3. Launch the new Teams app.

@christophemacabiau
Copy link
Author

christophemacabiau commented Apr 7, 2023 •
edited

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
Copy link
Contributor

nliu-ms commented Apr 10, 2023

@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?

@adashen adashen added needs more info Need user to provide more info and removed needs attention This issue needs the attention of a contributor. labels Apr 11, 2023
@ghost ghost added the no recent activity The issue labeled needs more info gets no reply from issue owner in time label Apr 18, 2023
@ghost
Copy link

ghost commented Apr 18, 2023

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.

@nliu-ms nliu-ms assigned yukun-dong and unassigned IvanJobs Apr 19, 2023
@ghost ghost removed the no recent activity The issue labeled needs more info gets no reply from issue owner in time label Apr 19, 2023
@yukun-dong
Copy link
Contributor

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
Copy link
Author

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.

@ghost ghost added needs attention This issue needs the attention of a contributor. and removed needs more info Need user to provide more info labels Apr 19, 2023
@yukun-dong
Copy link
Contributor

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.
image

@christophemacabiau
Copy link
Author

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

@swatDong
Copy link
Contributor

@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.

@adashen adashen removed the needs attention This issue needs the attention of a contributor. label Apr 24, 2023
@swatDong
Copy link
Contributor

Pinned the workaround for quick reference (#8527).

@hemxnt-saini
Copy link

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

@ghost ghost added the needs attention This issue needs the attention of a contributor. label Jun 27, 2023
@VKZycus
Copy link

VKZycus commented Jun 27, 2023

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

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

@adashen
Copy link
Contributor

adashen commented Jul 3, 2023

Please refer to the pinned the workaround for quick reference (#8527).

@adashen adashen removed the needs attention This issue needs the attention of a contributor. label Jul 3, 2023
@pm7y
Copy link

pm7y commented Mar 21, 2024 •
edited

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

@microsoft-github-policy-service microsoft-github-policy-service bot added the needs attention This issue needs the attention of a contributor. label Mar 21, 2024
@sarhaang
Copy link

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
Copy link
Contributor

nliu-ms commented Mar 25, 2024

This issue has been mitigated and tracked by #11146, close this one.

@nliu-ms nliu-ms closed this as completed Mar 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@swatDong swatDong

@yukun-dong yukun-dong

@nliu-ms nliu-ms

Labels
investigating needs attention This issue needs the attention of a contributor. TA:E2E Team Area: E2E
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests