New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SDK initialization timed out #2298
Comments
Hi @sschoeb , I'm sorry that you've run into this problem. Would you mind sharing an example from your code of the |
Thanks for your reply @TrevorJoelHarris Sure, this is what we do:
As this is an angular app, we call initialize() within the ngOnInit method. |
Oh, one other quick question. I am assuming you are seeing this in Teams on a desktop browser. Is that true? If not and you're reproing in some other host or platform please let me know! |
Hello @sschoeb - Please confirm the above details and let us know if you are facing this issue in New Teams client? |
@TrevorJoelHarris Thanks for the feedback. I'll enable the client side logging and will come back here as soon as I've detailed logs. Yes, looks like all reports are on Desktop (not yet sure about the version, but I try to figure that out as well) |
I'm going to close this due to inactivity, but please feel free to reopen or open a new issue that includes client logs and someone will be happy to hop in and take a look for you! |
@TrevorJoelHarris Takes a while till I have that stuff deployed properly to get the logs. Will reopen the task as soon as I've proper logs. Thank you very much for your help up to now! |
We are using the version 2.20.0 of the teams-js library.
We see more and more the following error reported in our app:
SDK initialization timed out.
There were already two of this issues in this repo:
#1894
#1681
Both of these are closed. But this is definitely not fixed. We currently even implemented a retry, but does not help either.
What does microsoft expect from us to do if we get this error from the framework? Should we show an error to the user?
here the callstack:
Do you need any additional information?
The text was updated successfully, but these errors were encountered: