I'm having trouble with microsoft chatbot on skype. The chatbot on skype not updating to latest bot I published from the visual studio. Here some screenshot of that.
Emulator Version (The right one, the test chatbot from the developer portal is the same response as this)
The skype version (The response is from my old version of chatbot script)
This is the ngrok inspection (all 200, In other word it's getting to the server, though it's wrong)
The AppID is e1425cb5-f16e-4c64-80d7-82b29d742268 and I've tried it from azure, too. The response is the same and for additional information the channels are not yet published + skype is up to date. Anyone get this strange bug too?
EDIT 1: Additional Information
After I use some breakpoint. The skype and emulator both catch the breakpoint on this one.
The strange things is, the skype one catch on this scripts (SimpleDialogFxm) which is my old one.
While the emulator one is catch on the right scripts (SimpleDialogue).
Try sending a /deleteprofile message to the Skype bot. It might be possible the the Skype bot is relying on the dialog state.
By sending that message you will force the bot to delete all the information in the data bags.
I had similar issues. The solution was to remove the bot from Skype contacts list and add again.
Also note, that the bot is not updated on Skype when we change it's name, profile picture or description. Seems it's a bug.
Related
I'm running a Telegram network where I post discounts from Amazon on a daily basis.
Now this is the problem: when I click on the links from my smartphone, they don't always open the Amazon app, but sometimes Telegram opens the page in its in-app browser. And that's a problem for me because users would never finalize a purchase by logging in again on Amazon from the Telegram browser - of course they go open the Amazon app and buy from there, and I get no commissions.
Now... is there some logic behind that? How does it work? I couldn't find a pattern for it: just sometimes it works, sometimes it doesn't. Sometimes the links open the Amazon app, sometimes they don't.
I used to shorten the links using Bit.ly, and thought it could be the problem (maybe the "amzn.to" wasn't recognized?), but nope, even using the long form links, sometimes it works and sometimes it doesn't.
Any idea?
Thank you.
Go to chat setting of Telegram and off the option to open in app link
New Matillion user, and my first project is to read in Google Analytics data by using a google account authorized to access GA data from several clients.
I follow the steps from this Matillion documentation: Google Query Authentication Guide
I have setup the needed client ID and client secret, and I've pasted the redirect URL into the credentials page in the Google console.
From Matillion, I enter the client ID and secret in the OAuth Configuration dialog, and I configure the proxyserver and proxyport under "advanced connection options" as specified in the Matillion documentation.
When I click the Authorization link in the OAuth it opens a new tab to the Google page where I login and allow the access. Once I do this, the redirect seems(?) to kick in and I presented with a browser page with the message "Authorisation complete Please close this tab". I am not taken back to the tab where Matillion OAuth configuration is still waiting for a response of some type.
Any ideas with this? Additional information: I setup Matillion via the Snowflake Partner Connect console and am still in the free 14-day trial for Matillion.
I was able to get the OAuth workflow to finish. Any issues from this point forward will be a battle for another day. Here are my findings:
First note that I initiated my Matillion install from the Snowflake Partner Connect, which was very straight forward. I was up and running with Matillion in less than a minute.
The Matillion version that launched was 1.50.6, which is behind the most current version 1.58.4. I had no idea this would not be the most current version, as I assume the cloud platform might provide new installs with the latest version. I can see reasons why this might not be the case.
After several hours ensuring my GCP project, client id, client key, and other settings were correct everywhere, the workflow still would not complete. I opened a support case with Matillion and it was responded to within 2 hours. That is excellent. The first recommendation was to update Matillion to the latest version as it will address an OAuth issue resembling the one I reported. I saw the new version was very recent, and didn't realize I was nowhere near having the latest version.
After the update completed, I tried repeating all of the same steps. The only difference now was that the "Authorisation complete" tab closed on its own returning me to the Matillion tab which still sat "Waiting for response from service...". The version update seemed to show promise but not a solution.
A comment Schepo above cleared the final hurdle: I removed the proxyserver and proxyport "Advanced Connection options" from the OAuth configuration, and then tried getting a new authorization link. Matillion froze up and the session was dead. I had to close the browser, open a new incognito window and repeat the steps - without the proxyserver/proxyport connection settings. This time the workflow completed!
The Matillion documentation for Google Query: https://documentation.matillion.com/docs/2339840 should be updated if the Proxy Settings are not required for all OAuth configurations. The OAuth issue I reported should also be documented somewhere as a known issue addressable by the latest version (if not already).
OAuth being one of the many ways you can set up connectivity with Snowflake; it appears you're attempting to set up External OAuth, that is Google is the authorizing server. My understanding is that there are two paths to setting up OAuth,
This link has the Azure AD setup with the two options, https://community.snowflake.com/s/article/Create-External-OAuth-Token-Using-Azure-AD-For-The-OAuth-Client-Itself
Googling to setup Google AD returns https://support.google.com/cloud/answer/6158849?hl=en
You may have to follow a similar process, follow this content here: https://docs.snowflake.com/en/user-guide/oauth-ext-custom.html
We running a wordpress website use google oauth for third-party social login. (via WP Social Login plugin.) Former engineer is leave, and we cannot have past google account credential.
We face a problem shows:
Error 401
Error: deleted_client
The OAuth client was deleted.
but we can only see old client id and secret from website admin panel.
I wanna to know,
if we set up a new google oauth application id/secret, will it make user crash from login website?
Or, is it possible for us to restore/retrieve former application ownership and make it live again?
This happened to me when I was working on an Add-On (maybe not completely related to this question but similar). I mistakenly deleted a Client ID that I thought we weren't using.
How I solved it:
Created a new project in Google Cloud
Associated the Apps Script project (Add-on) to this new Google Cloud project
Then I re-associated the App Script project with my previous Google Cloud project
The previous step will re-compile, create and associate the Client ID to the App Script project. It will contain all settings from the Client ID manually created and associated with your project in the code.
Maybe this will give some light to anyone having a similar problem.
Here use this link:
https://support.google.com/cloud/answer/6251787?hl=en
You have to reach google and they will help you out, this is the only solution you can do.
In my case, the simplest/only path (though certainly not ideal) ended up being to create a new Firebase project and start using that.
This of course can be problematic if you have a lot of data to move and/or a nontrivial data schema - say, with nested collections. For me, it was worth the effort to get unblocked from Sign-In suddenly failing to work.
... ah, OAuth fun
=======
If you are trying to make the new Client ID work .. though it's not a total solution, but after searching for a while, found this config option in Firebase console - where you enable Google Sign In.
So if you generate a new OAuth Client ID, update the ID & secret there.
After I did this, it went from a 401 error to a 400 mis_direct , which I think was step in the right direction.
I'm developing a bot for Skype and enabled setting that allows to add this bot to Group Chats. However, when I click to "Add People" button, I can see only the real people, but Skype Bots are hidden there (even the official ones).
There is an official doc that Skype bot can be added to the group chat as regular Skype account, but I am not able to do it.
My bot is not published, but one on one conversation works well. Also, in the private chat with Bot I can add people to conversation and thus I can create a group with this bot, but the main question is how to add the bot to the existing group chat?
On the configuration page for Skype on the dev.botframework.com site. Make sure you've enabled group messaging:
Additional information about groups on skype can be found here.
Finally I was able to add it to the group by opening Web Skype and then opening the private chat with my Bot.
Web Skype showed me a message "Add SkotBot to your contacts" which is very strange because it was already on my contact list. After clicking to this link bot is displayed on the "Add People" list.
I had the similar issues. and I try your method/suggestion above, it works!
the exact steps for other to read on (based on your suggestion)
1. from Mac Client Skype, I'm using version 7.43 (241) make a 1:1 chat with my bot. (to make it appears on the chat history on web skype later)
2. login the web skype, it will appear as history/conversation on the left. Message sending is disabled. Clicking on the bot icon appears on the chat screen above, it will open the profile
3. Add the bot to contact.
4. Then the bot can be added to the existing group conversation, just like add a normal human contact.
It seems to be some bugs in the Skype ecosystem?
I made a simple chatbot using Microsoft Bot Framework and integrated it with Telegram.
He works fine whenever I message him privately but whenever I put him in a group with my friends, he doesn't reply, even when I mention him.
/setjoingroups is enabled, and so is /setprivacy.
First make sure it is not caused by Microsoft Bot itself. Then for all normal bots --
Always add a Telegram bot to a group via the bot's info window, instead of inviting the bot to a group via the group's info window.
It's a clear trap for beginners. I'm surprised that Telegram didn't note this in their documentation.
When you configured your bot on Telegram, did you make it an inline bot? It's been my experience that inline bots cannot participate in group chats, but can message privately. If not, please open a GitHub issue here and we'll follow up there.
Beyond all other suggestions like turning off inline functions, setting privacy to disabled and allowing to participate in groups, I also made the bot an admin of my group. And now it processes all messages. That's what's worked for me.
I had this same problem, and I found that I just needed to add the bot as an 'admin' to the chat instead of just a normal member. The telegram bot must have admin privileges to access every message/image that the users of the group-chat send.