OfficeDev / TeamsFx

Developer tools for building Teams apps
Other
427 stars 164 forks source link

bug report: AppStudioPlugin.DeveloperPortalAPIFailed #6978

Closed mizginstlm closed 9 months ago

mizginstlm commented 1 year ago

API call to Developer Portal failed: Error, Request failed with status code 422, API name: create-app, X-Correlation-ID: 5fe7d18c-8cd6-4478-abdb-05d8e75e952f. This may come from some intermittent service error. Please wait for a few minutes and retry the current step. data: "Value cannot be name: accessToken"

stack: DeveloperPortalAPIFailed: API call to Developer Portal failed: Error, Request failed with status code 422, API name: create-app, X-Correlation-ID: 5fe7d18c-8cd6-4478-abdb-05d8e75e952f. This may come from some intermittent service error. Please wait for a few minutes and retry the current step. data: "Value cannot be name: accessToken" at AppStudioResultFactory.SystemError (:2:7657360) at wrapException (:2:7626256) at Object.importApp (:2:7629559) at process.processTicksAndRejections (node::96:5) at async Object.createTeamsApp (:2:7609468) at async AppManifest.provision (:2:7582333) at async AppManifest. (:2:6957183) at async TeamsfxCore.provision (:2:6511322) at async TeamsfxCore. (:2:6957183) at async FxCore.provisionResourcesOld (:2:7943430) at async FxCore. (:2:8080524) at async exports.ProjectSettingsWriterMW (:2:8135874) at async exports.ContextInjectorMW (:2:8069319) at async FxCore. (:2:8075982) at async exports.ProjectSettingsLoaderMW (:2:8134511) at async exports.ProjectVersionCheckerMW (:2:8139330) at async exports.AadManifestMigrationMW (:2:8048999) at async exports.ProjectConsolidateMW (:2:8069031) at async exports.ProjectMigratorMW (:2:8118007) at async exports.ConcurrentLockerMW (:2:8051543) at async exports.ErrorHandlerMW (:2:8082459)

ghost commented 1 year ago

Thank you for contacting us! Any issue or feedback from you is quite important to us. We will do our best to fully respond to your issue as soon as possible. Sometimes additional investigations may be needed, we will usually get back to you within 2 days by adding comments to this issue. Please stay tuned.

ghost commented 1 year ago

Sorry for the inconvenience! Based on the info provided, the issue is caused by the API failure from Teams Developer Portal. We will inform you once we get any updates.

Githamza commented 1 year ago

any updates ? I have a similar issue ?

√ Teams app manifest is resolved and app package is saved in /Users/hamzahaddad/TeamsApps/newtabfromscrach/rhapp/build/appPackage/appPackage.local.zip

× DeveloperPortalAPIFailed: API call to Developer Portal failed: Error, Request failed with status code 422, API name: create-app, X-Correlation-ID: c5d96f9c-9284-4290-872f-5ae5e6d3b923. This may come from some intermittent service error. Please wait for a few minutes and retry the current step. data: "Error mapping types.\r\n\r\nMapping types:\r\nApplicationManifest -> AppDefinition\r\nAppStudio.API.Models.ApplicationManifest -> AppStudio.API.Models.AppDefinition\r\n\r\nType Map configuration:\r\nApplicationManifest -> AppDefinition\r\nAppStudio.API.Models.ApplicationManifest -> AppStudio.API.Models.AppDefinition\r\n\r\nDestination Member:\r\nMeetingExtensionDefinition\r\n"

Visit https://aka.ms/teamsfx-debug-prepare-manifest-task to learn more about 'Build and upload Teams manifest' task.
nliu-ms commented 1 year ago

Hey @Githamza , can you please provide the "meetingExtensionDefinition" section in your manifest? And if you do not use this section, please remove it and try again to see if it works. Thank you.

Githamza commented 1 year ago

Hi @nliu-ms ,By deleting the meetingExtensionDefinitionsection it works. But I need to use this in order to enable meeting stage apps for anonymous users

