search

OfficeDev / microsoft-teams-library-js

JavaScript library for use by Microsoft Teams apps
https://docs.microsoft.com/microsoftteams/platform/
Other
430 stars 199 forks source link

Initialization of “app” from “@microsoft/teams-js” is timing out #1181

Open shubh30126 opened 2 years ago

shubh30126 commented 2 years ago

version: “@microsoft/teams-js” : "2.0.0-beta.4-dev.9" Error thrown: Teams js method app.initialize() Error: SDK initialization timed out. User Agent of Popup window: Mozilla/5.0 (Macintosh; Intel Mac OS X 12_2_1) AppleWebKit/537.36 (KHTML, like Gecko) Teams/1.5.00.4683 Chrome/85.0.4183.121 Electron/10.4.7 Safari/537.36

ghost commented 2 years ago

Hi shubh30126! Thank you for bringing this issue to our attention. We will investigate and if we require further information we will reach out in one business day. Please use this link to escalate if you don't get replies.

Best regards, Teams Platform

Meghana-MSFT commented 2 years ago

We are looking into this issue, we will update you.

laduma-adamc commented 2 years ago

Is there any more follow up to this? We are having the same issue on almost all Windows clients.

version: “@microsoft/teams-js” : "2.0.0-beta.7" Error thrown: Teams js method app.initialize() Error: SDK initialization timed out.

laduma-adamc commented 2 years ago

Since updating to stable V2.0.0 we are still having this issue.

Meghana-MSFT commented 2 years ago

Could you please confirm if you are using this one - https://www.npmjs.com/package/@microsoft/teams-js ?

laduma-adamc commented 2 years ago

Could you please confirm if you are using this one - https://www.npmjs.com/package/@microsoft/teams-js ?

Yes we are.

We have also refined when the issue is timing out. This only happens in the authorise part of the teams app, in the pop-out modal for logging into our SaaS platform.

If we are in a meeting, and in a side panel, or in a shared meeting stage, we reliably call the app.initialize() in our final stages of loggin in in the modal, it will work really quickly.

If however we are in a content page, or in the configure page, when we add our app to the meeting, then it times out and says that the action was canceled by the user.

Thanks.

Meghana-MSFT commented 2 years ago

Thank you for the details, we will update you soon.

Meghana-MSFT commented 2 years ago

We tried this at our end with the CDN link and it seems to be working fine, are you using it through CDN link or importing the modules?

AE-MS commented 2 years ago

Hi @laduma-adamc, we've been looking into your issue and I was hoping you could provide a few more details that might help us reproduce the problem to identify the issue.

If I understand correctly, in your app you call authentication.authenticate to a custom page in your app, which then redirects to a login page for your SaaS platform. After logging in, the SaaS platform site redirects back to your custom page (still executing in the popout) and that page tries to call app.initialize(), and in certain circumstances that call times out.

Do I have that flow correct?

And am I correct that the only circumstances in which that call to app.initialize() times out is when your app is running from a personal tab (the contentUrl value in the staticTabs section of the manifest) started from the app bar on the side of teams, or a configuration tab (the configurationUrl property in the configurableTabs section of the manifest)?

laduma-adamc commented 2 years ago

@Meghana-MSFT we are importing the modules to use in a React application, hosted in azure static webapps.

@AE-MS

  1. we import authentication from the @microsoft/teams-js package, and call authentication which loads an inital auth start page that is part of our teams application (still in the popout),
  2. The poput then redirtects to our login page for our SaaS platform, which logs the user in.
  3. Then redirects back to our teams application, to finalise the login process.
  4. In the finalisation page, still in the popup, we load app from the @microsoft/teams-js package, and call initialize()
  5. At this point is when it it is failing to initalise, and we have a timeout after 5 seconds.

Currently this only happens if you attempt to log into the application from the configurableTabs configurationUrl and the content view in a meetings details page. We dont have any personal tabs or channel tabs yet in our application, only a meeting extension, and it is usable in the Side Panel, Shared Meeting Stage, and the Details page.

thanks, Adam

shubh30126 commented 2 years ago

@Meghana-MSFT Any update on this?

AE-MS commented 2 years ago

@Meghana-MSFT we are importing the modules to use in a React application, hosted in azure static webapps.

@AE-MS

  1. we import authentication from the @microsoft/teams-js package, and call authentication which loads an inital auth start page that is part of our teams application (still in the popout),
  2. The poput then redirtects to our login page for our SaaS platform, which logs the user in.
  3. Then redirects back to our teams application, to finalise the login process.
  4. In the finalisation page, still in the popup, we load app from the @microsoft/teams-js package, and call initialize()
  5. At this point is when it it is failing to initalise, and we have a timeout after 5 seconds.

