-
Notifications
You must be signed in to change notification settings - Fork 204
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
MS Teams Toolkit Error #12131
Comments
hi @MoonAlzoubi26z , the reason is that your network cannot access the json schema. Could you check if you can open this link ( https://developer.microsoft.com/en-us/json-schemas/teams/v1.16/MicrosoftTeams.schema.json) in your browser? |
hi @MoonAlzoubi26z , it looks like you do have access to this json schema. Could you retry in the Teams Toolkit? It might be due to a network spike before. |
hi @MoonAlzoubi26z, for further investigation, could you tell me which template your are using or share your project codes? |
it looks like your |
It turned out the company's VPN is causing this issue, i was able to debug and run without any issues after a disconnected the vpn. Thank you all |
I'm starting new on the Teams Toolkit i followed the steps on the toolkit plugin page and i'm getting an error in this step:
Run Local Preview.
and this is the output:
[Error] - Failed to Execute lifecycle provision due to failed action: teamsApp/validateManifest. ManifestValidationFailed:Manifest Validation is unsuccessful! Unable to get schema from https://developer.microsoft.com/en-us/json-schemas/teams/v1.16/MicrosoftTeams.schema.json, message: Failed to get manifest at url https://developer.microsoft.com/en-us/json-schemas/teams/v1.16/MicrosoftTeams.schema.json due to: request to https://developer.microsoft.com/en-us/json-schemas/teams/v1.16/MicrosoftTeams.schema.json failed, reason: connect ETIMEDOUT 23.33.241.144:443. Env output: {"TEAMS_APP_ID":"74028ab9-f369-42ff-ab93-57a1a0e008fb","TEAMS_APP_TENANT_ID":"59f4d0e9-1e36-4c52-94c1-84176ffa43e5","TAB_DOMAIN":"localhost:53000","TAB_ENDPOINT":"https://localhost:53000"}
[2024-07-31T16:16:31.655Z] [Info] - Execution summary:
Summary:
(×) Error: Lifecycle stage provision failed.
(√) Done: teamsApp/create was executed successfully.
(√) Done: Teams app with id 74028ab9-f369-42ff-ab93-57a1a0e008fb already exists, skipped creating a new Teams app.
(√) Done: script was executed successfully.
(√) Done: Successfully executed command echo "::set-teamsfx-env TAB_DOMAIN=localhost:53000"; echo "::set-teamsfx-env TAB_ENDPOINT=https://localhost:53000";
(×) Error: teamsApp/validateManifest failed.
(×) Error: Manifest Validation is unsuccessful! Unable to get schema from https://developer.microsoft.com/en-us/json-schemas/teams/v1.16/MicrosoftTeams.schema.json, message: Failed to get manifest at url https://developer.microsoft.com/en-us/json-schemas/teams/v1.16/MicrosoftTeams.schema.json due to: request to https://developer.microsoft.com/en-us/json-schemas/teams/v1.16/MicrosoftTeams.schema.json failed, reason: connect ETIMEDOUT 23.33.241.144:443
(!) Warning: teamsApp/zipAppPackage was not executed.
(!) Warning: teamsApp/validateAppPackage was not executed.
(!) Warning: teamsApp/update was not executed.
(!) Warning: teamsApp/extendToM365 was not executed.
The text was updated successfully, but these errors were encountered: