cristianoag / microsoft-teams-apps-company-communicator

Company Communicator app template
MIT License
16 stars 38 forks source link

Company Communicator - Messages queued after New Teams 2.1 Upgrade. #77

Open saranRK05 opened 6 months ago

saranRK05 commented 6 months ago

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

After following the below instructions mentioned in the article https://github.com/cristianoag/microsoft-teams-apps-company-communicator/issues/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 commented 6 months ago

@luishdemetrio luishdemetrio - Any thoughts on this?

cristianoag commented 6 months ago

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

saranRK05 commented 6 months ago

@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 commented 6 months ago

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 iOShttps://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)

@cristianoaghttps://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 GitHubhttps://github.com/cristianoag/microsoft-teams-apps-company-communicator/issues/77#issuecomment-2015233154, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALSAPKVEAOLVDJ4WFORMKOTYZQ6IRAVCNFSM6AAAAABFBLPABWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJVGIZTGMJVGQ. You are receiving this because you were mentioned.Message ID: @.***>

saranRK05 commented 6 months ago

![Uploading queued.JPG…]() Just queued for ever, Also this happened after changing it to branch master-v5.31.

cristianoag commented 6 months ago

I would say keys may be incorrect or the sync may have issues. Need to check those.

Get Outlook for iOShttps://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 GitHubhttps://github.com/cristianoag/microsoft-teams-apps-company-communicator/issues/77#issuecomment-2015269365, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ALSAPKV727GQQVQSGZTNIZTYZRAMHAVCNFSM6AAAAABFBLPABWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMJVGI3DSMZWGU. You are receiving this because you were mentioned.Message ID: @.***>

saranRK05 commented 6 months ago

image Can see this message on all three function apps.

cristianoag commented 6 months ago

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 commented 6 months ago

@cristianoag - Thanks, Let me check and revert.

saranRK05 commented 6 months ago

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