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.
Related
I was added to a Slack workspace by a coworker. I must've accepted something on the mobile app because I have access to the workspace there. Somehow, the desktop app never reflected this change and shows no sign of knowing about the workspace. I attempted to solve this problem by inviting myself to the workspace from the mobile app and accepting the invite link on the desktop app. I now have access to the workspace on the desktop app, but no direct messages have been carried over. (My desktop is Debian and mobile is iOS, if that makes any difference.)
I can't find any discussion about this on the Slack website or through a DuckDuckGo search... Does anyone know how to sync Slack from mobile to desktop? I will greatly appreciate any suggestions or direction. Thank you in advance!
This is not possible and despite the fact that this question was raised as soon people had two devices, Slack never agreed to address it.
On desktop I have no less than 15 workspaces.
A workaround that just worked for me was signing out of the desktop app and signing again. That allowed me see all the workspaces I was already in.
Here's a workaround (it is not ideal so I'm still searching for a better solution):
From the channel(s) I wanted to sync, on the mobile app, I added myself and now I have access to those channels on the desktop app. Unfortunately, I show up as two members with the same name...
I know this is an old thread, but I was struggling just now with the opposite problem: there was a Slack workspace that I could see in my computer but not in my mobile app. I write here how I solved it in case someone faces the same problem in the future.
In my case, it turned out that the problem was that I was using different email addresses for the different workspaces (either my professional or personal email), and I had pending to verify one of the addresses.
To solve it I:
Opened the Home menu by either sweeping right of tapping on the icon of the workspace I was in at that time
Went to Add a workspace
Saw that there was one email pending to confirm, so I confirmed it and immediately saw the missing workspace in my home menu together with the rest
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.
When I try to publish a release in the Google Play Console, I constantly get this error:
Your app cannot be published yet. Complete the steps listed on the Dashboard.
And yes, I have indeed completed all the steps listed in the dashboard. I am using the new Play Console Beta, this is possibly related. What do I need to do before I can publish a release? Is there a hidden step?
After some searching, I found the button 'Use classic Play Console'. Apparently there are some steps to be finished that are simply not visible in the Beta:
Click on Use classic Play Console
Go to Pricing & distribution
Check the Content guidelines checkmark
Check the US export laws checkmark
Press Save draft
And you're good to go!
I had that problem and fix it. the problem caused by google console because they added one additional task in the app content about wither your app is consider a news app or not. so go to the inbox in your app and you will find that message from google click and you will be leaded to the content that you should fill. I hope that help any one having that issue.
I also had this problem. It was regarding setting your app as free from the App Pricing section as my application was free. So after setting that, I released my app.
I am getting this error when I try to create a project in console.developers.google.com. I have 8 more projects left in my quota. I have tried different names and different project IDs. When I hit the "retry" button it shows the error after some time again.
UPDATE [Oct 9, 2017]: It looks like Google fixed the issue, since I was able to create a new project today.
I went ahead and attempted to create a new project in the Google API, and received the same error. This has occurred before with the Google API and is considered a temporary issue, often being fixed the same day. But if I remember correctly they have had it down longer in the past.
So the good news is, it's not something that is on your end, the bad news is, it's on Google's end.
If your google account is a Google Apps account (Google Suite, Google Apps, Gsuite, or whatever the Marketing folks are calling it these days), then you need to enable "Google Developers Console".
Login as an admin to admin.google.com
Go to Apps > Additional Google services
Find the "Google Developers Console" line item and set to "ON for everyone" (or whatever).
That should do it.
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).