search

microsoft / csapps-msteams-watercooler

Water Cooler is a custom Teams app that enables corporate teams to create, invite, and join casual conversations among teammates, like those that take place by the Water Cooler or break room. Use this template for multiple scenarios, such as new non-project related announcements, topics of interest, current events, or conversations about hobbies. The app provides an easy interface for anyone to find an existing conversation or start a new one. It's a foundation for building custom targeted communication capabilities, promoting interaction amongst coworkers who may otherwise not get a chance to socialize during breaks.
MIT License
23 stars 17 forks source link

New Room Creation stuck at loading #32

Closed cagrimunyas closed 3 years ago

cagrimunyas commented 3 years ago

After deploying the app on Teams there is no existing room so when I try to create a new room the task interface stuck at loading indicator. Unfortunately nothing is logged throughout the code, so I can't backtrace the source of the error. Any help is appreciated.

cagrimunyas commented 3 years ago

Adding Screenshot of the error image

rdeoburman commented 3 years ago

There is some room icons in "csapps-msteams-watercooler/WaterCoolerAPI/WaterCoolerAPI/Icons/" folder. Upload these icons to blob container. It will work.

rwenz02 commented 3 years ago

I had the same problem, although I uploaded my icons in the Blob container. The error was partly due to the fact that under the "Graphhelper" in the "Helpers" folder, the "CreateOnlineMeeting" function executed the following request: var onlineMeetingResponse = await graphServiceClient.Users[this.configuration[Common.Constants.UserIdConfigurationSettingsKey]].OnlineMeetings .Request() .AddAsync(onlineMeeting); return onlineMeetingResponse;

However, [this.configuration[Common.Constants.UserIdConfigurationSettingsKey]] had the wrong Id, I had to replace it with my own one. Furthermore I had to activate some SecurityProtocols in the class "ParticitantsScheduler" in the method "RunJob": ServicePointManager.SecurityProtocol =. (SecurityProtocolType)48 | (SecurityProtocolType)192 | (SecurityProtocolType)768 | (SecurityProtocolType)3072;

This did the trick for me

cagrimunyas commented 3 years ago

Thank you, I located the problem after posting this. while creating the room, component gets the first image as the default, when the blob is empty there is no first element so it gets stuck at loading state. Uploading the icons solved my issue.