You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I posted this elsewhere but I realized it was in the wrong area, so I do apologize. This was done with the latest version of the SDK as of 1/2/2025.
So as an experiment I pulled the whole Agents Solution down, and added an Empty Teams App from the Visual Studio template.
I then updated one of the "Teams" projects, "BotAllCards" launchSerttings.json to include the "Teams App Test Tool" json.
I then updated the new Empty Teams App template to include the Teams App Test Tool json in the launchSettings.json.
Finally I created a new debugging profile to run both of these projects.
Once I started them both up, the Teams App Test Tool started as expected, but the "onMembersAddedAsync" method did not fire. All of the other code worked, just that did not fire.
Thoughts?
The text was updated successfully, but these errors were encountered:
BTW I did another test where I changed all the "agent" references back to the "bot framework" references and it worked perfectly. The issue is definitely in the agent code.
I posted this elsewhere but I realized it was in the wrong area, so I do apologize. This was done with the latest version of the SDK as of 1/2/2025.
So as an experiment I pulled the whole Agents Solution down, and added an Empty Teams App from the Visual Studio template.
I then updated one of the "Teams" projects, "BotAllCards" launchSerttings.json to include the "Teams App Test Tool" json.
I then updated the new Empty Teams App template to include the Teams App Test Tool json in the launchSettings.json.
Finally I created a new debugging profile to run both of these projects.
Once I started them both up, the Teams App Test Tool started as expected, but the "onMembersAddedAsync" method did not fire. All of the other code worked, just that did not fire.
Thoughts?
The text was updated successfully, but these errors were encountered: