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.
Related
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.
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.
I'm trying to make a MS Teams app using the following guide: https://learn.microsoft.com/nl-nl/learn/modules/embedded-web-experiences/3-exercise-create-custom-teams-personal-tab
I managed to add my app to MS Teams and got it to work.
However, when I updated the code, deleted the app in MS Teams and tried adding the updated version, it would give me a Something went wrong notification.
Now, I'm not able to open the App Studio app or the Apps page. It'll just non-stop load, but nothing shows up.
Things that I've tried
Restart MS Teams
Restart MS Teams in admin mode
Under %AppData%\Microsoft\Teams clear the following folders: blob_storage, Cache and GPUCache
Expected result
When I click the Apps button, the Apps page should open and show me all the apps, so I can navigate and add my own custom app.
Actual result
Pressing App Studio button does nothing. The button will be in a "pressed" state, but nothing shows up
I'm experiencing this also - my suspicion is Teams is being affected by the very large volume of users working remotely, and certain portions are being, let's say, "stress tested" more than usual.
I'm getting logged out of all Google services a set period after opening the browser or logging in, it's about 20 minutes, maybe less. Occasionally the log in page will automatically redirect to a "clear cache and cookies" help page, however following the instructions on this page changes nothing and a short time later it logs me out again. This is particularly annoying when writing a response to a review on the Google Play Developer Console, because as soon as it detects being logged out it greys the text box so that it's not possible to copy and paste the message and it is not saved as a draft, it has to be written again. It's important to note this happens regardless of the browser being used and regardless of whether or not you are logged in on multiple devices. This is something Google really need to fix. Has anyone else suffered these problems?
It appears I've found a solution, as an Android app developer I always have a bunch of tabs open such as Google Play Developer Console for reviews and statistics and Google Wallet for financial reports. It turns out the problem is related to Google Wallet because if I close this tab, it won't log me out of all Google services. It appears this is a bug with the Google Wallet service. So to clarify this is a bug with Google Wallet, so if you're experiencing this problem like me, always close this tab after viewing the reports (the one launched from the Play console under financial reports).