We’re using the Facebook SDK for iOS. Everything works (both auth and feed dialog etc.), except the Request Dialog; the callback function "dialogCompleteWithUrl" is getting response URLs that contain no request_ids at all! We get something like "fbconnect://success?request=177205945735026&to%5B0%5D=559849340", which effectively translates to "fbconnect://success?request=177205945735026&to[0]=559849340" if you decode the URL encoding. We checked the friend's account; there were no requests in the notification section. Can anyone please help?
Furthermore, we tested the Hackbook sample using "Send invite" menu; it did NOT work either -- it generates similar URLs with no request_ids in it.
BTW, We're using the latest Facebook iOS SDK (downloaded last week on April 20, 2012) on the latest XCode 4.3.2 using iOS 5.1 & 5.0; tests were done on both the simulator and new iPad, as well as iPhone 4. A test using http://demo.vatlab.net/RequestDialog.aspx works between the user accounts used in the iOS sdk test mentioned above.
Thanks so much in advance.
The docs states:
Requests will only surface on platforms where the game has been
defined in the app dashboard as having a presence. So for example, if
an app exists on iOS and Android, but has no Canvas presence,
recipients will not see requests received via that app appear on the
desktop web version of Facebook.com.
Facebook Docs
Related
Google Transaction API has been implemented in Dialogflow Fulfillment. In my intent function my code is like agent.add(agent.conv().ask(new TransactionRequirements())). This code was running properly and giving response in google action console only before deployment in alpha test. But that time in mobile google assistance there were no response as well as no log in google firebase function. After deployment in alpha test the response is coming in google action console i.e
DISPLAY REQUEST RESPONSE AUDIO DEBUG ERRORS Invocation Error You
cannot use standard Google Assistant features in the Simulator. If you
want to try them, use Google Assistant on your phone or other
compatible devices.
Now also in mobile google assistant still response not coming. What is the solution for that?
let tran = new TransactionRequirements();
agent.setContext(context);
agent.add(agent.conv()
.ask(tran)
)
#stackjohnny
for a my UWP App I have created an extension for Edge and Chrome.
I have tried to create a new submission to the store but I have received the following errors:
com.microsoft.edge.extension is a reserved extension type. Your app does not have permission to use this extension type. To request permission, please use our extension submission form: https://aka.ms/extension-request
Your developer account doesn’t have permission to submit apps converted with the Desktop Bridge at this time. https://aka.ms/desktopbridgeforwindowsstore
I have fill the module at https://aka.ms/extension-request and at https://aka.ms/desktopbridgeforwindowsstore but, after 1 month, I didn't received any response.
Somebody know what I have to do in order to continue with the submission?
Does somebody have any experiences on that?
P.S.: I have sent a post at the MSDN forum and I have asked support at the Microsoft Answers but anybody was able to help me on that.
Thank you,
Regards,
MatVic
Conversation Flow : android device/web simulator - google assistant - api.ai - webhook - [websocket/FCM push] - android device
From end of last week, access token is not delivered to our webhook server even if account linking was successful and it is displayed on web simulator debugging window. When we logged on webhook server, the account token value from api.ai was NULL. After this happened, next account linking is not processed even if I reset (turn it off and on again) api.ai agent.
I tried to make new actions project and migrate api.ai agent to new one, but it was the same. I make sure the same test has been successful before last week.
If anyone has gone through the similar issue, I hope your help.
I was also very confused because I was expecting the accessToken to be in the same JSON format as shown in the simulator.
if still not working please send the body of the request you receive not what the simulator show you.
but it's under originalRequest.data.user.accessToken.
if you are using NodeJS you don't need to parse anything you will just need to call :
getUser().accessToken
from ApiAiApp object in the actions-on-google node library.
This has been driving me nuts all day:
I have an iOS app with a custom URL scheme defined, and am trying to share a link on FB which points to a page that has this scheme in its applink meta tags, so that tapping it should fire up my app.
Every little piece of it is working just fine. I can enter my URL scheme in safari on the phone and the browser launches my app. I have tested my webpage with the FB debug tool and there are no errors or warnings - it correctly identifies all the meta tags.
If I share the link using FB on the phone or on my laptop, all works fine.
HOWEVER, if I share the exact same link using FBSDKShareDialog, it does not work. It just opens the web page with the meta tags as if it was any regular web page.
Anyone has any idea why these two ways of sharing would be different? They look exactly the same otherwise.
If anyone else runs into this problem, here's the reply from FB:
When you share with mode automatic, the app does a fast app switch over to the FB app to show the native share dialog
The post is cached locally on the device, and it does not know about app links (since only Facebook server side knows about it)
When the user opens the FB, the user sees their cached story (with no app links behavior),
This doesn't manifest with the Web mode since the Facebook app needs
to pull from the server to get the post, in which case it has all the
app links info.
This is unlikely something that we'll fix. However, after a while, the
cache will expire, and Facebook app will re-pull the posts from the
servers, in which case the app link data will be available.
In order to test this, you can share the post on one device, and then
try clicking on the post from another device. The app links should
work at that point.
Which is kind of a lame response IMO - they parse the target page to build the preview, how hard would it be to remember the applink and use it?
There could be two possible issues:
Either the one told by #NJ, i.e. you are just trying to open the link in Facebook app, using the same device from which you posted the link.'
Solution - either open link in other device or cose and re-open your facebook app and do multiple refresh
Or You have some error in your meta tags. There is one important thing though, that Facebook never mentions, i.e. they cache the URL you provide.
So any one used the web link with meta tags the first time in Facebook, Whole meta tags will be cached, and you updated meta tags won't be parsed by facebook.
Solution
To get over with the issue, use below link
Facebook debug tool
Input your meta data included web page URL and
-click on show existing scrape information to find any error
Click on Fetch new scrape information for refreshing your URL on facebook. it will clear the cache for that URL in facebook server.
This maybe very noob and unworthy of stackoverflow.com, but nonetheless here goes:
I'm trying to write a custom application that syncs my Google data (emails, calendar and contacts) to the desktop (I know that there are several tools that let you do that, but curiosity only killed the cat!!).
I know that m.google.com is the sync sever I need to use. I've gone through [MS-ASHTTP].pdf, and got all the protocol information down.
Now, using either the cURL command-line or a tool (in Windows) such as Fiddler (http://www.fiddler2.com/), I'm unable to make valid ActiveSync requests to m.google.com. Moreover the URI /Microsoft-Server-ActiveSync doesn't exist on m.google.com, and searching Google turned up nothing for me. Need help!!!
Connecting to Google using ActiveSync should work (I have an Android app - Corporate Addressbook that does that successfully)
Use the following URL
https://m.google.com/Microsoft-Server-ActiveSync?User=xyz#gmail.com&DeviceId=1234512345&DeviceType=Android&Cmd=xxxxx
Edit the email address and the command you are sending. Also you will need to send the auth string in the header
I have a blog post that should help.