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

teamsApp/extendToM365 failed #12773

Open
AKSHILMY opened this issue Nov 24, 2024 · 6 comments
Open

teamsApp/extendToM365 failed #12773

AKSHILMY opened this issue Nov 24, 2024 · 6 comments
Assignees
Labels
TA:Compute Team Area: Compute

Comments

@AKSHILMY
Copy link

AKSHILMY commented Nov 24, 2024

Describe the bug
Upon clicking provision, the teamsApp/extendToM365 failed occurs. Trying after sometime does not show any error. This error keeps on occurring. I need to resolve this so that I could test easily.
Even if comment out the teamsApp/extendToM365 in the teamsapp.yml , the agent is not displayed in Teams

To Reproduce
Steps to reproduce the behavior:

  1. Provisioning via VsCode Extension

Screenshots
image

VS Code Extension Information (please complete the following information):

  • OS: Ubuntu 22.04
  • Version : v5.10.1
@microsoft-github-policy-service microsoft-github-policy-service bot added the needs attention This issue needs the attention of a contributor. label Nov 24, 2024
@adashen adashen added investigating TA:Infra Team Area: Infra labels Nov 25, 2024
@sayali-MSFT
Copy link

Hello @AKSHILMY, Thank you for your inquiry about your Teams app development issue!

To assist you better, could you please provide the following details?

Code Snippets: Relevant code snippets that illustrate the issue.
Manifest Package: If applicable, please share the manifest package for your app.

This information will help us better understand the situation and provide a more accurate response.

@kuojianlu
Copy link
Contributor

@AKSHILMY Which template do you use? Or please share the manifest content.

@AKSHILMY
Copy link
Author

AKSHILMY commented Dec 4, 2024

@AKSHILMY Which template do you use? Or please share the manifest content.

{
    "$schema": "https://developer.microsoft.com/json-schemas/teams/v1.19/MicrosoftTeams.schema.json",
    "manifestVersion": "1.19",
    "version": "1.0.9",
    "id": "${{TEAMS_APP_ID}}",
    "developer": {
        "name": "Teams App, Inc.",
        "websiteUrl": "https://www.example.com",
        "privacyUrl": "https://www.example.com/privacy",
        "termsOfUseUrl": "https://www.example.com/termofuse"
    },
    "icons": {
        "color": "color.png",
        "outline": "outline.png"
    },
    "name": {
        "short": "Dev${{APP_NAME_SUFFIX}}",
        "full": "Full name for agent-dev"
    },
    "description": {
        "short": "Short description for agent-dev",
        "full": "Full description for agent-dev"
    },
    "accentColor": "#FFFFFF",
    "composeExtensions": [],
    "permissions": [
        "identity",
        "messageTeamMembers"
    ],
    "copilotAgents": {
        "declarativeAgents": [
            {
                "id": "declarativeAgent",
                "file": "declarativeAgent.json"
            }
        ]
    },
    "validDomains": []
}

@huimiu
Copy link
Member

huimiu commented Dec 4, 2024

Hi @AKSHILMY, the main reason for this error is probably that the content in the declarative agent JSON file doesn't comply with AI standards. You can try tweaking the content in the declarative agent JSON file and then provision again to see if it passes the RAI check.

By the way, teamsApp/extendToM365 is a necessary step to display your agent in Teams.

@huimiu huimiu removed needs attention This issue needs the attention of a contributor. investigating labels Dec 4, 2024
@kuojianlu kuojianlu added TA:Compute Team Area: Compute and removed TA:Infra Team Area: Infra labels Dec 4, 2024
@kuojianlu kuojianlu removed their assignment Dec 4, 2024
@AKSHILMY
Copy link
Author

AKSHILMY commented Dec 4, 2024

Hi @AKSHILMY, the main reason for this error is probably that the content in the declarative agent JSON file doesn't comply with AI standards. You can try tweaking the content in the declarative agent JSON file and then provision again to see if it passes the RAI check.

By the way, teamsApp/extendToM365 is a necessary step to display your agent in Teams.

Sometimes, the same state of the agent codebase yields successful provision after keeping it for a few hours without any changes.

That's something unusual. I am currently testing it like that with gap intervals of around few hours between provisions.
Any such limit for no of provisions per hour?

@microsoft-github-policy-service microsoft-github-policy-service bot added the needs attention This issue needs the attention of a contributor. label Dec 4, 2024
@huimiu
Copy link
Member

huimiu commented Dec 4, 2024

That's quite unusual. As far as I know, there is no such limit, but the RAI check is currently unpredictable, and it's difficult to debug this error. We're investigating some ways to improve the development experience on this.

For the time being, I would like to suggest updating the agent content or trying with gap intervals as you mentioned.

@huimiu huimiu removed the needs attention This issue needs the attention of a contributor. label Dec 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
TA:Compute Team Area: Compute
Projects
None yet
Development

No branches or pull requests

5 participants