Microsoft JSON fails validation in prepare dependencies step

[bzuidgeest]

Describe the bug
I added the teams toolkit to visual studio. Created a new project for a message extension. Got a the repair data template. When I do the prepare dependencies step I get an error:
"name": "ManifestValidationFailed",
"message": "Manifest Validation is unsuccessful! Unable to get schema from https://developer.microsoft.com/json-schemas/teams/vDevPreview/MicrosoftTeams.schema.json, message: Invalid regular expression: /^(?!.[\r\n\f\b\v\a\t])[\S]\.xll$/: Invalid escape",

To Reproduce
Steps to reproduce the behavior:

• start a new message extension project. Right click teams app and go to teams tookit -> prepare teams app dependencies --> sign in if not and otherwise follow instructions.

Expected behavior
No errors as it's the default template from microsoft.

Screenshots
No screenshot but here is the output from the TEams toolkit

Executing provision

Lifecycle stage: provision(7 step(s) in total). The following actions will be executed:
(1/7) Action teamsApp/create: create Teams app.
(2/7) Action script
(3/7) Action teamsApp/validateManifest: validate Teams app.
(4/7) Action teamsApp/zipAppPackage: build Teams app package.
(5/7) Action teamsApp/validateAppPackage: validate Teams app.
(6/7) Action teamsApp/update: update Teams app.
(7/7) Action teamsApp/extendToM365: acquire Microsoft 365 title with the app package

