I've created a bot for Facebook Messenger from GupShup but when I try to access it from the site it does not appear in the Dashboard - > My Bots, but it still works on Facebook, so basically I've got a bot I can't modify, anyone got the same issue?
Looks like it was a login issue, Firefox 60.0 (64bit) has some issue, works fine in incognito mode or chrome
Related
So, I integrated Facebook Audience Network with AdMob Mediation. The waterfall ads work fine, however open bidding ads are not working.
I have tried all ways and still could not fix it. Any help is greatly appreciated.
I had the same issue. I solved mine by creating the app-ads.txt on the root of my developer website on playstore and uploaded both the code provided by AdMob and Facebook. Waited for several hours for admob to crawl the app-ads.txt changes and tried testing the mediation and everything worked.
facebook.com, fan_id, DIRECT, fan_id
google.com, pub-a_id, DIRECT, a_id
We pass an image from our app to Instagram using their standard iPhone URL scheme. It was working fine in iOS11, but in iOS12 it briefly goes to an Instagram login page (even though we're logged in) and then opens the Instagram Library with our image and tapping next to the Share screen places the image on a share page with many options unavailable. For example if you type a # hashtag it does no lookup. Tapping share does nothing.
Any ideas?
The redirect to the login page is a bug with the Instagram app, you have to wait for an update. You can do nothing, even their apps like Boomerang are broken when currently sharing to Instagram.
Yes, I tried so many repost application to be sure about the problem, unfortunately, it seems a bug of the iOS version of Instagram. In our application's Android version, we can trigger the Instagram.
I've created a Bot in MS teams that can authenticate the user against AAD. I've used the AuthBot code for this.
This works correctly. I have questions regarding further improving the sign-in experience. The Bot currently opens up a web browser, the user logs in and is redirect to a page with a magic number that he or she needs to copy-paste back into teams.
If I understand the Authentication section on this page correctly, then the following should be possible:
The browser window can be opened inside of Teams instead of through
the browser by specifying a validDomains attribute in the Teams
package manifest file. However, I chat with the Bot 1:1 and it
doesnt seem to use the manifest file (the Bot's image doesnt use the
one from the manifest). How do I get the login window to open inside
Teams?
There is a MS Teams javascript file. Can I use this (on the page that my Bots shows after authentication) to
redirect the user back to teams, and possibly automatically paste
the magic number into the chat with the Bot?
We missed answering this in August, apologies.
A more elegant way of doing bot authentication has been a common developer request. We are almost ready to publish samples and documentation for this solution once it's fully deployed on all client platforms. This approach removes the need for AuthBot completely and supports an integrated authentication experience, i.e. without opening a browser tab.
Currently, however, to answer your question, there is no way to have an inline authentication experience and the validDomains is not enforced (since it's just opening a browser page). The JavaScript client SDK you refer to is not used at all with bots because bots cannot currently run code on the client.
So in other words, what you are doing with AuthBot is currently the best possible way to do it.
Does anyone know why my action can NOT use in web simulator??
I set my invocation name for testing as "test", and in web simulator , I try to use my action by input "Talk to test", but it told me "Sorry, this action is not available in simulation"...
Is there anything wrong with me ??
I got this to work by saying "talk to my test app" or typing it in to the simulator prompt, that triggered my app to start in the simulator. I am using an account that is NOT associated with a home device, I also have NOT entered in artwork etc.
I have found that you have to type in that phrase anytime the simulator gets confused to get back into your intent flow.
In my case it looks like this in the Dialog portion of the simulator:
Turns out for me, even though I had turned on all the activity controls as the tutorial instructed, the organisation my login was associated with had them disabled.
Ask your admin to enable "Web & App Activity" in "My Account" > "Admin" > "Google Services"
I had same issue. This is how I "solved" it
Registered Google Home physical device to my email used for Action and api.ai development
(Redeployed, now Silly project started working)
(Still my project won't work)
Changed the invocation name to something simple ( My first language is not english)
Now Web simulator started working(
One possible Root cause - you are logged in via your second account.
This is the same issue I had. The UI from the earlier google home tutorials have been changed a bit. So after clicking the actions on google in api.ai we are redirected to to actions on google page. (Previously it was sent to the web simulator straight)
I created a project called personal butler in api.ai but what I saw was a project called API project, so when I clicked it and try to simulate it I got the exact error.
I registered to api.ai from my secondary google email. So when I was redirected to the actions on google page, it logged in via the primary account. After I signed out and loged in via the same account I was able to see my project and it was working fine.
PS - When testing with google home also the same account should be used in the andriod app
This bug should be resolved now. If you are still having this problem, you should try pairing your account with an actual device first. The issue was resolved for me by signing in to the Google Home app on my mobile device and pairing it to a home unit. After that, using the simulator then works in the browser.
I have a SharePoint instance serving as our Extranet to our salesforce - communicating over HTTPS. All sales agents have a Blackberry device, but none can access our Extranet.
In IIS, we only have ASP.NET Impersonation and Windows Authentication enabled, but the BB device doesnt even prompt for credentials, it just receives a 401 error.
Needless to say, the site is browsable on other devices (PC, tablet, iPhone..), so it seems to be something specific to BB settings - or thats my inclination. Anyone have any thoughts on how I can troubleshoot\resolve?
I should add.. I downloaded the BlackBerry emulator for my PC, and that too has the same issue, so I dont think it's a BlackBerry service setting.. but something with how the device is attempting to connect\authenticate.
OK, found the answer (apparently the Google machine is running much better today than it was yesterday ;)
Blackberry doesnt support Windows Authentication since the browser is too old. I had to turn on Basic Authentication, which isnt recommended unless your running over SSL.. which fortunately I am. Found the answer here: http://support.microsoft.com/kb/907273