-
Notifications
You must be signed in to change notification settings - Fork 520
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
Problem reaching the app - error shown when navigating to bot personal app #4249
Comments
Hi siduppal! 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 |
Suggested workarounds for this issue: utilizing the app in web browser, popping out the 1:1 chat, or using mobile Teams client. |
I had the same issue before |
same. |
Same here. Looking for the solution soon. Thank you |
Hello, is there any official Microsoft document or statement regarding this? There is no confirmation available anywhere about when the fix is available? |
Do you know if there is any official Microsoft update on this? I don't think the correct updates are provided on this page |
I just opened a ticket. |
Do you have the ticket number from Microsoft |
I've only gotten to the part where they make me do all the work and do not read my ticket.
|
|
Bug still here |
I dont blame them. The agents are doing their job and the best they can. They are providing us the information they have and can't do anything more. And as far these questions are concerned i don't see anything wrong with it, its their job to ask the questions to determine the root cause and if we submit a ticket we should be also ready to help them in order to receive the assistance. |
That is a fair response and a good update, at least we have a timeline now. Your agent is really good as compared to mine who just said this is an ongoing issue. |
Did anyone get the fix? I know there is one more day left, I am still having the problem here, getting a little bit nervous since I didn't get the updated fix yet, do I need to do anything to get the fix? Thanks! |
Same problem here. A lot of users affected. Need this fix ASAP 🙏 |
A number of our users are also experiencing this same problem, which is poor timing since we just released our app to the marketplace and it makes it seem as though it's a bug in our app. A speedy fix would very much be appreciated! |
Same here, have to keep explaining to the client it is not a bug from us, very frustrating. |
I just restarted my client and the problem went away for me! I'm still checking with other users that were affected by the bug. Can any of you still repro? Just curious. |
Same here, I should have checked it before the restart, but I restarted it, and no more issue. |
Still having issues here. The annoying pop up is gone, but the rendering issues are still a problem. This adaptive card rendered fine on the desktop client before this issue began. Just for clarification, the text is purposely pixelated for privacy, The issue is with the squishing of the first column. |
I tried to restart app just now and it didn't help. When should we expect the fix? It affects hundreds of thousands our users |
Also still an issue at a customer tenant in EMEA (West-Europe) . Is there any update on the progress? |
Issue is fixed for both of our EMEA customers, thank you. |
Issue is still reproduced in East Europe (Ukraine) |
We received the following : Scope of impact: The issue affects most customers and may affect any user interacting with bots in the affected Microsoft Teams desktop client version. |
@Bizjes - Thanks a lot for confirmation. |
What should be the users actions after the fix will be applied? Update Teams client / Restart Teams or relogin? Or the issue should be gone without any extra actions? |
The fix for the issue causing "There was a problem reaching the app" error has just finished rolling to 100% of production. Teams desktop client will automatically pull the latest build after a period of inactivity, but you can also try doing Check for updates. Please do not hesitate to reach out to us here on GitHub if you encounter any other issues while developing and running your apps. |
Tell us about your experience!Hi siduppal! This issue is closed in our system. We would like your feedback on your experience with our support team and Platform. Best regards, |
Yeah, still not working. Again, the error message is gone but the rendering is still messed up. The two happened at the same time so I assumed that they were related. Do you have another tracker that we can follow the rendering fix? |
@v-chetsh - Best scenario is that a simple restart fixes the issue. But currently I have people on the tenant testing a restart + cache clear. I have yet to receive confirmation if this is now solved. |
@Bizjes - Microsoft Teams platform engineering team confirmed that fix is rolled out 100%. Could you please update your desktop client using "Check for updates" option? If you are still facing this issue please share your Teams client version. |
Same issue with Web and Teams Desktop Bot Error is it still continued issue ? |
We got confirmation that the fix was deployed. Our customer also confirmed this. |
There is an ongoing issue in Teams that is causing some users to see an error ("There was a problem reaching the app") when navigating to the bot personal app from flyout. The fix has started rolling out to all users and is expected to finish rollout by early next week unless some unforeseen issues are encountered (ETA Oct 11).
Creating and pinning this issue for awareness.
Screenshot of the error:
![image](https://user-images.githubusercontent.com/7799064/135512344-1d217562-4d5c-4198-a229-e3abd7654277.png)
Note that the compose box is functional and the messages can be sent and received.
The text was updated successfully, but these errors were encountered: