search

OfficeDev / teams-toolkit

Developer tools for building Teams apps
Other
453 stars 184 forks source link

teamsApp/extendToM365 failed with BadRequest: No elements found in the manifest #12407

Open lolocoder3 opened 3 days ago

lolocoder3 commented 3 days ago

Describe the bug Create Teams app by clicking Provision in "Lifecycle" section, I meet error in VS code console below:

Summary: (×) Error: Lifecycle stage provision failed. (√) Done: teamsApp/create was executed successfully. (√) Done: Teams app with id 0c2a3cf1-dca4-4488-8889-92756c6f96c5 already exists, skipped creating a new Teams app. (√) Done: teamsApp/zipAppPackage was executed successfully. (√) Done: teamsApp/update was executed successfully. (√) Done: Teams app 0c2a3cf1-dca4-4488-8889-92756c6f96c5 updated successfully (×) Error: teamsApp/extendToM365 failed. (×) Error: Request failed with status code 400 (tracingId: xxxxxxxx) BadRequest: No elements found in the manifest.

To Reproduce Steps to reproduce the behavior:

  1. Clone this MS teams sample https://github.com/OfficeDev/Copilot-for-M365-Samples/tree/main/samples/cext-geolocator-game
  2. Follow the readme and do the steps one by one
  3. After do this step Create Teams app by clicking Provision in "Lifecycle" section., there is error in console.

Expected behavior The "Geo Locator Game with copilot" should be started with no error by this tenant.

Screenshots If applicable, add screenshots to help explain your problem.

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

CLI Information (please complete the following information):

Additional context log into Teams Toolkit using another tenant, there is no error here.

microsoft-github-policy-service[bot] commented 3 days ago

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.

lolocoder3 commented 3 days ago

I log into Teams Toolkit using another tenant, this sample is started with no error.

lolocoder3 commented 3 days ago

I see there is a similar issue https://github.com/OfficeDev/teams-toolkit/issues/12346, so the root cause is Declarative Copilot is in private preview, right?

lijie-lee commented 2 days ago

Hi @lolocoder3. Thanks for reaching out. I'll check this issue and share why it occur then.