Currently this only happens if you attempt to log into the application from the configurableTabs configurationUrl and the content view in a meetings details page. We dont have any personal tabs or channel tabs yet in our application, only a meeting extension, and it is usable in the Side Panel, Shared Meeting Stage, and the Details page.

thanks, Adam

Thanks for providing the extra detail. I double-checked that my attempt to reproduce the problem matched what you are doing, but unfortunately, I was not able to reproduce the issue. As a result, I'm about to publish some instructions for you on how to enable logging so you can run your scenario with logging on and we can use that to try and troubleshoot. Be back with those instructions within a day!

laduma-adamc commented 2 years ago

Thank you very much, looking forward to it.

AE-MS commented 2 years ago

I've published a page about how to enable TeamsJS logging. Could you enable logging and run your scenario again to see if there's any obvious errors coming from the logs? If you are comfortable doing so, could you share your TeamsJS logs? Please be sure to remove any personal/sensitive information/authentication tokens from the logs if you share them. Thanks!

Meghana-MSFT commented 2 years ago

@Meghana-MSFT Any update on this?

Engineering team is looking into it.

laduma-adamc commented 2 years ago

Hi,

Please find attached two sets of debug logs, app_page.txt are the logs from the page we launch the auth window from, and auth_page.txt are the logs from the auth window.

app_page.txt auth_page.txt

Thanks,

AE-MS commented 2 years ago

Hi,

Please find attached two sets of debug logs, app_page.txt are the logs from the page we launch the auth window from, and auth_page.txt are the logs from the auth window.

app_page.txt auth_page.txt

Thanks,

Thank you so much for providing the logs! Using the information from them, we have some idea what might be going on. We are investigating and will get back to you ASAP.

laduma-adamc commented 2 years ago

Thanks,

Any more help that you need, please let me know, we are being held up by this issue.

Thanks.

AE-MS commented 2 years ago

Just wanted to let you know that we're still looking to ensure we have the right people investigating the problem so we can get to the bottom of the issue. @nwojod-MSFT is working to find the right contact and can update this issue.

nwojod-MSFT commented 2 years ago

@laduma-adamc we did get in touch with the right team and they are still investigating the problem. I will update this thread once I get an ETA for resolution.

shubh30126 commented 2 years ago

@nwojod-MSFT Any update on this?

nwojod-MSFT commented 2 years ago

Hello @shubh30126, I am yet to get any update from the team. The team raised an incident report and are currently working on resolving the issue; however, no ETA has been given.

nwojod-MSFT commented 2 years ago

@laduma-adamc and @shubh30126 got an update from the team, unfortunately, the issue has a proposed fix in Electron 16 based Teams. The current estimate for rollout on Windows is end of September.

shubh30126 commented 2 years ago

@nwojod-MSFT Do we have an ETA for Mac based Teams App as well?

nwojod-MSFT commented 2 years ago

@shubh30126 Mac will likely rollout before Windows. ETA for Mac is end of August.

CKGHarju commented 2 years ago

I am leaving this here if it might be any help to @nwojod-MSFT AE-MS Meghana-MSFT for narrowing down the issue, which seems to be network related?

@shubh30126 I've encountered the same error with the authentication flow both on Windows 10 and and Mac. On the last page of the authentication flow when calling microsoftTeams.app.initialize it timeouts and we get the following error Error: SDK initialization timed out, preventing us from ever reaching microsoftTeams.authentication.notifySuccess.

clarification edit. this problem occured when running teams in the desktop electron application. When running teams directly from the browser the timeout does not occur for me.

I've tried every trick I could think of without success. Weirdly when passing our application zip file to my coworkers (working on different networks) they would not encounter the same error.

I managed to resolve the issue on my clients when switching to a different network.

tiennguyen1293 commented 2 years ago

i'm facing this issue.

You have Microsoft Teams Version 1.5.00.19359. It was last updated on 11/08/2022. "@microsoft/teams-js": "^2.2.0"

guillaumemeyer commented 2 years ago

Got the same issue here. Any news @nwojod-MSFT ?

guillaumemeyer commented 2 years ago

@laduma-adamc @tiennguyen1293 , were you able to find a solution on your side? Or you're still waiting for a fix from MS?

tiennguyen1293 commented 2 years ago

i was downgrading"@microsoft/teams-js": "1.11.0" and it's working, but still need to fix it asap, if we want to using teams SDK v2.

guillaumemeyer commented 2 years ago

