-
Notifications
You must be signed in to change notification settings - Fork 81
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.
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
[Bug]: Trey Research Fails to build #132
Comments
What version of Teams Toolkit are you using @charleslucot13 ? |
I also experience this problem with the latest version of Teams Toolkit. If I run "Debug in Copilot (Chrome)" from 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 Our interest in this sample is because we intended to create a Copilot plugin that interacts with an Open API definition, the |
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 |
@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.
|
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
The text was updated successfully, but these errors were encountered: