Company Communicator stop working when use New Teams version

[CRVieiras]

My company turned on to use New version of Teams but I found that the communicator is error as attached, when I get back to normal Teams version "1.6.00.29964 (64-bit)" it worked fine. please help to advise if we have version that able to use with new Teams please.

[luishdemetrio]

That issue is happening for all CC versions due a change that was done on Azure FrontDoor. We provided a temporary fix today to direct call the APIs. Please rebuild (sync) the app service.

[Fadel1949]

Hello @cristianoag , I have seen the official repo fix the problem. Has your repo fixed the same problem as the official repo? Thank you very much. Ref. official repo https://github.com/OfficeDev/microsoft-teams-apps-company-communicator/issues/1201#issuecomment-1824323987

[cristianoag]

Yes. You need to resync. Keep in mind that it is a temporary solution. It is basically a bypass of the front door for all calls to the api. As soon as front door gets fixed we will remove the bypass and you will need to resync again.

Get Outlook for iOShttps://aka.ms/o0ukef

---

From: Fadel1949 @.> Sent: Friday, November 24, 2023 3:29:03 AM To: cristianoag/microsoft-teams-apps-company-communicator @.> Cc: Cristiano Goncalves @.>; Mention @.> Subject: Re: [cristianoag/microsoft-teams-apps-company-communicator] Company Communicator stop working when use New Teams version (Issue #68)

Hello @cristianoaghttps://github.com/cristianoag , I have seen the official repo fix the problem. Has your repo fixed the same problem as the official repo? Thank you very much. Ref. official repo OfficeDev#1201 (comment)https://github.com/OfficeDev/microsoft-teams-apps-company-communicator/issues/1201#issuecomment-1824323987

— Reply to this email directly, view it on GitHubhttps://github.com/cristianoag/microsoft-teams-apps-company-communicator/issues/68#issuecomment-1825203445, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALSAPKWDIFRN5MKADVINPADYGA5C7AVCNFSM6AAAAAA7YFL2AGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRVGIYDGNBUGU. You are receiving this because you were mentioned.Message ID: @.***>

[jackdawsonnv]

Hi @cristianoag , I am still experiencing the error message described above after syncing the app service and all three of the function services. Any suggestions to resolve it?

[cristianoag]

Please test using the teams client on the browser and clean the cache to make sure it is not influencing anything. If you have any firewalls between your clients and the app service, make sure you allow connections directly to the app service. What temporary fix does is bypass the front door for all API calls.

---

From: jackdawsonnv @.> Sent: Tuesday, November 28, 2023 16:53 To: cristianoag/microsoft-teams-apps-company-communicator @.> Cc: Cristiano Goncalves @.>; Mention @.> Subject: Re: [cristianoag/microsoft-teams-apps-company-communicator] Company Communicator stop working when use New Teams version (Issue #68)

Hi @cristianoaghttps://github.com/cristianoag , I am still experiencing the error message described above after syncing the app service and all three of the function services. Any suggestions to resolve it?

— Reply to this email directly, view it on GitHubhttps://github.com/cristianoag/microsoft-teams-apps-company-communicator/issues/68#issuecomment-1830621840, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALSAPKU5BHJPD2ZOCZQCAJDYGY6MJAVCNFSM6AAAAAA7YFL2AGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZQGYZDCOBUGA. You are receiving this because you were mentioned.Message ID: @.***>

[jackdawsonnv]

Please test using the teams client on the browser and clean the cache to make sure it is not influencing anything. If you have any firewalls between your clients and the app service, make sure you allow connections directly to the app service. What temporary fix does is bypass the front door for all API calls. …

Hi @cristianoag , Thank you for your quick reply. I already tried restarting the web app service and accessing it using the Teams client in a browser (after clearing the cache), but I am still seeing the same error. I have tried resyncing the app service twice now with the same results. Any other suggestions?

[cristianoag]

Do you have any firewalls between Teams clientes and app service? If yes, please check if the app service URL is on the whitelist.

Get Outlook for iOShttps://aka.ms/o0ukef

---

From: jackdawsonnv @.> Sent: Tuesday, November 28, 2023 5:08:25 PM To: cristianoag/microsoft-teams-apps-company-communicator @.> Cc: Cristiano Goncalves @.>; Mention @.> Subject: Re: [cristianoag/microsoft-teams-apps-company-communicator] Company Communicator stop working when use New Teams version (Issue #68)

Please test using the teams client on the browser and clean the cache to make sure it is not influencing anything. If you have any firewalls between your clients and the app service, make sure you allow connections directly to the app service. What temporary fix does is bypass the front door for all API calls. … ____ From: jackdawsonnv @.> Sent: Tuesday, November 28, 2023 16:53 To: cristianoag/microsoft-teams-apps-company-communicator @.> Cc: Cristiano Goncalves @.>; Mention @.> Subject: Re: [cristianoag/microsoft-teams-apps-company-communicator] Company Communicator stop working when use New Teams version (Issue #68https://github.com/cristianoag/microsoft-teams-apps-company-communicator/issues/68) Hi @cristianoaghttps://github.com/cristianoaghttps://github.com/cristianoag , I am still experiencing the error message described above after syncing the app service and all three of the function services. Any suggestions to resolve it? — Reply to this email directly, view it on GitHub<#68 (comment)https://github.com/cristianoag/microsoft-teams-apps-company-communicator/issues/68#issuecomment-1830621840>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALSAPKU5BHJPD2ZOCZQCAJDYGY6MJAVCNFSM6AAAAAA7YFL2AGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZQGYZDCOBUGA. You are receiving this because you were mentioned.Message ID: @.***>

Hi @cristianoaghttps://github.com/cristianoag , Thank you for your quick reply. I already tried restarting the web app service and accessing it using the Teams client in a browser (after clearing the cache), but I am still seeing the same error. I have tried resyncing the app service twice now with the same results. Any other suggestions?

— Reply to this email directly, view it on GitHubhttps://github.com/cristianoag/microsoft-teams-apps-company-communicator/issues/68#issuecomment-1830641420, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALSAPKVA4XD6FUEASNQF3CTYGZADTAVCNFSM6AAAAAA7YFL2AGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZQGY2DCNBSGA. You are receiving this because you were mentioned.Message ID: @.***>

[jackdawsonnv]

Do you have any firewalls between Teams clientes and app service? If yes, please check if the app service URL is on the whitelist. Get Outlook for iOShttps://aka.ms/o0ukef … Yes, there is a firewall between the Teams client and the app service in the Azure cloud, but we do not restrict outbound access through our firewall AND this Company Communicator app was working perfectly until the new Teams client update. No other network or firewall changes have been made since this error message appeared. I have also tested this from a different location with the same error message.

[cristianoag]

Are you using master-v4.51? If yes, please resync it as I forgot to fix that version and just did it right now. Cristiano

---

From: jackdawsonnv @.> Sent: Tuesday, November 28, 2023 17:59 To: cristianoag/microsoft-teams-apps-company-communicator @.> Cc: Cristiano Goncalves @.>; Mention @.> Subject: Re: [cristianoag/microsoft-teams-apps-company-communicator] Company Communicator stop working when use New Teams version (Issue #68)

Do you have any firewalls between Teams clientes and app service? If yes, please check if the app service URL is on the whitelist. Get Outlook for iOShttps://aka.ms/o0ukef … Yes, there is a firewall between the Teams client and the app service in the Azure cloud, but we do not restrict outbound access through our firewall AND this Company Communicator app was working perfectly until the new Teams client update. No other network or firewall changes have been made since this error message appeared. I have also tested this from a different location with the same error message.

— Reply to this email directly, view it on GitHubhttps://github.com/cristianoag/microsoft-teams-apps-company-communicator/issues/68#issuecomment-1830735594, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALSAPKSPWW3LDHHQLTD2YJTYGZGBTAVCNFSM6AAAAAA7YFL2AGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZQG4ZTKNJZGQ. You are receiving this because you were mentioned.Message ID: @.***>

[jackdawsonnv]

Actually, I am using the master branch. Should I be using another branch instead?

Get Outlook for iOShttps://aka.ms/o0ukef

---

From: Cristiano Goncalves @.> Sent: Tuesday, November 28, 2023 1:23:11 PM To: cristianoag/microsoft-teams-apps-company-communicator @.> Cc: Jack Dawson @.>; Comment @.> Subject: Re: [cristianoag/microsoft-teams-apps-company-communicator] Company Communicator stop working when use New Teams version (Issue #68)

Are you using master-v4.51? If yes, please resync it as I forgot to fix that version and just did it right now. Cristiano

---

From: jackdawsonnv @.> Sent: Tuesday, November 28, 2023 17:59 To: cristianoag/microsoft-teams-apps-company-communicator @.> Cc: Cristiano Goncalves @.>; Mention @.> Subject: Re: [cristianoag/microsoft-teams-apps-company-communicator] Company Communicator stop working when use New Teams version (Issue #68)

Do you have any firewalls between Teams clientes and app service? If yes, please check if the app service URL is on the whitelist. Get Outlook for iOShttps://aka.ms/o0ukef … Yes, there is a firewall between the Teams client and the app service in the Azure cloud, but we do not restrict outbound access through our firewall AND this Company Communicator app was working perfectly until the new Teams client update. No other network or firewall changes have been made since this error message appeared. I have also tested this from a different location with the same error message.

— Reply to this email directly, view it on GitHubhttps://github.com/cristianoag/microsoft-teams-apps-company-communicator/issues/68#issuecomment-1830735594, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALSAPKSPWW3LDHHQLTD2YJTYGZGBTAVCNFSM6AAAAAA7YFL2AGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZQG4ZTKNJZGQ. You are receiving this because you were mentioned.Message ID: @.***>

— Reply to this email directly, view it on GitHubhttps://github.com/cristianoag/microsoft-teams-apps-company-communicator/issues/68#issuecomment-1830769618, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AID6FX5FDZ74U4N2ATNEE4TYGZI37AVCNFSM6AAAAAA7YFL2AGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZQG43DSNRRHA. You are receiving this because you commented.Message ID: @.***>

[cristianoag]

master was already fixed. Sorry that was a change in front door that is impacting all instances of CC. The fix has worked for multiple customers so far. Need to troubleshoot as it looks like you have another problem.

Is the sync completing ok?

Get Outlook for iOShttps://aka.ms/o0ukef

---

From: jackdawsonnv @.> Sent: Tuesday, November 28, 2023 6:48:09 PM To: cristianoag/microsoft-teams-apps-company-communicator @.> Cc: Cristiano Goncalves @.>; Mention @.> Subject: Re: [cristianoag/microsoft-teams-apps-company-communicator] Company Communicator stop working when use New Teams version (Issue #68)

Actually, I am using the master branch. Should I be using another branch instead?

Get Outlook for iOShttps://aka.ms/o0ukef

---

From: Cristiano Goncalves @.> Sent: Tuesday, November 28, 2023 1:23:11 PM To: cristianoag/microsoft-teams-apps-company-communicator @.> Cc: Jack Dawson @.>; Comment @.> Subject: Re: [cristianoag/microsoft-teams-apps-company-communicator] Company Communicator stop working when use New Teams version (Issue #68)

Are you using master-v4.51? If yes, please resync it as I forgot to fix that version and just did it right now. Cristiano

---

From: jackdawsonnv @.> Sent: Tuesday, November 28, 2023 17:59 To: cristianoag/microsoft-teams-apps-company-communicator @.> Cc: Cristiano Goncalves @.>; Mention @.> Subject: Re: [cristianoag/microsoft-teams-apps-company-communicator] Company Communicator stop working when use New Teams version (Issue #68)

Do you have any firewalls between Teams clientes and app service? If yes, please check if the app service URL is on the whitelist. Get Outlook for iOShttps://aka.ms/o0ukef … Yes, there is a firewall between the Teams client and the app service in the Azure cloud, but we do not restrict outbound access through our firewall AND this Company Communicator app was working perfectly until the new Teams client update. No other network or firewall changes have been made since this error message appeared. I have also tested this from a different location with the same error message.

— Reply to this email directly, view it on GitHubhttps://github.com/cristianoag/microsoft-teams-apps-company-communicator/issues/68#issuecomment-1830735594, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALSAPKSPWW3LDHHQLTD2YJTYGZGBTAVCNFSM6AAAAAA7YFL2AGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZQG4ZTKNJZGQ. You are receiving this because you were mentioned.Message ID: @.***>

— Reply to this email directly, view it on GitHubhttps://github.com/cristianoag/microsoft-teams-apps-company-communicator/issues/68#issuecomment-1830769618, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AID6FX5FDZ74U4N2ATNEE4TYGZI37AVCNFSM6AAAAAA7YFL2AGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZQG43DSNRRHA. You are receiving this because you commented.Message ID: @.***>

— Reply to this email directly, view it on GitHubhttps://github.com/cristianoag/microsoft-teams-apps-company-communicator/issues/68#issuecomment-1830801698, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALSAPKUO4SA2JSC3SJWSZUTYGZLZTAVCNFSM6AAAAAA7YFL2AGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZQHAYDCNRZHA. You are receiving this because you were mentioned.Message ID: @.***>

[jackdawsonnv]

Yes. The sync is successful after which I restart the app service, cleared my browser cache, and then accessed the Teams client through the web browser but still get the same error message. I don’t want to do this if I don’t have to, but should I just delete and redeploy the entire app?

Get Outlook for iOShttps://aka.ms/o0ukef

---

From: Cristiano Goncalves @.> Sent: Tuesday, November 28, 2023 1:50:19 PM To: cristianoag/microsoft-teams-apps-company-communicator @.> Cc: Jack Dawson @.>; Comment @.> Subject: Re: [cristianoag/microsoft-teams-apps-company-communicator] Company Communicator stop working when use New Teams version (Issue #68)

master was already fixed. Sorry that was a change in front door that is impacting all instances of CC. The fix has worked for multiple customers so far. Need to troubleshoot as it looks like you have another problem.

Is the sync completing ok?

Get Outlook for iOShttps://aka.ms/o0ukef

---

From: jackdawsonnv @.> Sent: Tuesday, November 28, 2023 6:48:09 PM To: cristianoag/microsoft-teams-apps-company-communicator @.> Cc: Cristiano Goncalves @.>; Mention @.> Subject: Re: [cristianoag/microsoft-teams-apps-company-communicator] Company Communicator stop working when use New Teams version (Issue #68)

Actually, I am using the master branch. Should I be using another branch instead?

Get Outlook for iOShttps://aka.ms/o0ukef

---

From: Cristiano Goncalves @.> Sent: Tuesday, November 28, 2023 1:23:11 PM To: cristianoag/microsoft-teams-apps-company-communicator @.> Cc: Jack Dawson @.>; Comment @.> Subject: Re: [cristianoag/microsoft-teams-apps-company-communicator] Company Communicator stop working when use New Teams version (Issue #68)

Are you using master-v4.51? If yes, please resync it as I forgot to fix that version and just did it right now. Cristiano

---

From: jackdawsonnv @.> Sent: Tuesday, November 28, 2023 17:59 To: cristianoag/microsoft-teams-apps-company-communicator @.> Cc: Cristiano Goncalves @.>; Mention @.> Subject: Re: [cristianoag/microsoft-teams-apps-company-communicator] Company Communicator stop working when use New Teams version (Issue #68)

Do you have any firewalls between Teams clientes and app service? If yes, please check if the app service URL is on the whitelist. Get Outlook for iOShttps://aka.ms/o0ukef … Yes, there is a firewall between the Teams client and the app service in the Azure cloud, but we do not restrict outbound access through our firewall AND this Company Communicator app was working perfectly until the new Teams client update. No other network or firewall changes have been made since this error message appeared. I have also tested this from a different location with the same error message.

— Reply to this email directly, view it on GitHubhttps://github.com/cristianoag/microsoft-teams-apps-company-communicator/issues/68#issuecomment-1830735594, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALSAPKSPWW3LDHHQLTD2YJTYGZGBTAVCNFSM6AAAAAA7YFL2AGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZQG4ZTKNJZGQ. You are receiving this because you were mentioned.Message ID: @.***>

— Reply to this email directly, view it on GitHubhttps://github.com/cristianoag/microsoft-teams-apps-company-communicator/issues/68#issuecomment-1830769618, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AID6FX5FDZ74U4N2ATNEE4TYGZI37AVCNFSM6AAAAAA7YFL2AGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZQG43DSNRRHA. You are receiving this because you commented.Message ID: @.***>

— Reply to this email directly, view it on GitHubhttps://github.com/cristianoag/microsoft-teams-apps-company-communicator/issues/68#issuecomment-1830801698, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALSAPKUO4SA2JSC3SJWSZUTYGZLZTAVCNFSM6AAAAAA7YFL2AGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZQHAYDCNRZHA. You are receiving this because you were mentioned.Message ID: @.***>

— Reply to this email directly, view it on GitHubhttps://github.com/cristianoag/microsoft-teams-apps-company-communicator/issues/68#issuecomment-1830804611, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AID6FX2LG7WTVD2BUX5K4J3YGZMBXAVCNFSM6AAAAAA7YFL2AGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZQHAYDINRRGE. You are receiving this because you commented.Message ID: @.***>

[jackdawsonnv]

I was looking through the three Function apps and found new errors in the notification section that may be contributing to this problem. Please let me know if this could be the issue… @.***

@.*** Jack Dawson​​​​ Director ‑ Information Technology​ | +1 (775) 412-4305<tel:+1%20(775)%20412-4305>

From: Jack Dawson @.> Sent: Tuesday, November 28, 2023 1:54 PM To: cristianoag/microsoft-teams-apps-company-communicator @.>; cristianoag/microsoft-teams-apps-company-communicator @.> Cc: Comment @.> Subject: Re: [cristianoag/microsoft-teams-apps-company-communicator] Company Communicator stop working when use New Teams version (Issue #68)

Yes. The sync is successful after which I restart the app service, cleared my browser cache, and then accessed the Teams client through the web browser but still get the same error message. I don’t want to do this if I don’t have to, but should I just delete and redeploy the entire app?

Get Outlook for iOShttps://aka.ms/o0ukef

---

From: Cristiano Goncalves @.**@.>> Sent: Tuesday, November 28, 2023 1:50:19 PM To: cristianoag/microsoft-teams-apps-company-communicator @.**@.>> Cc: Jack Dawson @.**@.>>; Comment @.**@.>> Subject: Re: [cristianoag/microsoft-teams-apps-company-communicator] Company Communicator stop working when use New Teams version (Issue #68)

master was already fixed. Sorry that was a change in front door that is impacting all instances of CC. The fix has worked for multiple customers so far. Need to troubleshoot as it looks like you have another problem.

Is the sync completing ok?

Get Outlook for iOShttps://aka.ms/o0ukef

---

From: jackdawsonnv @.<mailto:@.>> Sent: Tuesday, November 28, 2023 6:48:09 PM To: cristianoag/microsoft-teams-apps-company-communicator @.<mailto:@.>> Cc: Cristiano Goncalves @.<mailto:@.>>; Mention @.<mailto:@.>> Subject: Re: [cristianoag/microsoft-teams-apps-company-communicator] Company Communicator stop working when use New Teams version (Issue #68)

Actually, I am using the master branch. Should I be using another branch instead?

Get Outlook for iOShttps://aka.ms/o0ukef

---

From: Cristiano Goncalves @.<mailto:@.>> Sent: Tuesday, November 28, 2023 1:23:11 PM To: cristianoag/microsoft-teams-apps-company-communicator @.<mailto:@.>> Cc: Jack Dawson @.<mailto:@.>>; Comment @.<mailto:@.>> Subject: Re: [cristianoag/microsoft-teams-apps-company-communicator] Company Communicator stop working when use New Teams version (Issue #68)

Are you using master-v4.51? If yes, please resync it as I forgot to fix that version and just did it right now. Cristiano

---

From: jackdawsonnv @.<mailto:@.>> Sent: Tuesday, November 28, 2023 17:59 To: cristianoag/microsoft-teams-apps-company-communicator @.<mailto:@.>> Cc: Cristiano Goncalves @.<mailto:@.>>; Mention @.<mailto:@.>> Subject: Re: [cristianoag/microsoft-teams-apps-company-communicator] Company Communicator stop working when use New Teams version (Issue #68)

Do you have any firewalls between Teams clientes and app service? If yes, please check if the app service URL is on the whitelist. Get Outlook for iOShttps://aka.ms/o0ukef … Yes, there is a firewall between the Teams client and the app service in the Azure cloud, but we do not restrict outbound access through our firewall AND this Company Communicator app was working perfectly until the new Teams client update. No other network or firewall changes have been made since this error message appeared. I have also tested this from a different location with the same error message.

— Reply to this email directly, view it on GitHubhttps://github.com/cristianoag/microsoft-teams-apps-company-communicator/issues/68#issuecomment-1830735594, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALSAPKSPWW3LDHHQLTD2YJTYGZGBTAVCNFSM6AAAAAA7YFL2AGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZQG4ZTKNJZGQ. You are receiving this because you were mentioned.Message ID: @.<mailto:@.>>

— Reply to this email directly, view it on GitHubhttps://github.com/cristianoag/microsoft-teams-apps-company-communicator/issues/68#issuecomment-1830769618, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AID6FX5FDZ74U4N2ATNEE4TYGZI37AVCNFSM6AAAAAA7YFL2AGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZQG43DSNRRHA. You are receiving this because you commented.Message ID: @.<mailto:@.>>

— Reply to this email directly, view it on GitHubhttps://github.com/cristianoag/microsoft-teams-apps-company-communicator/issues/68#issuecomment-1830801698, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALSAPKUO4SA2JSC3SJWSZUTYGZLZTAVCNFSM6AAAAAA7YFL2AGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZQHAYDCNRZHA. You are receiving this because you were mentioned.Message ID: @.<mailto:@.>>

— Reply to this email directly, view it on GitHubhttps://github.com/cristianoag/microsoft-teams-apps-company-communicator/issues/68#issuecomment-1830804611, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AID6FX2LG7WTVD2BUX5K4J3YGZMBXAVCNFSM6AAAAAA7YFL2AGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZQHAYDINRRGE. You are receiving this because you commented.Message ID: @.**@.>>

[cristianoag]

Functions weren’t affected by the issue and didn’t get any changes. So, if you’re seeing errors with functions those are being caused by another issue.

Get Outlook for iOShttps://aka.ms/o0ukef

---

From: jackdawsonnv @.> Sent: Tuesday, November 28, 2023 8:43:49 PM To: cristianoag/microsoft-teams-apps-company-communicator @.> Cc: Cristiano Goncalves @.>; Mention @.> Subject: Re: [cristianoag/microsoft-teams-apps-company-communicator] Company Communicator stop working when use New Teams version (Issue #68)

I was looking through the three Function apps and found new errors in the notification section that may be contributing to this problem. Please let me know if this could be the issue… @.***

@.*** Jack Dawson​​​​ Director ‑ Information Technology​ | +1 (775) 412-4305<tel:+1%20(775)%20412-4305>

From: Jack Dawson @.> Sent: Tuesday, November 28, 2023 1:54 PM To: cristianoag/microsoft-teams-apps-company-communicator @.>; cristianoag/microsoft-teams-apps-company-communicator @.> Cc: Comment @.> Subject: Re: [cristianoag/microsoft-teams-apps-company-communicator] Company Communicator stop working when use New Teams version (Issue #68)

Yes. The sync is successful after which I restart the app service, cleared my browser cache, and then accessed the Teams client through the web browser but still get the same error message. I don’t want to do this if I don’t have to, but should I just delete and redeploy the entire app?

Get Outlook for iOShttps://aka.ms/o0ukef

---

From: Cristiano Goncalves @.**@.>> Sent: Tuesday, November 28, 2023 1:50:19 PM To: cristianoag/microsoft-teams-apps-company-communicator @.**@.>> Cc: Jack Dawson @.**@.>>; Comment @.**@.>> Subject: Re: [cristianoag/microsoft-teams-apps-company-communicator] Company Communicator stop working when use New Teams version (Issue #68)

master was already fixed. Sorry that was a change in front door that is impacting all instances of CC. The fix has worked for multiple customers so far. Need to troubleshoot as it looks like you have another problem.

Is the sync completing ok?

Get Outlook for iOShttps://aka.ms/o0ukef

---

From: jackdawsonnv @.<mailto:@.>> Sent: Tuesday, November 28, 2023 6:48:09 PM To: cristianoag/microsoft-teams-apps-company-communicator @.<mailto:@.>> Cc: Cristiano Goncalves @.<mailto:@.>>; Mention @.<mailto:@.>> Subject: Re: [cristianoag/microsoft-teams-apps-company-communicator] Company Communicator stop working when use New Teams version (Issue #68)

Actually, I am using the master branch. Should I be using another branch instead?

Get Outlook for iOShttps://aka.ms/o0ukef

---

From: Cristiano Goncalves @.<mailto:@.>> Sent: Tuesday, November 28, 2023 1:23:11 PM To: cristianoag/microsoft-teams-apps-company-communicator @.<mailto:@.>> Cc: Jack Dawson @.<mailto:@.>>; Comment @.<mailto:@.>> Subject: Re: [cristianoag/microsoft-teams-apps-company-communicator] Company Communicator stop working when use New Teams version (Issue #68)

Are you using master-v4.51? If yes, please resync it as I forgot to fix that version and just did it right now. Cristiano

---

From: jackdawsonnv @.<mailto:@.>> Sent: Tuesday, November 28, 2023 17:59 To: cristianoag/microsoft-teams-apps-company-communicator @.<mailto:@.>> Cc: Cristiano Goncalves @.<mailto:@.>>; Mention @.<mailto:@.>> Subject: Re: [cristianoag/microsoft-teams-apps-company-communicator] Company Communicator stop working when use New Teams version (Issue #68)

Do you have any firewalls between Teams clientes and app service? If yes, please check if the app service URL is on the whitelist. Get Outlook for iOShttps://aka.ms/o0ukef … Yes, there is a firewall between the Teams client and the app service in the Azure cloud, but we do not restrict outbound access through our firewall AND this Company Communicator app was working perfectly until the new Teams client update. No other network or firewall changes have been made since this error message appeared. I have also tested this from a different location with the same error message.

— Reply to this email directly, view it on GitHubhttps://github.com/cristianoag/microsoft-teams-apps-company-communicator/issues/68#issuecomment-1830735594, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALSAPKSPWW3LDHHQLTD2YJTYGZGBTAVCNFSM6AAAAAA7YFL2AGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZQG4ZTKNJZGQ. You are receiving this because you were mentioned.Message ID: @.<mailto:@.>>

— Reply to this email directly, view it on GitHubhttps://github.com/cristianoag/microsoft-teams-apps-company-communicator/issues/68#issuecomment-1830769618, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AID6FX5FDZ74U4N2ATNEE4TYGZI37AVCNFSM6AAAAAA7YFL2AGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZQG43DSNRRHA. You are receiving this because you commented.Message ID: @.<mailto:@.>>

— Reply to this email directly, view it on GitHubhttps://github.com/cristianoag/microsoft-teams-apps-company-communicator/issues/68#issuecomment-1830801698, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALSAPKUO4SA2JSC3SJWSZUTYGZLZTAVCNFSM6AAAAAA7YFL2AGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZQHAYDCNRZHA. You are receiving this because you were mentioned.Message ID: @.<mailto:@.>>

— Reply to this email directly, view it on GitHubhttps://github.com/cristianoag/microsoft-teams-apps-company-communicator/issues/68#issuecomment-1830804611, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AID6FX2LG7WTVD2BUX5K4J3YGZMBXAVCNFSM6AAAAAA7YFL2AGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZQHAYDINRRGE. You are receiving this because you commented.Message ID: @.**@.>>

— Reply to this email directly, view it on GitHubhttps://github.com/cristianoag/microsoft-teams-apps-company-communicator/issues/68#issuecomment-1830952546, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALSAPKR5HRLPPZVHAOI3XSDYGZZLLAVCNFSM6AAAAAA7YFL2AGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZQHE2TENJUGY. You are receiving this because you were mentioned.Message ID: @.***>

[jackdawsonnv]

Ok, thanks. I only ask because these errors appeared after syncing.

@.*** Jack Dawson​​​​ Director ‑ Information Technology​ | +1 (775) 412-4305<tel:+1%20(775)%20412-4305>

From: Cristiano Goncalves @.> Sent: Tuesday, November 28, 2023 3:46 PM To: cristianoag/microsoft-teams-apps-company-communicator @.> Cc: Jack Dawson @.>; Comment @.> Subject: Re: [cristianoag/microsoft-teams-apps-company-communicator] Company Communicator stop working when use New Teams version (Issue #68)

Functions weren’t affected by the issue and didn’t get any changes. So, if you’re seeing errors with functions those are being caused by another issue.

Get Outlook for iOShttps://aka.ms/o0ukef

---

From: jackdawsonnv @.> Sent: Tuesday, November 28, 2023 8:43:49 PM To: cristianoag/microsoft-teams-apps-company-communicator @.> Cc: Cristiano Goncalves @.>; Mention @.> Subject: Re: [cristianoag/microsoft-teams-apps-company-communicator] Company Communicator stop working when use New Teams version (Issue #68)

I was looking through the three Function apps and found new errors in the notification section that may be contributing to this problem. Please let me know if this could be the issue… @.***

@.*** Jack Dawson​​​​ Director ‑ Information Technology​ | +1 (775) 412-4305<tel:+1%20(775)%20412-4305>

From: Jack Dawson @.> Sent: Tuesday, November 28, 2023 1:54 PM To: cristianoag/microsoft-teams-apps-company-communicator @.>; cristianoag/microsoft-teams-apps-company-communicator @.> Cc: Comment @.> Subject: Re: [cristianoag/microsoft-teams-apps-company-communicator] Company Communicator stop working when use New Teams version (Issue #68)

Yes. The sync is successful after which I restart the app service, cleared my browser cache, and then accessed the Teams client through the web browser but still get the same error message. I don’t want to do this if I don’t have to, but should I just delete and redeploy the entire app?

Get Outlook for iOShttps://aka.ms/o0ukef

---

From: Cristiano Goncalves @.**@.>> Sent: Tuesday, November 28, 2023 1:50:19 PM To: cristianoag/microsoft-teams-apps-company-communicator @.**@.>> Cc: Jack Dawson @.**@.>>; Comment @.**@.>> Subject: Re: [cristianoag/microsoft-teams-apps-company-communicator] Company Communicator stop working when use New Teams version (Issue #68)

master was already fixed. Sorry that was a change in front door that is impacting all instances of CC. The fix has worked for multiple customers so far. Need to troubleshoot as it looks like you have another problem.

Is the sync completing ok?

Get Outlook for iOShttps://aka.ms/o0ukef

---

From: jackdawsonnv @.<mailto:@.>> Sent: Tuesday, November 28, 2023 6:48:09 PM To: cristianoag/microsoft-teams-apps-company-communicator @.<mailto:@.>> Cc: Cristiano Goncalves @.<mailto:@.>>; Mention @.<mailto:@.>> Subject: Re: [cristianoag/microsoft-teams-apps-company-communicator] Company Communicator stop working when use New Teams version (Issue #68)

Actually, I am using the master branch. Should I be using another branch instead?

Get Outlook for iOShttps://aka.ms/o0ukef

---

From: Cristiano Goncalves @.<mailto:@.>> Sent: Tuesday, November 28, 2023 1:23:11 PM To: cristianoag/microsoft-teams-apps-company-communicator @.<mailto:@.>> Cc: Jack Dawson @.<mailto:@.>>; Comment @.<mailto:@.>> Subject: Re: [cristianoag/microsoft-teams-apps-company-communicator] Company Communicator stop working when use New Teams version (Issue #68)

Are you using master-v4.51? If yes, please resync it as I forgot to fix that version and just did it right now. Cristiano

---

From: jackdawsonnv @.<mailto:@.>> Sent: Tuesday, November 28, 2023 17:59 To: cristianoag/microsoft-teams-apps-company-communicator @.<mailto:@.>> Cc: Cristiano Goncalves @.<mailto:@.>>; Mention @.<mailto:@.>> Subject: Re: [cristianoag/microsoft-teams-apps-company-communicator] Company Communicator stop working when use New Teams version (Issue #68)

Do you have any firewalls between Teams clientes and app service? If yes, please check if the app service URL is on the whitelist. Get Outlook for iOShttps://aka.ms/o0ukef … Yes, there is a firewall between the Teams client and the app service in the Azure cloud, but we do not restrict outbound access through our firewall AND this Company Communicator app was working perfectly until the new Teams client update. No other network or firewall changes have been made since this error message appeared. I have also tested this from a different location with the same error message.

— Reply to this email directly, view it on GitHubhttps://github.com/cristianoag/microsoft-teams-apps-company-communicator/issues/68#issuecomment-1830735594, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALSAPKSPWW3LDHHQLTD2YJTYGZGBTAVCNFSM6AAAAAA7YFL2AGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZQG4ZTKNJZGQ. You are receiving this because you were mentioned.Message ID: @.<mailto:@.>>

— Reply to this email directly, view it on GitHubhttps://github.com/cristianoag/microsoft-teams-apps-company-communicator/issues/68#issuecomment-1830769618, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AID6FX5FDZ74U4N2ATNEE4TYGZI37AVCNFSM6AAAAAA7YFL2AGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZQG43DSNRRHA. You are receiving this because you commented.Message ID: @.<mailto:@.>>

— Reply to this email directly, view it on GitHubhttps://github.com/cristianoag/microsoft-teams-apps-company-communicator/issues/68#issuecomment-1830801698, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALSAPKUO4SA2JSC3SJWSZUTYGZLZTAVCNFSM6AAAAAA7YFL2AGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZQHAYDCNRZHA. You are receiving this because you were mentioned.Message ID: @.<mailto:@.>>

— Reply to this email directly, view it on GitHubhttps://github.com/cristianoag/microsoft-teams-apps-company-communicator/issues/68#issuecomment-1830804611, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AID6FX2LG7WTVD2BUX5K4J3YGZMBXAVCNFSM6AAAAAA7YFL2AGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZQHAYDINRRGE. You are receiving this because you commented.Message ID: @.**@.>>

— Reply to this email directly, view it on GitHubhttps://github.com/cristianoag/microsoft-teams-apps-company-communicator/issues/68#issuecomment-1830952546, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALSAPKR5HRLPPZVHAOI3XSDYGZZLLAVCNFSM6AAAAAA7YFL2AGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZQHE2TENJUGY. You are receiving this because you were mentioned.Message ID: @.***>

— Reply to this email directly, view it on GitHubhttps://github.com/cristianoag/microsoft-teams-apps-company-communicator/issues/68#issuecomment-1830954525, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AID6FX2JFXD7GOKJSGILOQDYGZZULAVCNFSM6AAAAAA7YFL2AGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZQHE2TINJSGU. You are receiving this because you commented.Message ID: @.***>

[Fadel1949]

I have the same problem. After re-sync, I still encounter the same problem. Use branch master.

[MarkusMGB]

@cristianoag same here, deployed the fix still not working.

[CRVieiras]

@cristianoag , bom dia! Mesma situação aqui. Refiz o sync, porém o erro persiste

[cristianoag]

Ok here is the deal. I just tested and the latest master-v5.31 is working fine. Unfortunately, I don't have time neither the right environments to perform regression tests to previous versions, so I recommend everybody that still wants to use this community version to update to master-v5.31.

What do you need to do?

1. Check if you have key vault already deployed on your resource group. If you have it, then you just need to disconnect the App Service and all functions and point them to master-v5.31. You can do that by accessing deployment center for each on of those resources, clicking disconnect under Source and reconnect specifying the branch master-v5.31 instead of just master or any other version. Then click Sync and wait until all resources get synced without any errors.
2. If you are in a previous version (if you don't have the key vault resource), then follow instructions available on the wiki and upgrade to the latest version.

Of course, you have the option to just wait until Front Door gets fixed and start passing the auth headers again to the back-end. Unfortunately, I don't have a date for when that is going to happen.

[Fadel1949]

@cristianoag Hi Cristiano, Regarding the master branch, do you have a plan for when the fix will be completed? Thank you very much.

[cristianoag]

Master is based on v5.13 and this is just a temporary workaround for the front door problem. I don’t have an environment based on 5.13 to test and I don’t think the effort worth. You can upgrade to 5.31, move to the official version or just wait for the front door fix.

Get Outlook for iOShttps://aka.ms/o0ukef

---

From: Fadel1949 @.> Sent: Thursday, November 30, 2023 3:51:15 AM To: cristianoag/microsoft-teams-apps-company-communicator @.> Cc: Cristiano Goncalves @.>; Mention @.> Subject: Re: [cristianoag/microsoft-teams-apps-company-communicator] Company Communicator stop working when use New Teams version (Issue #68)

@cristianoaghttps://github.com/cristianoag Hi Cristiano, Regarding the master branch, do you have a plan for when the fix will be completed? Thank you very much.

— Reply to this email directly, view it on GitHubhttps://github.com/cristianoag/microsoft-teams-apps-company-communicator/issues/68#issuecomment-1833203597, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALSAPKWCMAHYZTXBE5SNHRDYHAUGHAVCNFSM6AAAAAA7YFL2AGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZTGIYDGNJZG4. You are receiving this because you were mentioned.Message ID: @.***>

[MarkusMGB]

@cristianoag We have the latest Build, we synched the CC with your temporary fix and still no luck new Teams App ist not working. We even have now some users with the same problem in Teams classic

[cristianoag]

I recommend you to use the official version. I’m sorry, no time to troubleshoot specific cases.

Get Outlook for iOShttps://aka.ms/o0ukef

---

From: MarkusMGB @.> Sent: Friday, December 1, 2023 9:10:27 AM To: cristianoag/microsoft-teams-apps-company-communicator @.> Cc: Cristiano Goncalves @.>; Mention @.> Subject: Re: [cristianoag/microsoft-teams-apps-company-communicator] Company Communicator stop working when use New Teams version (Issue #68)

@cristianoaghttps://github.com/cristianoag We have the latest Build, we synched the CC with your temporary fix and still no luck new Teams App ist not working. We even have now some users with the same problem in Teams classic

— Reply to this email directly, view it on GitHubhttps://github.com/cristianoag/microsoft-teams-apps-company-communicator/issues/68#issuecomment-1836017186, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALSAPKXDDR5HKZJH3WMJ34DYHHCLHAVCNFSM6AAAAAA7YFL2AGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZWGAYTOMJYGY. You are receiving this because you were mentioned.Message ID: @.***>

[CeciliaRavera]

Hello. We have the same problem.. we redeployed to branch v5.31 and still not working :(

[cristianoag]

@CeciliaRavera and others. We just figured out that besides the update, you also need to temporarily disable the second rule in Front Door. After that restart the App Service and test. It will work.

[PaoloCastAway]

@cristianoag, question. Not sure if I correctly understood the fix: is this fix/solution actually bypassing Front Door? I read somewhere else that the very first workaround was to bypass FD. My customer's policies do not allow such bypass, so I have to be sure to be compliant before start a new deployment

[cristianoag]

Yes, the temporary fix bypasses the Front Door. If your customer requires it, there is no solution until the Front Door service gets fixed.

Get Outlook for iOShttps://aka.ms/o0ukef

---

From: Paolo Castaldi @.> Sent: Wednesday, December 20, 2023 11:12:21 AM To: cristianoag/microsoft-teams-apps-company-communicator @.> Cc: Cristiano Goncalves @.>; Mention @.> Subject: Re: [cristianoag/microsoft-teams-apps-company-communicator] Company Communicator stop working when use New Teams version (Issue #68)

@cristianoaghttps://github.com/cristianoag, question. Not sure if I correctly understood the fix: is this fix/solution actually bypassing Front Door? I read somewhere else that the very first workaround was to bypass FD. My customer's policies do not allow such bypass, so I have to be sure to be compliant before start a new deployment

— Reply to this email directly, view it on GitHubhttps://github.com/cristianoag/microsoft-teams-apps-company-communicator/issues/68#issuecomment-1864542230, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALSAPKXPBDLPOHC5RTDB4YDYKLW4LAVCNFSM6AAAAAA7YFL2AGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNRUGU2DEMRTGA. You are receiving this because you were mentioned.Message ID: @.***>

[Fadel1949]

@cristianoag I have a question: Why doesn't CC Branch Official have to disable the front door?

[CRVieiras]

Boa tarde!

Por gentileza, poderiam verificar essa questão? O Company Communicator funciona no "novo teams" no website, porém no app desktop continua apresentando erro.

Website Teams

Aplicativo Desktop Teams

[ostromecko]

Hi @cristianoag, I have done sync for the service app and all three functions, I'm pointing to master branch v5.31, I have also disabled the second rule for Azure front door but still I'm facing this issue. I'm checking both in the new desktop client and new browser client. How we can sort this issue out?

[ostromecko]

Hi @cristianoag, I have done sync for the service app and all three functions, I'm pointing to master branch v5.31, I have also disabled the second rule for Azure front door but still I'm facing this issue. I'm checking both in the new desktop client and new browser client. How we can sort this issue out?

This issue on my end was resolved.

[CRVieiras]

Hi @cristianoag, I have done sync for the service app and all three functions, I'm pointing to master branch v5.31, I have also disabled the second rule for Azure front door but still I'm facing this issue. I'm checking both in the new desktop client and new browser client. How we can sort this issue out?

This issue on my end was resolved.

What did you do to solve the problem?

[Maxiz80]

Hi @cristianoag, I have done sync for the service app and all three functions, I'm pointing to master branch v5.31, I have also disabled the second rule for Azure front door but still I'm facing this issue. I'm checking both in the new desktop client and new browser client. How we can sort this issue out?

This issue on my end was resolved.

What did you do to solve the problem?

Hi. In my case cleaning the cache solved the problem afetr doing what you've already done

[ostromecko]

Hi @cristianoag, I have done sync for the service app and all three functions, I'm pointing to master branch v5.31, I have also disabled the second rule for Azure front door but still I'm facing this issue. I'm checking both in the new desktop client and new browser client. How we can sort this issue out?

This issue on my end was resolved.

What did you do to solve the problem?

I have cleared cache few times in browser & desktop app and it finally worked.

[jvrabel88]

@cristianoag I am still having issues, even after disabling the 2nd front door routing rule and clearing cache on browser/teams. I have updated the app service and the 3 function apps to v5.31. All of the function apps runtime version to ~4 and .NET version 6. What else can I try or am I missing?

[cristianoag]

What is the error you’re receiving now?

Get Outlook for iOShttps://aka.ms/o0ukef

---

From: jvrabel88 @.> Sent: Wednesday, March 20, 2024 1:51:06 PM To: cristianoag/microsoft-teams-apps-company-communicator @.> Cc: Cristiano Goncalves @.>; Mention @.> Subject: Re: [cristianoag/microsoft-teams-apps-company-communicator] Company Communicator stop working when use New Teams version (Issue #68)

@cristianoaghttps://github.com/cristianoag I am still having issues, even after disabling the 2nd firewall rule and clearing cache on browser/teams. I have updated the app service and the 3 function apps to v5.31. All of the function apps runtime version to ~4 and .NET version 6. What else can I try or am I missing?

— Reply to this email directly, view it on GitHubhttps://github.com/cristianoag/microsoft-teams-apps-company-communicator/issues/68#issuecomment-2010043700, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALSAPKUQ2OVVTVCFAV5ZIRDYZG47VAVCNFSM6AAAAAA7YFL2AGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJQGA2DGNZQGA. You are receiving this because you were mentioned.Message ID: @.***>

[jvrabel88]

"Sorry, an error occurred while trying to access this service."

[cristianoag]

Can you please make sure you are cleaning the cache of the browser and teams client? Got other customers with the error and cleaning the cache solved the issue.

Get Outlook for iOShttps://aka.ms/o0ukef

---

From: jvrabel88 @.> Sent: Wednesday, March 20, 2024 6:01:08 PM To: cristianoag/microsoft-teams-apps-company-communicator @.> Cc: Cristiano Goncalves @.>; Mention @.> Subject: Re: [cristianoag/microsoft-teams-apps-company-communicator] Company Communicator stop working when use New Teams version (Issue #68)

"Sorry, an error occurred while trying to access this service."

— Reply to this email directly, view it on GitHubhttps://github.com/cristianoag/microsoft-teams-apps-company-communicator/issues/68#issuecomment-2010629893, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALSAPKTABFYY2KPM6I6SWUDYZH2JJAVCNFSM6AAAAAA7YFL2AGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJQGYZDSOBZGM. You are receiving this because you were mentioned.Message ID: @.***>

[jvrabel88]

Well it's been about a week since i made the change, i just checked teams on the web and it seems to be working in the new version, however the new teams version thick client is not working still. Both the web and the thick client were not working earlier, so i'm assuming that the thick client will work eventually as well. I'll keep monitoring. Thank you for the quick replies!

[cristianoag]

Please follow the instructions available in the following article to clean the teams client cache https://learn.microsoft.com/en-us/microsoftteams/troubleshoot/teams-administration/clear-teams-cache

It works on the client as well. It is just cache.

Get Outlook for iOShttps://aka.ms/o0ukef

---

From: jvrabel88 @.> Sent: Friday, March 22, 2024 10:02:25 AM To: cristianoag/microsoft-teams-apps-company-communicator @.> Cc: Cristiano Goncalves @.>; Mention @.> Subject: Re: [cristianoag/microsoft-teams-apps-company-communicator] Company Communicator stop working when use New Teams version (Issue #68)

Well it's been about a week since i made the change, i just checked teams on the web and it seems to be working in the new version, however the new teams version thick client is not working still. Both the web and the thick client were not working earlier, so i'm assuming that the thick client will work eventually as well. I'll keep monitoring. Thank you for the quick replies!

— Reply to this email directly, view it on GitHubhttps://github.com/cristianoag/microsoft-teams-apps-company-communicator/issues/68#issuecomment-2015058491, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALSAPKR7JHS3OGJNK5PV45LYZQTWDAVCNFSM6AAAAAA7YFL2AGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJVGA2TQNBZGE. You are receiving this because you were mentioned.Message ID: @.***>

[jvrabel88]

This worked, i must have been clearing the classic teams cache. I followed the instructions to reset the cache for new teams and it worked. Thanks again!