Company Communicator - Messages queued after New Teams 2.1 Upgrade.

[saranRK05]

Initially it throwed an error while accessing CC app on new teams.

After following the below instructions mentioned in the article #68 , the issue with accessing CC got fixed. BUt was unable to edit and exisging Draft message also when sending a new message, it gets struck with status queued. Trid to sync Function apps and restarted App services with no luck.

Instructions Followed:
Change the git branch to App service. To below values
• Disconnect the repo and update to
External Git
Repository: https://github.com/cristianoag/microsoft-teams-apps-company-communicator.git
Branch: From master to master-v5.31

• Perform this change on :
	AppService
	RTLearningHub-data-function
	RTLearningHub-function
	RTLearningHub-prep-function
• Wait for 30 mins and resyn the service. 
• Open Front Door and CDN profiles and navigate to Front door designer

Change routing rule to disable Routing Rule 2

[saranRK05]

@luishdemetrio luishdemetrio - Any thoughts on this?

[cristianoag]

@saranRK05 - Can you create and send a new message? What version did you have previously when the draft was created?

[saranRK05]

@cristianoag - Yes, created a new message and its getting Queued. With regards to message struck in draft it was created with Teams Classic with CC branch: master. Any advise?

[cristianoag]

Queued and delivered or just queued forever? Can you move to master-v5.31 instead? CC branch master in this repo or the official repo? Get Outlook for iOS<https://aka.ms/o0ukef>

…

________________________________ From: saranRK05 ***@***.***> Sent: Friday, March 22, 2024 11:32:40 AM To: cristianoag/microsoft-teams-apps-company-communicator ***@***.***> Cc: Cristiano Goncalves ***@***.***>; Mention ***@***.***> Subject: Re: [cristianoag/microsoft-teams-apps-company-communicator] Company Communicator - Messages queued after New Teams 2.1 Upgrade. (Issue #77) @cristianoag<https://github.com/cristianoag> - Yes, created a new message and its getting Queued. With regards to message struck in draft it was created with Teams Classic with CC branch: master. Any advise? — Reply to this email directly, view it on GitHub<#77 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ALSAPKVEAOLVDJ4WFORMKOTYZQ6IRAVCNFSM6AAAAABFBLPABWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJVGIZTGMJVGQ>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[saranRK05]

Just queued for ever, Also this happened after changing it to branch master-v5.31.

[cristianoag]

I would say keys may be incorrect or the sync may have issues. Need to check those. Get Outlook for iOS<https://aka.ms/o0ukef>

…

________________________________ From: saranRK05 ***@***.***> Sent: Friday, March 22, 2024 11:50:43 AM To: cristianoag/microsoft-teams-apps-company-communicator ***@***.***> Cc: Cristiano Goncalves ***@***.***>; Mention ***@***.***> Subject: Re: [cristianoag/microsoft-teams-apps-company-communicator] Company Communicator - Messages queued after New Teams 2.1 Upgrade. (Issue #77) Just queued for ever, Also this happened after changing it to branch master-v5.31. — Reply to this email directly, view it on GitHub<#77 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ALSAPKV727GQQVQSGZTNIZTYZRAMHAVCNFSM6AAAAABFBLPABWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJVGI3DSMZWGU>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[saranRK05]

Can see this message on all three function apps.

[cristianoag]

Ouch. Now I know what is going on. I guess you upgraded to v5 without changing the function framework. Here is what you need to do:

1. Run the script https://github.com/OfficeDev/microsoft-teams-apps-company-communicator/blob/main/Deployment/dotnet6-migration.ps1 to migrate your functions and App Service to .Net 6.
2. Make sure you change the runtime version for all functions to ~4. You can do that after running the above script on Configuration->Function Runtime Settings.

[saranRK05]

@cristianoag - Thanks, Let me check and revert.

[saranRK05]

@cristianoag - Thanks for your update, it worked after performing above suggested steps.