[Bug]: Trey Research Fails to build
Closed this issue · 10 comments
Sample
cext-trey-research
Description
This issue is for cext-trey-research.
I'm getting an error saying "No elements found in the manifest" when I attempt to run in Teams Toolkit via VS Code.
Steps to reproduce
Teams Toolkit, F5
Expected results
Build/Run
Actual results
[2024-06-12T15:59:37.049Z] [Error] - Unable to execute action teamsApp/extendToM365. Error message: undefined
[2024-06-12T15:59:37.050Z] [Error] - Failed to Execute lifecycle provision due to failed action: teamsApp/extendToM365. PackageServiceError:Request failed with status code 400 (tracingId: 00-202220fb1c1b4c58c329a17b843985de-5158ccbe6feb0035-00) BadRequest: No elements found in the manifest. . Env output: {"TEAMS_APP_ID":"3634dc55-26b5-4831-a771-44ef80fc0ecf","TEAMS_APP_TENANT_ID":"8dd03a3c-4763-4bf4-a497-68fa057490a2","FUNC_NAME":"me","FUNC_ENDPOINT":"http://localhost:7071","TEAMS_APP_UPDATE_TIME":"2024-06-12T15:59:35.9865047+00:00"}
Additional Info
No response
EDIT: @garrytrinder updated Sample section content
What version of Teams Toolkit are you using @charleslucot13 ?
Can you try with the latest released version please (v5.8.1)?
I also experience this problem with the latest version of Teams Toolkit. If I run "Debug in Copilot (Chrome)" from launch.json, the same thing occurs. Oddly, if I run "Preview in Copilot (Chrome)", I get a teams window and can seemingly interact with the sample as expected. Trying npm run dev also fails but due to missing STORAGE_ACCOUNT_CONNECTION_STRING.
The readme does not provide any info about how to set this value. Overall I find the sample a bit difficult to understand. Is there any documentation for example, for the trey-plugin.json?
Our interest in this sample is because we intended to create a Copilot plugin that interacts with an Open API definition, the trey-plugin.json appears to be the relevant file for this functionality but the difficulty getting the sample functioning and lack of documentation for the plugin file is leaving me uncertain how to implement the functionality we need.
What version of Teams Toolkit are you using @charleslucot13 ? Can you try with the latest released version please (v5.8.1)?
Thanks Bob, I'm on the latest version of Teams Toolkit (5.8.1). Any other suggestions are appreciated.
@charleslucot13 @olliejm Declarative Copilots are in private preview, the errors seem consistent with trying to use the sample against a tenant that does not have the functionality deployed. Are you able to confirm if your tenant is enrolled in the private preview?
I work with @olliejm - our tenant is from "Microsoft Copilot Developer Tenant Private Preview Program". Should that tenant be a member of "Declarative Copilots private preview"? If not - how can we join?
Not necessarily, it could be that the tenant has not yet been flighted with the functionality. I recommend that you raise a support ticket via the admin portal and speak to your account manager.
I am having the same problem of no elements found in the manifest using declarative copilot for geolocator . I am using the latest version of teams toolkit v5.8.1.
@IntranetFactory @SidhantAcharya922 this might be an issue with the version of Teams Toolkit CLI that you have installed. Can you install the latest beta npm i -g @microsoft/teamsapp-cli@beta and try again.
@garrytrinder I tried with the latest beta but still I am getting the same error.
I have been able to recreate the error when attempting to deploy the sample to my developer tenant which does not have Copilot enabled. See TTK output below.
This error appears to be a tenant configuration issue, not an issue with the sample or TTK. If you have Copilot enabled and still see this error, then it's most likely that the tenant has not been flighted with declarative copilot functionality. In either case, you should raise a support ticket via the Microsoft 365 Admin Center.
[2024-08-29T09:58:52.332Z] [Info] - Current VS Code locale is: en
[2024-08-29T09:58:53.261Z] [Info] - Teams Toolkit extension is now active!
[2024-08-29T10:00:32.499Z] [Info] - Running 'Validate prerequisites' Visual Studio Code task.
(Total: 3 Steps) Teams Toolkit is checking the required prerequisites.
(1/3) Checking Node.js ...
(2/3) Checking Microsoft 365 Account ...
(3/3) Checking ports occupancy ...
Summary:
(√) Done: Node.js version (v20.16.0) is installed
(√) Done: Microsoft 365 Account (<redacted>@<redacted>.onmicrosoft.com) is logged in and custom app upload permission is enabled
(√) Done: Ports (7071, 9229) are not occupied
Visit https://aka.ms/teamsfx-tasks/check-prerequisites to get more info about 'Validate prerequisites' task.
[2024-08-29T10:00:33.266Z] [Info] - Finished 'Validate prerequisites' Visual Studio Code task in 0.77 seconds.
[2024-08-29T10:00:36.428Z] [Info] - Running Visual Studio Code task: 'Start local tunnel'
(Total: 1 Step) Teams Toolkit is starting local tunneling service to forward public URL to local port. Open the terminal window for details.
(1/1) Starting dev tunnel service ...
[2024-08-29T10:00:38.486Z] [Info] - Created environment file at e:\Copilot-for-M365-Plugins-Samples\samples\cext-trey-research\env\.env.local
Summary:
(√) Done: Forwarding URL https://53mtnrxc-7071.uks1.devtunnels.ms/ to http://localhost:7071 and saved [OPENAPI_SERVER_URL] to e:\Copilot-for-M365-Plugins-Samples\samples\cext-trey-research\env\.env.local.
Visit https://aka.ms/teamsfx-local-tunnel-task to get more info about 'Start local tunnel' task.
[2024-08-29T10:00:38.488Z] [Info] - Started local tunneling service in 2.06 seconds.
[2024-08-29T10:00:38.694Z] [Info] - Executing provision
Lifecycle stage: provision(5 step(s) in total). The following actions will be executed:
(1/5) Action teamsApp/create: create Teams app.
(2/5) Action script
(3/5) Action teamsApp/zipAppPackage: build Teams app package.
(4/5) Action teamsApp/update: update Teams app.
(5/5) Action teamsApp/extendToM365: acquire Microsoft 365 title with the app package
[2024-08-29T10:00:38.695Z] [Info] - Executing lifecycle provision
[2024-08-29T10:00:46.858Z] [Info] - [script stdout] "::<REDACTED:secret> FUNC_NAME=me"; echo "::<REDACTED:secret> <REDACTED:secret>:<REDACTED:secret>:7071";
[2024-08-29T10:00:46.882Z] [Info] - (√)Done: Teams Package e:\Copilot-for-M365-Plugins-Samples\samples\cext-trey-research\appPackage\build\appPackage.local.zip built successfully!
[2024-08-29T10:00:52.418Z] [Error] - Unable to execute action teamsApp/extendToM365. Error message: undefined
[2024-08-29T10:00:52.420Z] [Error] - Failed to Execute lifecycle provision due to failed action: teamsApp/extendToM365. PackageServiceError:Request failed with status code 400 (tracingId: 00-2c696ec2012e3868059bfbeb805822b1-64f7552f5de30e7a-00) BadRequest: No elements found in the manifest. . Env output: {"TEAMS_APP_ID":"f69e8cd5-0a75-4712-aa13-bae189f98de0","TEAMS_APP_TENANT_ID":"bf805346-44e7-43f7-8e60-c5e24aefe49c","FUNC_NAME":"me","FUNC_ENDPOINT":"http://localhost:7071","TEAMS_APP_UPDATE_TIME":"2024-08-29T10:00:49.277225+00:00"}
[2024-08-29T10:00:52.421Z] [Info] - Execution summary:
Summary:
(×) Error: Lifecycle stage provision failed.
(√) Done: teamsApp/create was executed successfully.
(√) Done: Teams app f69e8cd5-0a75-4712-aa13-bae189f98de0 created successfully
(√) Done: script was executed successfully.
(√) Done: Successfully executed command echo "::<REDACTED:secret> FUNC_NAME=me"; echo "::<REDACTED:secret> <REDACTED:secret>:<REDACTED:secret>:7071";
(√) Done: teamsApp/zipAppPackage was executed successfully.
(√) Done: teamsApp/update was executed successfully.
(√) Done: Teams app f69e8cd5-0a75-4712-aa13-bae189f98de0 updated successfully
(×) Error: teamsApp/extendToM365 failed.
(×) Error: Request failed with status code 400 (tracingId: 00-2c696ec2012e3868059bfbeb805822b1-64f7552f5de30e7a-00) BadRequest: No elements found in the manifest.
[2024-08-29T10:00:52.428Z] [Info] - Created environment file (secret) at e:\Copilot-for-M365-Plugins-Samples\samples\cext-trey-research\env\.env.local.user