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

[lolocoder3]

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):

• OS: Macos 15.0
• Version 5.9.2024091206 (pre-release)

CLI Information (please complete the following information):

• OS: [e.g. iOS8.1]
• Version [e.g. 22]

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

[microsoft-github-policy-service]

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]

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

[lolocoder3]

I see there is a similar issue #12346, so the root cause is Declarative Copilot is in private preview, right?

[lijie-lee]

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