False warning when validation teams app with localization

[nbelyh]

Describe the bug

If you validate a Teams manifest file apk validate that has a localization file, it gives a warning:

The schema version of the localization file

(!) Warning: The schema version of the localization file for sv-se is different from the schema version of the app manifest file. 
Localization schema version found: v1.19. App manifest schema version provided: 1.19

To Reproduce
Steps to reproduce the behavior:

1. Run apk validate against the attached package (our production package).
2. A warning is displayed that version 1.19 is not the same as v1.19

visplan-manifest-prod.zip

Expected behavior
There should be no warning.

Screenshots

CLI Information (please complete the following information):

• OS: Windows 11
• Version 1.0.1

Additional context
The original validator (website) was also giving this warning, despite the scemas are correct.
There is a missing "v" in the validator code that must be added. The correct manifest schemas are:

Manifest:
https://developer.microsoft.com/en-us/json-schemas/teams/v1.19/MicrosoftTeams.schema.json

Localization:
https://developer.microsoft.com/en-us/json-schemas/teams/v1.19/MicrosoftTeams.Localization.schema.json

[m365-agent-toolkit-assistant]

👋 Hi @nbelyh,

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:

Known Issue Identified

Issue:

There is a known issue with schema version validation between the Teams app manifest and localization files.

Example Case:

• Error message: Warning: The schema version of the localization file for sv-se is different from the schema version of the app manifest file. Localization schema version found: v1.19. App manifest schema version provided: 1.19

Similar Known Issue:

1. Mismatch between schema URL and manifest version:

• GitHub Issue chore: update adaptivecard pkg version to 1.0.0-rc #4970: Includes discrepancies in schema versions impacting validation in Developer Portal.

Proposed Solutions:

1. Check File Schema Version:
   Ensure both your manifest and localization files use the correct schema URL:

   • Manifest:

     "$schema": "https://developer.microsoft.com/en-us/json-schemas/teams/v1.19/MicrosoftTeams.schema.json"
     

   • Localization:

     "$schema": "https://developer.microsoft.com/en-us/json-schemas/teams/v1.19/MicrosoftTeams.Localization.schema.json"
     

2. Ensure Matching Versions:
   The schema versions (v1.19 and 1.19) are technically the same. However, ensure consistency in your file references.

Additional Steps:

1. Environment Details:

   • Development environment (VS Code/VS/CLI)
   • Teams Toolkit version

2. Reproduction Steps:
   Provide detailed steps to reproduce the behavior.

3. Error Logs:
   Include error logs and relevant screenshots.

For exact debugging, provide the specific details if the issue persists.

✨We'd love your feedback! Please take a moment to fill out our survey.

---

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!

[HuihuiWu-Microsoft]

Thanks @nbelyh for reporting this to us. When you validate in Agents Toolkit CLI, it actually calls upstream API to validate app package. That's why the result is consistent between ATK and 'original validator(website)'. I'll raise ticket to related team and let you know once it's fixed.