Be careful @tiennguyen1293 . As the Teams client is being upgraded to Electron 16, teams-js v1.x is already not working anymore on certain Mac desktop clients, and Windows soon (despite anything you can read about compatibility for deprecated methods of the SDK...).

nwojod-MSFT commented 2 years ago

@guillaumemeyer , @tiennguyen1293 Mac rollout for E16 version is 100% and Windows is still about 50%. The same estimate for 100% Windows is end of September. You should be able to update your Mac client to get the E16 version.

AE-MS commented 2 years ago

Be careful @tiennguyen1293 . As the Teams client is being upgraded to Electron 16, teams-js v1.x is already not working anymore on certain Mac desktop clients, and Windows soon (despite anything you can read about compatibility for deprecated methods of the SDK...).

Hi @guillaumemeyer! Could you provide some more details about which functionality in TeamsJS currently marked as deprecated is not working anymore? Ideally if you could open a new github issue with an example, we could use that to investigate. Any deprecated methods still in the SDK remain supported and if you've found deprecated methods that have stopped working, we would treat that as a bug to be fixed. Thanks!

tiennguyen1293 commented 2 years ago

Hi teams, any update on this issue, I'm waiting to implement Teams v2. :(

sumit12690 commented 2 years ago

Hi team, is there any update on this issue? I am facing the same issue in ms-teams SDK version 2.3.0.

Screenshot Attached

Screenshot 2022-09-27 at 3 44 57 PM
sumit12690 commented 2 years ago

@AE-MS , @Meghana-MSFT : Can you please let me know the ETA of the this issue?

Meghana-MSFT commented 2 years ago

@sumit12690 - Please refer https://github.com/OfficeDev/microsoft-teams-library-js/issues/1181#issuecomment-1224136708. Thank you.

sumit12690 commented 2 years ago

@AE-MS , @Meghana-MSFT : Can you please let me know the release date of the new version?

NuxXDev commented 2 years ago

@laduma-adamc and @shubh30126 got an update from the team, unfortunately, the issue has a proposed fix in Electron 16 based Teams. The current estimate for rollout on Windows is end of September.

@AE-MS What is the status of the Teams Electron 16 release for Windows? September has now passed and there is still no fix for this issue.

nwojod-MSFT commented 2 years ago

@sumit12690, @NuxXDev, got new update. The team encountered a problem that needs to be resolved before the fix can be released. Release for Windows is expected in coming days, but no exact date yet. I will update this thread once the release date is finalized.

Alcip commented 2 years ago

@nwojod-MSFT any update on the issue? More and more users are facing this issue.

nwojod-MSFT commented 2 years ago

@Alcip the rollout is currently 75%. The team is anticipating 100% rollout by end of week if no new issues are identified.

NuxXDev commented 2 years ago

My Teams Windows Client updated to Version 1.5.00.28361 / Electron 16.2.8, does this mean it should have the fix? I haven't verified yet.

For anyone wondering how to get the Teams Electron Version to display, you have to LEFT click on the Teams Icon in the systray fast about 8 times to enable the debug menu, then right click and select "Get Electron/ Slimcore Version"

Alcip commented 2 years ago

have received an update here is the version You have Microsoft Teams Version 1.5.00.28567 (64-bit). It was last updated on 21/10/2022. And I'm still seeing the issue.

nwojod-MSFT commented 2 years ago

@Alcip thank you for the update. Please can you provide a snippet of the error message you are seeing? I will share this information back with the engineering team to identify why the issue persists. Thanks

cgvalayev commented 2 years ago

Hey @nwojod-MSFT can you please let us know starting with which Teams version the fix is applied? Also, is restart or reinstall of the Teams desktop app required?

nwojod-MSFT commented 2 years ago

Hi @cabevavy the team is still running some tests to ensure the issue is resolved for all users. The current version of Teams to have this fix is 1.5.00.28567, and Electron 16.2.8. Last updated 11/1/2022.

cgvalayev commented 1 year ago

Can't tell how many people got update but the issue doesn't seem to go away:

image
miron4dev commented 1 year ago

Hi @nwojod-MSFT

The issue is still reproducible for 1.5.00.32154, last updated on 18.11.2022. Setup: macOS Monterey 12.5.1 "@microsoft/teams-js": "^2.5.0"

ms.app.initialize().then(() => ms.authentication.notifySuccess())

The issue is blocking us from upgrading to SDK 2.x

zaishuiyufang commented 1 year ago

Hi @nwojod-MSFT I'm also facing this problem，The issue is blocking us from upgrading to SDK 2.5.0 image However, the problem that I downgraded to version 1.10.0 can be solved.