So we are currently building a bot / app for Microsoft Teams and have based our query/search messaging extension on this code sample: https://github.com/microsoft/BotBuilder-Samples/blob/master/samples/javascript_nodejs/50.teams-messaging-extensions-search/bots/teamsMessagingExtensionsSearchBot.js
This works fine on the desktop client of Teams when we post a NEW conversation (selectItem is invoked correctly). When using this for a reply however, after selecting the entry, the reply area just closes and does not render any card... Also, on Teams mobile (latest Android version), selectItem is never called. There is a button to expand the card but it's not working..
I could live with mobile not working as expected, though having it this broken in replies is making the selectItem basically useless..
Thanks
This is a known issue. We already have a bug on this which is being tracked. Thanks!!
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.
Recently, our (published) app stopped working on mobile, with the above message, "This tab is not available on mobile". The app is a custom teams tab basically.
What can be causing this issue?
From our side, we have not changed anything (neither in the manifest nor in the hosting).
Are there some changes in the teams policy or maybe some new requirements or changes?
In the desktop/web client the app works like it did before. On the mobile, if you try to click a link to the app tab, it shows this notification tooltip "not available on mobile" instead of opening the tab.
Manifest version: 1.9
"#microsoft/teams-js": "^1.12.1",
Not sure, if the versions are related, the mobile client shows that tooltip without even trying to open the tab.
It looks like the problem appeared with some latest update of the Teams client. The app is still working fine with Teams client from June 2022, but starts showing this message "tab is not available on mobile" if the Teams mobile client is updated to the latest version.
I have noticed that now there is a button to "Add an app.." in the teams app on mobile. Are there some new requirements for existing apps because of this maybe (so that existing apps won't work on mobile unless adapted)?
Related observation: all app tabs created disappeared on "More..." tab after mobile teams client is updated
Appreciate any insights what might be causing the issue?
Posting the solution here from the linked issue if somebody else faces it. The message was appearing because websiteUrl property was not set in the tab configuration. It is now required for the tab to appear in the mobile client. Setting this property in the tab configuration resolves the 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 used app studio from MS Teams to creat a manifest for a Bot App. I've uploaded the full color picture as well as trasparent outlone. However the icon is not displaying at the chat window. Only the default icon is visivle.
Any ideas, how can I solve the issue? Thanks a lot!
Is your bot sideloaded or uploaded to your organization's private app store? In those cases, the image used for the bot in the chat window is taken from the bot registration in Bot Framework. (This is a known issue that we're tracking.)
To change your bot's icon:
If you registered your bot using App Studio:
Go to https://dev.botframework.com/bots and sign in with the same account you use in Teams
Select your bot, then go to Settings
Click on "Upload custom icon"
If you registered your app using the Azure portal:
Go to the Bot Service or Bot Channels Registration resource in Azure
Go to Settings
Upload a custom icon
As #Adrian Solis answer is indeed correct, I just wanted to add that it can also be related to caching issues. If you are changing icons and want to check if everything is working as expected, you can delete your browsers cache or the cache of the Microsoft Teams Windows App.
The Microsoft Teams Windows App has the following cache folders. Just stop the app, delete everything in this folders and start it again.
%appdata%\Microsoft\teams\application cache\cache\
%appdata%\Microsoft\teams\blob_storage\
%appdata%\Microsoft\teams\Cache\
%appdata%\Microsoft\teams\databases\
%appdata%\Microsoft\teams\GPUcache\
%appdata%\Microsoft\teams\IndexedDB\
%appdata%\Microsoft\teams\Local Storage\
%appdata%\Microsoft\teams\tmp\
For example in this demo: http://demos.telerik.com/kendo-ui/scheduler/index
On a desktop browser, clicking on the event opens an editor. On a mobile touch device, tapping on the event does nothing. This repros also when running Chrome device emulation as iPhone.
Telerik claims that this works here:
http://www.telerik.com/forums/creating-or-editing-event-in-mobile-browser
so I don't understand how they can make that claim.
Can someone please confirm that this does not work, or if I'm doing something wrong? I am just evaluating their product at this stage, so I do not have paid support subscription required to reply on that forum thread.
I figured out the answer to my question. On mobile devices, the scheduler needs to be configured for mobile using mobile:"phone" or mobile:"tablet", as well as instantiate a kendo.mobile.Application.
Here's an example: http://dojo.telerik.com/#ggkrustev/uCiNU