Executing lifecycle provision
Executing action teamsApp/create in lifecycle provision
Teams app with id e62fea8f-d79f-4320-b306-347cd4b0730e already exists, skipped creating a new Teams app.
Action teamsApp/create in lifecycle provision succeeded with output {"TEAMS_APP_ID":"e62fea8f-d79f-4320-b306-347cd4b0730e","TEAMS_APP_TENANT_ID":"4be23bdd-d690-43b3-a262-068a8ff13c56"}
Executing action script in lifecycle provision
Start to run command: "echo "::set-teamsfx-env OPENAPI_SERVER_URL=https:";" with args: {"shell":"C:\Windows\system32\cmd.exe","cwd":"C:\Users\bzs\source\repos\MyTeamsApp1\MyTeamsApp1\TeamsApp","encoding":"ibm850","env":{"ALLUSERSPROFILE":"C:\ProgramData","API_COPILOT_API_KEY":"false","APPDATA":"C:\Users\bzs\AppData\Roaming","APP_NAME_SUFFIX":"local","CLIENTNAME":"IDEFIXHOME","CommonProgramFiles":"C:\Program Files\Common Files","CommonProgramFiles(x86)":"C:\Program Files (x86)\Common Fi...
[script stdout] "::set-teamsfx-env OPENAPI_SERVER_URL=https:";

script output env variables: {"OPENAPI_SERVER_URL":"https:*"}
Action script in lifecycle provision succeeded with output {"OPENAPI_SERVER_URL":"https://<>.euw.devtunnels.ms"}
Executing action teamsApp/validateManifest in lifecycle provision
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/json-schemas/teams/vDevPreview/MicrosoftTeams.schema.json, message: Invalid regular expression: /^(?!.[\r\n\f\b\v\a\t])[\S].xll$/: Invalid escape. Env output: {"TEAMS_APP_ID":"e62fea8f-d79f-4320-b306-347cd4b0730e","TEAMS_APP_TENANT_ID":"4be23bdd-d690-43b3-a262-068a8ff13c56","OPENAPI_SERVER_URL":"https...
Execution summary:

Summary:
(×) Error: Lifecycle stage provision failed.
(√) Done: teamsApp/create was executed successfully.
(√) Done: Teams app with id e62fea8f-d79f-4320-b306-347cd4b0730e already exists, skipped creating a new Teams app.
(√) Done: script was executed successfully.
(√) Done: Successfully executed command
(×) Error: teamsApp/validateManifest failed.
(×) Error: Manifest Validation is unsuccessful! Unable to get schema from https://developer.microsoft.com/json-schemas/teams/vDevPreview/MicrosoftTeams.schema.json, message: Invalid regular expression: /^(?!.[\r\n\f\b\v\a\t])[\S].xll$/: Invalid escape
(!) Warning: teamsApp/zipAppPackage was not executed.
(!) Warning: teamsApp/validateAppPackage was not executed.
(!) Warning: teamsApp/update was not executed.
(!) Warning: teamsApp/extendToM365 was not executed.

{
"errorType": "UserError",
"source": "AppStudioPlugin",
"name": "ManifestValidationFailed",
"message": "Manifest Validation is unsuccessful! Unable to get schema from https://developer.microsoft.com/json-schemas/teams/vDevPreview/MicrosoftTeams.schema.json, message: Invalid regular expression: /^(?!.[\r\n\f\b\v\a\t])[\S]\.xll$/: Invalid escape",
"stack": "ManifestValidationFailed: Manifest Validation is unsuccessful! Unable to get schema from https://developer.microsoft.com/json-schemas/teams/vDevPreview/MicrosoftTeams.schema.json, message: Invalid regular expression: /^(?!.[\r\n\f\b\v\a\t])[\S]\.xll$/: Invalid escape\n at AppStudioResultFactory.UserError (C:\snapshot\server\lib\index.js)\n at ValidateManifestDriver.validate (C:\snapshot\server\lib\index.js)\n at process.processTicksAndRejections (node:internal/process...
"innerError": null,
"userData": null,
"timestamp": "2025-03-13T14:22:47.643Z",
"displayMessage": "Manifest Validation is unsuccessful! Unable to get schema from https://developer.microsoft.com/json-schemas/teams/vDevPreview/MicrosoftTeams.schema.json, message: Invalid regular expression: /^(?!.[\r\n\f\b\v\a\t])[\S]\.xll$/: Invalid escape",
"helpLink": "https://aka.ms/teamsfx/whyneedprovision",
"issueLink": null
}

Using:
Microsoft Visual Studio Enterprise 2022 (64-bit) - Current
Version 17.13.2

Hope somebody here knows why this happens.

When I click the Json link in the browser it loads perfectly fine in a browser.

[teams-toolkit-assistant]

👋 Hi @bzuidgeest,

Thank you for reporting this issue! We want to let you know that:

⏱️ Our team will personally review your issue
🎯 You can expect a response within 2 business days

✨ This is an AI-generated initial response
🤖 AI-Generated Preliminary Analysis:

It looks like the issue you're encountering is due to a problem with the Teams manifest schema found at https://developer.microsoft.com/json-schemas/teams/vDevPreview/MicrosoftTeams.schema.json. Here are some steps and workarounds based on the gathered resources:

Summary of Issues:

• ManifestValidationFailed: "Invalid escape" error occurred when trying to fetch the schema.
• Cause: Regular expression in the schema causing validation issues.

Temporary Workarounds and Guidance:

1. Use a Stable Schema Version:

Instead of using the vDevPreview schema, you might want to switch to the latest stable version of the Teams manifest schema. Update your manifest.json to refer to a stable schema version, such as 1.13 or 1.16:

{
  "$schema": "https://developer.microsoft.com/json-schemas/teams/v1.16/MicrosoftTeams.schema.json",
  "manifestVersion": "1.16"
}

This will help avoid potential issues with the developer preview schema.

2. Manual Manifest Validation:

As a workaround, you can try validating the manifest manually by temporarily removing or safely commenting out specific problematic sections in your manifest file.

Updating the Manifest Using Teams Toolkit:

If you haven't already, you can use the Teams Toolkit to update and validate your app manifest:

1. Open the command palette in Visual Studio (Ctrl+Shift+P).
2. Run the Teams: Upgrade Teams manifest command and select your app manifest file. This will automatically update the schema references to a stable version.

Potential Fix with set-teamsfx-env:

There could be environmental issues causing the error. Ensure that your environment settings are appropriately set within Visual Studio.

Common Issues and Solutions:

1. Additional Properties Issue:
   Ensure that your manifest.json does not contain additional properties not defined by the schema version. Check the latest manifest schema for allowable properties.

2. Validate and Package App Manually:

   • You can manually validate your manifest and package it using the Teams Developer Portal to avoid the command execution issues temporarily.

Resources:

• Teams manifest schema
• Extend a Teams personal tab across Microsoft 365
• Public developer preview app manifest

Applying these measures should help you bypass the validation issues. If the problem persists, please reach out again, and we could further investigate specific cases or errors.

---

Note: This is an automated first response generated by AI. A human team member will review your issue and provide a more detailed response soon. We appreciate your patience!

[bzuidgeest]

I tried the bots suggestion. Though I would expect a microsoft template to be correct as is.
I then get all kinds of new errors in the validation itself. I check to see if the teams toolkit had a newer version in VS. But no updates,

Start Teams Toolkit pre-debug task...
Executing provision

Lifecycle stage: provision(7 step(s) in total). The following actions will be executed:
(1/7) Action teamsApp/create: create Teams app.
(2/7) Action script
(3/7) Action teamsApp/validateManifest: validate Teams app.
(4/7) Action teamsApp/zipAppPackage: build Teams app package.
(5/7) Action teamsApp/validateAppPackage: validate Teams app.
(6/7) Action teamsApp/update: update Teams app.
(7/7) Action teamsApp/extendToM365: acquire Microsoft 365 title with the app package

Executing lifecycle provision
Executing action teamsApp/create in lifecycle provision
Teams app with id e62fea8f-d79f-4320-b306-347cd4b0730e already exists, skipped creating a new Teams app.
Action teamsApp/create in lifecycle provision succeeded with output {"TEAMS_APP_ID":"e62fea8f-d79f-4320-b306-347cd4b0730e","TEAMS_APP_TENANT_ID":"4be23bdd-d690-43b3-a262-068a8ff13c56"}
Executing action script in lifecycle provision
Start to run command: "echo "::set-teamsfx-env OPENAPI_SERVER_URL=https:";" with args: {"shell":"C:\Windows\system32\cmd.exe","cwd":"C:\Users\bzs\source\repos\MyTeamsApp1\MyTeamsApp1\TeamsApp","encoding":"ibm850","env":{"ALLUSERSPROFILE":"C:\ProgramData","API_COPILOT_API_KEY":"false","APPDATA":"C:\Users\bzs\AppData\Roaming","APP_NAME_SUFFIX":"local","CLIENTNAME":"IDEFIXHOME","CommonProgramFiles":"C:\Program Files\Common Files","CommonProgramFiles(x86)":"C:\Program Files (x86)\Common Fi...
[script stdout] "::set-teamsfx-env OPENAPI_SERVER_URL=https:";

script output env variables: {"OPENAPI_SERVER_URL":"https:***"}
Action script in lifecycle provision succeeded with output {"OPENAPI_SERVER_URL":"https://<>.euw.devtunnels.ms"}
Executing action teamsApp/validateManifest in lifecycle provision

Teams Toolkit has checked manifest(s) with the corresponding schema:

Summary:
4 failed.
You can check and update your Teams manifest at ./appPackage/manifest.json.
(×) Error: /composeExtensions/0 must have required property 'botId'. Details: {"missingProperty":"botId"}
(×) Error: /composeExtensions/0 must NOT have additional properties. Details: {"additionalProperty":"composeExtensionType"}
(×) Error: /composeExtensions/0 must NOT have additional properties. Details: {"additionalProperty":"apiSpecificationFile"}
(×) Error: /composeExtensions/0/commands/0 must NOT have additional properties. Details: {"additionalProperty":"apiResponseRenderingTemplateFile"}

Failed to Execute lifecycle provision due to failed action: teamsApp/validateManifest. ManifestValidationFailed:Teams Toolkit has completed checking your app package against validation rules. 4 failed.. Env output: {"TEAMS_APP_ID":"e62fea8f-d79f-4320-b306-347cd4b0730e","TEAMS_APP_TENANT_ID":"4be23bdd-d690-43b3-a262-068a8ff13c56","OPENAPI_SERVER_URL":"https://<>.euw.devtunnels.ms"}
Execution summary:

Summary:
(×) Error: Lifecycle stage provision failed.
(√) Done: teamsApp/create was executed successfully.
(√) Done: Teams app with id e62fea8f-d79f-4320-b306-347cd4b0730e already exists, skipped creating a new Teams app.
(√) Done: script was executed successfully.
(√) Done: Successfully executed command
(×) Error: teamsApp/validateManifest failed.
(×) Error: Teams Toolkit has completed checking your app package against validation rules. 4 failed.
(!) Warning: teamsApp/zipAppPackage was not executed.
(!) Warning: teamsApp/validateAppPackage was not executed.
(!) Warning: teamsApp/update was not executed.
(!) Warning: teamsApp/extendToM365 was not executed.

{
"errorType": "UserError",
"source": "AppStudioPlugin",
"name": "ManifestValidationFailed",
"message": "Teams Toolkit has completed checking your app package against validation rules. 4 failed.",
"stack": "ManifestValidationFailed: Teams Toolkit has completed checking your app package against validation rules. 4 failed.\n at AppStudioResultFactory.UserError (C:\snapshot\server\lib\index.js)\n at ValidateManifestDriver.validate (C:\snapshot\server\lib\index.js)\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n at async ValidateManifestDriver. (C:\snapshot\server\lib\index.js)\n at async ValidateManifestDriver.execute (C:\snapsho...
"innerError": null,
"userData": null,
"timestamp": "2025-03-13T14:36:02.319Z",
"displayMessage": "Teams Toolkit has completed checking your app package against validation rules. 4 failed. Check Output panel for details.",
"helpLink": null,
"issueLink": null
}

The readme says nothing about all this... Where are the correct instructions?

[HuihuiWu-Microsoft]

Hi @bzuidgeest Could you let me know your selected template name? I tried your steps with following template on VS17.13.2 and wasn't able to reproduce

[microsoft-github-policy-service]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 7 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate.

[microsoft-github-policy-service]

Due to lack of details for further investigation, we will archive the issue for now. In case you still have following-up questions on this issue, please always feel free to reopen the issue by clicking ‘reopen issue’ button below the comment box. We will get back to you as soon as possible.