Does anyone also experienced this type of problem? Webhook works perfectly fine with the rest but just with 1 certain user I'm not receiving anything from the webhook. It's not even called from facebook
The user already tried to uninstall and install back the messenger application but still the same result. Maybe there's something in their settings that need to be turned on or what
I somehow confirmed that facebook API has some traffic issues and sometimes have a delay in showing messages that are sent through their APIs. So patience is a virtue :D
Related
we received an email from Facebook review team telling us that our live app (website) is being reviewed and later got another templated email saying that our login is crashing or hanging, suggested we fix it, and gave us a bunch of links to the best practices on how to fix the FB login integration.
The problem is we don't use FB in our login (we just use their Marketing API) and, to us, the login works just fine.
Anyone else with a similar experience out there? If so, what did you do?
I've developed a Google Smart Home action and it is live on the Google Assistant and Google Home app.
Account Linking, Device Creation, and Device Control seem to all be working fine.
The one complaint we receive is that sometimes, after around a month, the devices seem to lose connection to the Google Assistant app.
When attempting to send a command, we get the most message "Sorry it looks like the is unavailable right now." The devices still show up under Home control and the action still appears under "Linked". The command event never reaches our Lambda function.
Does this problem description sound like a red flag towards any aspect of the integration?
I'm wondering if it is maybe a token that isn't being refreshed correctly? So that after the month, Google kicks us out? I only think this because of the consistent time frame the error occurs at. No idea though haha. I don't remember seeing anything in the docs or the sample action (https://github.com/actions-on-google/smart-home-nodejs) that mentioned preventing expirations from occurring.
Thank you for your help in advance!
You can review the error logs for your project, which will indicate if errors are occurring due to account linking or something else related to your intent fulfillment.
I'm wondering if it is maybe a token that isn't being refreshed correctly?
This is a reasonable place to start, and your error logs will indicate if there are account linking errors. For example, your OAuth server may be expiring the refresh token before a new one is delivered to Google Assistant. You can find more details on implementing OAuth token exchange in the documentation, including a note about rotating refresh tokens.
Note that Google Assistant generally only refreshes the access token when an intent needs to be sent (i.e. not immediately once the token expires). Sometimes this can also affect the refresh behavior of your OAuth server.
I have a problem with Facebook webhooks. The page/feed webhook works fine (triggers without any problems) for any page that authenticates with my app.
But the problem is that messenger webhook works only for pages that are managed by the owner of the app, pages from other users don't work, even in development mode, when these people are added as Developers/Testers. I'm trying to create an integration for an external ticket system that will support adding messenger messages as chats/tickers on the inside. As I said before everything works fine for feed and also for messenger but only if integrated page is managed by app owner.
Is there a possibility to overcome this at all? Or is it done like this by design and won't work this way ever?
I can't seem to find anything about this, so I decided to write here, maybe someone will know something.
Turns out that were permissions missing - for "outside" usage except manage_pages,publish_pages you also have to add read_page_mailboxes,pages_messaging,pages_messaging_phone_number permissions and everything stars working if it is configured properly.
I've got a FB page, that I used on a bot creation platform, then I use it for another bot creation platform.
What I expected was FB to cancel the previous subscription before setting the second one but looks like no.
I always get 2 responses, one from each of the platform.
I'm testing a handmade webhook, now and I'm getting 3 responses, the previous 2 ones and mine.
Is there a way to make FB drop the 2 first webhooks ?
By going to your page Settings and then Messenger platform you can uninstall any applications you do not wish to receive postbacks and/or send messages.
I have done few things with the facebook. And one of the easiest is what you are asking for.
So go to https://developers.facebook.com
Log and find you app
Go to webhooks
There are listed all the webhooks and next to each of them there is a button "Unsubscribe"
It is working without any verifications etc..
I'm sure this is something blindingly obvious, but I can't work it out.
I've added an admin and a tester user to my app (and I mean they're real people as opposed to the generated random named user that FB offers) but after a couple of weeks they're still listed as '(pending)' and they're unable to login to the web page that I've written using their Facebook account. OAuth responds with an error:
Sorry, this feature isn't available right now: An error occurred while processing this request. Please try again later.
I appear to be able to login just fine and can test the [currently] limited functions.
Our web page is right at the beginning of development but it's now at the stage where I'd like real people to mess around on the page and give me feedback.
The two users haven't received any messages - I sort of expected they'd get something in their inbox asking to confirm their role with the app.
So how do I go about getting real people to be test users? Have I missed the point of the test user role?
As of this writing (things change), have the Facebook user go to https://developers.facebook.com/requests/
They will need to be logged in to Facebook.
There should be listed one or more pending requests that they will need to confirm. If the Confirm button(s) is disabled, they may need to register as a Facebook Developer before the Confirm buttons are enabled.