I'm developing a Messenger bot and my use case requires me to link an account.
I was able to setup this, but I realized that the linking process doesn't work when the account linking URL is opened on browser. Though, it actually seems fine if opened on Messenger app.
According to the docs, there are two parameters appended on the account linking URL automatically: (a) account_linking_token and (b) redirect_uri.
Based on my test, the parameters are provided on Messenger app, but not on browser which causes it to fail.
I'll be grateful for any help you can provide and explanation on why this happen. Is account linking only works on mobile phone? Or is there something that I'm missing?
Related
I have created a conversational action in Actions Builder that uses account linking via OAuth (not Google sign in). Functionally, everything is working well.
The only issue I noticed is that when I try to link accounts using anything except a phone in the simulator, I get a response telling me to link accounts using the Google Home app. Since my action is a conversational action and not a smart home action, my action will never be found in the Google Home app.
I have confirmed that this kind of account linking is supported with conversational actions (via docs as well as Actions on Google support). What support could not answer for me is what I can do about this, they directed me here for help.
So my question is, how is account linking handled for conversational actions on non-phone devices (e.g. smart speaker)? Does it simply not run at all, or do I have to do something to remove these Google Home prompts?
Thanks
If the Action is running on a device type that does not support a web browser then the authentication step is not going to work. If you have not signed in before, the operation will fail. Though if you have signed in already, any device will be able to retrieve your access token.
The way to do this would be to handle cases for a non-authenticated device that cannot be authenticated. This may mean providing some part of your Action that can run in these conditions. Alternately, you'll need to inform people that they'll first need to use their phone to perform account linking.
I am building a simple Facebook app to connect the backend of a project to Facebook Messenger.
I am trying to send my app for review but it requires me to send a platform for the reviewer to test my app on.
the only place to interact with the app is the test Facebook page i created but i cannot add Facebook urls to the platform. What am I doing wrong here or what am I supposed to do?
I am building a simple Facebook app to connect the backend of a project to Facebook Messenger.
If you don’t have any end-user facing frontend, this would be considered a “server-to-server” app.
The documentation has specific instructions on how to submit those: https://developers.facebook.com/docs/apps/server-to-server-apps
Platform
Platform refers to the platform that your app users use to interact with your app. Since your app does not have an interface and your users don't interact with it directly, set this to Website and provide the URL to your company's website.
(Make sure to properly describe the purpose of your app and how it works, so that the reviewer does not try to go to that URL and look for a login button there.)
I want to provide the ability for my users to log-in to my app using OAuth providers like Google, Facebook, etc. For those purposes, I've built a unified OAuth login system that involves my server, based on instructions like this: Manually Build a Login Flow. From my users' accounts, I need only default permissions plus e-mail, with those permissions I've publish my Facebook app, and review was not required.
Today I've received a message from Facebook where I was asked to specify my Facebook app platforms, and this is where the problems begin. All provided but Facebook platform templates are not quite suitable for me:
currently, I'm using my system on the mobile app, but it is pointless to specify my package ID or provide some hashes because the app is not using Facebook SDK and those data will never be, received by Facebook
also, it is not correct to give the Facebook just my website URL it doesn't use Facebook login buttons or so, for log-in process communicates only mobile app and back-end
So, here my question.
Which platform I need to specify in my Facebook App if I've used instruction Manually Build a Login Flow to build my log-in flow.
Any ideas? May be someone have experience with this?
P.S. my app built on Flutter.
I'm looking for a solution on some problem.
We have mobile app on Xamarin and requirement to sign in with Facebook credentials.
To solve this we use Xamarin.Auth also tried CloudRail.
In both cases it works but it needs to input credentials when you laungh app first time, then app remebmers and allow to use them again.
Here is question. Maybe some one know how to skip that step, and login in app via Facebook with no one first time input credentials?
Like in GMail or Shazam. You download app, click Sign in with Facebook and it does't requires to input credentials, it's already known.
You could use
Facebook Xamairn Components
, which contains binding for Xamarin.iOS or Xamarin.Android.
I'm developing a 2nd version of our app for Facebook Messenger to meet their new platform integration requirements described here:
https://developers.facebook.com/docs/messenger
I'm attempting to allow both apps to share the same Facebook App ID. This page from the iOS troubleshooting docs has a section on Sharing an app ID across Apps
https://developers.facebook.com/docs/ios/troubleshooting#testsharedialog
It shows you how to add URL Scheme Suffixes to your apps so that they can both live on the same phone yet share the same Facebook App ID.
I've done this and it works successfully so that both apps can use Facebook login without stepping on each others toes. However, it seems that doing so broke my integration with FB messenger, which was previously working.
After following the instructions on the troubleshooting link above and adding the fields for the URL Scheme suffix, the videos I send to FB messenger no longer have a Reply button on them. Media inside Messenger that was sent from my app no longer contains any tappable element that takes you back to my app.
Does anyone know if there's a way to get the URL Scheme Suffix working in a way that it still works with the new Messenger Platform?
Thanks!
Heard back from Facebook directly on this. Their response:
No it doesn't. Because we will try to open the scheme without suffix. How would we know which suffix you want to open from messenger? ... So no suffixes are not supported. Just use a different app id.