search

MicrosoftDocs / msteams-docs

Source for the Microsoft Teams developer platform documentation.
https://aka.ms/teamsdev
Creative Commons Attribution 4.0 International
285 stars 506 forks source link

"handleMessageError" when saving connector configuration caused by the undefined property "needsIdentity" in the manifest schema #2949

Open jouhami opened 3 years ago

jouhami commented 3 years ago

I'am following the documenation here : https://docs.microsoft.com/en-us/microsoftteams/platform/webhooks-and-connectors/how-to/connectors-creating#adding-a-connector-to-your-teams-app

I registered the connector and downloaded the generated manifest.json then packaged (with icons) and tried to sideload the zip which was successful but when I tried to configure the connector I got the following error when the registered save handler was invoked (registerOnSaveHandler) :

{ "seq": 1616407542483, "timestamp": 1616410220797, "flightSettings": { "Name": "ConnectorFrontEndSettings", "AriaSDKToken": "d127f72a3abd41c9b9dd94faca947689-d58285e6-3a68-4cab-a458-37b9d9761d35-7033", "SPAEnabled": true, "ClassificationFilterEnabled": true, "ClientRoutingEnabled": true, "EnableYammerGroupOption": true, "EnableFadeMessage": false, "EnableDomainBasedOwaConnectorList": false, "EnableDomainBasedTeamsConnectorList": false, "DevPortalSPAEnabled": true, "ShowHomeNavigationButtonOnConfigurationPage": false, "DisableConnectToO365InlineDeleteFeedbackPage": true }, "status": 500, "clientType": "SkypeSpaces", "connectorType": "b3a71b98-2e28-48e2-a17c-cf389275ae01", "name": "handleMessageError" }

I then tried to open the generated manifest using the App Studio (App Studio -> Import an existing app) and this time I got a meaningful error saying the property needsIdentity is not defined by the schema from the manifest (https://developer.microsoft.com/en-us/json-schemas/teams/v1.3/MicrosoftTeams.schema.json)

image

Removing this property fixed the issue and I was able to save the connector configuration. I could not find any documentation about this property. I checked the last version of the schema by now (1.8) and it's not there !!

ghost commented 3 years ago

Hi jouhami! Thank you for bringing this issue to our attention. We will investigate and if we require further information we will reach out in one business day. Please use this link to escalate if you don't get replies.

Best regards, Teams Platform

Sridevi-MSFT commented 3 years ago

Hi @jouhami, I will repro at my end and will let you know.

Sridevi-MSFT commented 3 years ago

@jouhami, I am able to repro the issue and taking this for internal discussion with team.

Sridevi-MSFT commented 3 years ago

@jouhami, We have raised a bug for this issue, concerned team is working on it.

bmedenwald commented 1 year ago

I'm encountering this same issue. But, I do not have needsIdentity in my manifest and my app package validates without errors (other than warnings about using ngrok).

@Sridevi-MSFT You were able to reproduce and yet this is still an open bug from coming up on 2 years. What is the bug and how can I work around it?

ChetanSharma-msft commented 1 year ago

Hello @bmedenwald - Sorry for delay in response.

We will check the bug status and let you know the updates.