Skip to content
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

version v1.8 is not supported #13248

Open
ridomin opened this issue Feb 20, 2025 · 6 comments
Open

version v1.8 is not supported #13248

ridomin opened this issue Feb 20, 2025 · 6 comments
Labels
needs attention This issue needs the attention of a contributor.

Comments

@ridomin
Copy link

ridomin commented Feb 20, 2025

Open query-org-user-with-message-extension-sso with VScode

Hit F5

[Error] - code:ConfigManager.InvalidYamlSchemaError, message: Unable to parse yaml file: d:\teams-toolkit-samples\query-org-user-with-message-extension-sso\teamsapp.local.yml. Reason: version v1.8 is not supported. Supported versions: 1.0.0, 1.1.0, v1.2, v1.3, v1.4, v1.5, v1.6, v1.7. Please review the yaml file or upgrade to the latest Teams Toolkit.
 Help link: https://aka.ms/teamsfx-actions/invalid-lifecycle-error

TTK version 5.12.1 on Windows with latest VSCode

Copy link

👋 Hi @ridomin,

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:

The error you are encountering indicates that the teamsapp.local.yml file is using a version that is not supported by your current Teams Toolkit. Specifically, the version v1.8 mentioned in the error is not recognized, and you need to use one of the supported versions: 1.0.0, 1.1.0, v1.2, v1.3, v1.4, v1.5, v1.6, v1.7.

Here are the steps to resolve this issue:

  1. Update the teamsapp.local.yml file:

    • Open the teamsapp.local.yml file in your project directory.
    • Locate the version field at the top of the file.
    • Change the version to one of the supported versions, for example:
      version: v1.7
  2. Ensure you are using the latest Teams Toolkit:

    • Make sure your Teams Toolkit extension in Visual Studio Code is up-to-date. You can check for updates and install the latest version if needed.
    • To update the Teams Toolkit extension, go to the Extensions view in Visual Studio Code, search for "Teams Toolkit", and click on "Update" if an update is available.
  3. Review the YAML file for other potential issues:

By following these steps, you should be able to resolve the version compatibility issue with the teamsapp.local.yml file and run your project successfully.

For further details and support, you can refer to the Teams Toolkit GitHub issue #12286 which discusses similar issues related to YAML schema versions.

If you encounter any additional issues, please provide more details or error messages so that I can assist you further.


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!

@microsoft-github-policy-service microsoft-github-policy-service bot added the needs attention This issue needs the attention of a contributor. label Feb 20, 2025
@ridomin
Copy link
Author

ridomin commented Feb 20, 2025

same error with intelligent-data-chart-generator

@ridomin
Copy link
Author

ridomin commented Feb 20, 2025

same error with graph-connector-bot

Are these samples maintained?

@ridomin ridomin changed the title query-org-user-with-message-extension-sso fails on F5 version v1.8 is not supported Feb 20, 2025
@SLdragon
Copy link
Contributor

@ridomin ,
This error occurs because you're using an outdated TTK version when opening a new project template. Updating your Teams Toolkit to version 5.13.x should resolve the issue.

@Meghana-MSFT
Copy link

@ridomin - Could you please confirm if updating to version 5.13.x solved the issue.

@ridomin
Copy link
Author

ridomin commented Feb 20, 2025

mmhh.. from the changelog seems 5.12.1 is the latest, and I was expecting the extension to autoupdate

Forcing the pre-release version to use the samples in the default branch does not seem right to me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs attention This issue needs the attention of a contributor.
Projects
None yet
Development

No branches or pull requests

3 participants