This question already has answers here:
MS Teams App: There was a problem reaching this app
(2 answers)
Closed 7 months ago.
I have a C# botframework bot that I have been debugging and at some point received the error: There was a problem reaching this app -Retry-. Pressing -Retry- does nothing and now that error permanently takes up half of the chat window with the bot. I've read other people experiencing this with tabs pointing to a fix within the manifest file changing the loading indicator but this does not change the behavior. There is another issue with pinned apps: How to avoid There Was a Problem Reaching This App Error When Launching Pinned App from Teams Desktop Client ... but no apparent resolution yet. Anyone have suggestions? Thanks!
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 is expected to begin rolling out on October 4th and reach 100% by October 8th.
Tracker: #4249
Suggested workarounds for this issue: utilizing the app in web browser, popping out the 1:1 chat, or using mobile Teams client.
Related
We developed an app for MS Teams that utilizes a bot to interact with users.
One of the cards the bot sends includes a button that opens a chat with another person and fills in a default message. This is the form of the button URL:
https://teams.microsoft.com/l/chat/0/0?users=someone#email.com&message=Hello
It used to work well in the past year and in the last couple of weeks, all of the sudden, it seemed to have stopped working. What happens is, that a new chat is opened with the user as expected, but the message is not filled.
After a short investigation, we discovered that when inputting the URL above directly to the URL bar in the browser - it does work, and the default message appears. Moreover - if go and click on the button in the bot - it will now work as expected and fill the default message. This will continue working until we refresh the page - then it stops working again.
Feel free to watch this screen recording demonstrating the issue (sorry for the foreign language in the first 10 seconds 😅): https://myquestworld-my.sharepoint.com/:v:/g/personal/roy_myquest_co/EWGmLFZ49r5KlurOsMBeXIYBU1gBmhHmL2n-Cbo144JsOQ?e=2lXKAW
We contacted Office 365 support, and they directed us to this forum. We believe this is a bug in MS Teams, but so far we're not able to get MS to do anything about it.
Does anyone else experience this issue? Anything we can do about it?
Any advice would be appreciated.
When we open the Teams applications with a chat the auto-suggestions menu is automatically opened.
Are there any way to disable it?
We tried it for few different MS Teams apps and it is reproduced for all.
It is reproduced in ~90% cases.
We started facing it recently and didn't remember such behaviour before.
Steps to reproduce:
Open app with chat
Expected result:
Auto-suggestion menu is not opened
Actual result:
Auto-suggestion menu is opened
This seems to be expected behaviour of Bot having commands. These bot commands will pop up automatically. There is no way to disable it
Starting ~2 weeks ago (around Sep 14th, 2021) many of our customers have started to report problems launching any PINNED apps from their desktop teams client. Web chat Teams client can launch pinned Apps fine. Apps are pinned as part of a set up policy in Teams Admin Portal, in this case a Global Set up Policy.
Jira App is shown below as an example but it is happening for all pinned aps, at least ones with a chat tab (bot).
If you click on the ... below the app list on the left navigation rail and launch the app in that manner the error goes away.
The error does not prevent messaging to and from the app, just that it stop the users since they believe there is a problem. Clicking on retry does not do anything.
Are there any recent changes to Manifest files that may need to be addressed to avoid this pop over error?
Previous articles from Feb had recommended disabling Loading Indicator in Manifest files. That does not seem to have any impact on this situation.
This issue is being tracked on github. Please visit this for updates on Problem reaching the app issue.
I've been working on a Microsoft Teams app, and have been using the conversationUpdate message type that should be triggered whenever the app (or a user) is added to a team to send a welcome message. I am using the upload a custom app feature that Microsoft Teams has to upload the app.
For some reason, when I add the app to the team I want it on, the conversationUpdate message has never fired for me on the first attempt. No error message or warning of any type. It doesn't work until I go to the team I just added the app to, click the ellipses for the team and go to manage team, click apps, and remove the app I just added, then add the app again to the team. Only then do I get the correct conversationUpdate message that I can use to send out a welcome message.
I've tested out various bots written by Microsoft in their BotBuilder samples here: https://github.com/microsoft/BotBuilder-Samples/tree/main/samples/javascript_nodejs and have gotten the same result as my custom bot. I don't know why this error occurs and if it is isolated to an app uploaded with the upload a custom app feature.
Does anybody have insight as to why this is happening and if it happens on the Microsoft Teams App catalog as well?
I eventually figured out what the issue was. It would work the very first time I added the bot to a Team, but when I removed it, I was removing it from the Apps -> Built for your org only and not also removing it from the individual Team I had added it to. For some reason, when I did it this way, the first time I added the bot back in it would not trigger the conversationUpdate activity. Presumably because it thought that it was added to that Team still. Not sure exactly why, but that's what is happening.
I've updated the icon for my bot in the Azure portal about 35 hours ago, but it's still showing the old one for new messages sent from the bot. Surely it should have changed by now? Is there any issue with this currently?
It's correct in the Azure portal in the "Test in Web Chat", but Teams is still showing the old icon, even for new messages.
Update:
It's been a few days now, and the image finally changed, but now it's totally corrupted. Is there a way to see what's wrong with my PNG? Is there an issue with the bot framework/Teams of some sort? See images below:
Error:
Original Icon (I don't know if SO changes the file in any way, but presumably not)
Update: I've now modified my bot in the Azure portal to use the exact same icon as another bot which is working fine, and it's still broken, so I'm thinking there is an issue with the bot framework/Teams in some way at the moment.
What I've encountered from experience is that when updating the bot's info in "Bot App Registration" such as icon and display name.
You can either wait a couple days and see if it fixes itself.
I've consistently been able to get it to update sooner by logging in and out of Teams as well as closing it.
I have a feeling that it's related to the cache since Teams is built with Electron. Some other post mentioned this and there's no "official" surefire way to do this. Playing with the manifest also does not seem to affect it to update sooner.
TL;DR
Log in and out of Teams, close it. If using web version, clear the cache. Log back in.
Good luck!
Try reinstalling the application on Teams, sometimes it takes time.