{
  "$schema": "https://developer.microsoft.com/en-us/json-schemas/teams/v1.16/MicrosoftTeams.schema.json",
  "manifestVersion": "1.16",
  "version": "1.0.0",
  "id": "${{TEAMS_APP_ID}}",
  "packageName": "com.microsoft.teams.extension",
  "developer": {
    "name": "Teams App, Inc.",
    "websiteUrl": "https://www.example.com",
    "privacyUrl": "https://www.example.com/termofuse",
    "termsOfUseUrl": "https://www.example.com/privacy"
  },
  "icons": {
    "color": "${{CONFIG__MANIFEST__ICONS__COLOR}}",
    "outline": "${{CONFIG__MANIFEST__ICONS__OUTLINE}}"
  },
  "meetingExtensionDefinition": {
    "supportsAnonymousGuestUsers": true
  },
  "name": {
    "short": "${{CONFIG__MANIFEST__APPNAME__SHORT}}",
    "full": "${{CONFIG__MANIFEST__APPNAME__FULL}}"
  },
  "description": {
    "short": "${{CONFIG__MANIFEST__DESCRIPTION__SHORT}}",
    "full": "${{CONFIG__MANIFEST__DESCRIPTION__FULL}}"
  },
  "accentColor": "#FFFFFF",
  "bots": [],
  "composeExtensions": [],
  "configurableTabs": [
    {
      "configurationUrl": "${{PROVISIONOUTPUT__AZURESTORAGETABOUTPUT__ENDPOINT}}${{PROVISIONOUTPUT__AZURESTORAGETABOUTPUT__INDEXPATH}}/config",
      "canUpdateConfiguration": true,

      "scopes": ["team", "groupchat"],
      "meetingSurfaces": ["sidePanel", "stage"],
      "context": [
        "meetingChatTab",
        "meetingDetailsTab",
        "meetingSidePanel",
        "meetingStage"
      ]
    }
  ],
  "staticTabs": [
    {
      "entityId": "index0",
      "name": "Personal Tab",
      "contentUrl": "${{PROVISIONOUTPUT__AZURESTORAGETABOUTPUT__ENDPOINT}}${{PROVISIONOUTPUT__AZURESTORAGETABOUTPUT__INDEXPATH}}/tab",
      "websiteUrl": "${{PROVISIONOUTPUT__AZURESTORAGETABOUTPUT__ENDPOINT}}${{PROVISIONOUTPUT__AZURESTORAGETABOUTPUT__INDEXPATH}}/tab",
      "scopes": ["personal"]
    }
  ],
  "permissions": ["identity", "messageTeamMembers"],
  "validDomains": ["${{PROVISIONOUTPUT__AZURESTORAGETABOUTPUT__DOMAIN}}"],
  "webApplicationInfo": {
    "id": "${{AAD_APP_CLIENT_ID}}",
    "resource": "api://${{PROVISIONOUTPUT__AZURESTORAGETABOUTPUT__DOMAIN}}/${{AAD_APP_CLIENT_ID}}"
  }
}
nliu-ms commented 1 year ago

Got it @Githamza , I can reproduce the error, I will report it to Teams Developer Portal team, it might be a bug from server side. Sorry for the inconvenience.

nliu-ms commented 1 year ago

Hey @Githamza , Teams Developer Portal team has deployed a hotfix. Can you please try again and let me know if it works for you now? Thank you!

Githamza commented 1 year ago

I don't get the error anymore , but the feature is not working yet. anonymous users don't see the app when it's shared on meeting stage . Is the fix concerning the toolkit error or also the feature that's not working ?

image
nliu-ms commented 1 year ago

Hey @Githamza , the fix was concerning the Toolkit error. I will reach out to Teams Developer Portal team for more information.

nliu-ms commented 1 year ago

Hey @Githamza, I've got the response from corresponding team. This is currently expected as some dependency was rolled back earlier this month, and the ETA for the fix is the end of April. I will keep you updated, sorry for the inconvenience!

Githamza commented 1 year ago

What is going to be fixed by the end of April ? The toolkit compilation error or the apps running with anonymous user in meeting stage feature ?

nliu-ms commented 1 year ago

@Githamza , sorry for the ambiguity. The anonymous user in meeting stage feature will be fixed by the end of April.

Githamza commented 1 year ago

Any updates ? When the bug will be fixed ? It's important for my business to work well

nliu-ms commented 1 year ago

Hey @Githamza , I got the updates from corresponding team that the scenario "anonymous user in meeting stage" is not fully supported due to a dependency on React on Web experience, which is not fully rolled out. I'm checking with them about the ETA. Will get back to you ASAP.

nliu-ms commented 1 year ago

Hey @Githamza , sorry for the late reply. I checked with the team who implements the scenario of supporting anonymous user in meeting. Unfortunately, they gave me a bad news that this scenario is not supported as planned, it is currently blocked on a dependency and there is no ETA for the re-rollout plan. I will follow up with them and get back to you when I get any updates, sorry for the inconvenience.

Githamza commented 1 year ago

Oh ! That a really bad news ! It's killing my whole business idea ! I'm upset .. so much time working on that. So sad the team is not able to solve that

Githamza commented 1 year ago

Will this feature be maintained and fixed later in futur at least ? Or It will be canceled ?

nliu-ms commented 1 year ago

@Githamza , as far as I know the feature will be maintained and fixed later, won't be cancelled. I'm asking them if they have channels to communicate with users. If so, I will let you know and you can get latest update from them.

Githamza commented 1 year ago

Thank you , I need visibility to decide how should I implement my features and communicate to clients .

nliu-ms commented 1 year ago

Hey @Githamza , I still get no ETA from Meeting Extensibility team. But they will find a public forum for communicating with users. I will let you know once I get updated, and you can use the forum to get more visibility from them. Thanks!

Githamza commented 1 year ago

Thank you . I'll wait for you updates

nliu-ms commented 11 months ago

Hey @Githamza , I got the response from Meeting Extensibility team. You can use public forums listed below to ask questions about Teams. Please remember to use correct tag, it will make the question to the correct team. Sorry for the inconvenience! Hope you can get detailed answers there. https://learn.microsoft.com/en-us/microsoftteams/platform/feedback#developer-community-forums

Githamza commented 11 months ago

Thank you , I have posted a question on the MS Q&A forum. thanks

nliu-ms commented 9 months ago

Close this issue as it's delivered to Meeting Extensibility team.