Skip to content
#

facebook

Here are 2,672 public repositories matching this topic...

stevkan
stevkan commented Jan 3, 2020

Docs & samples should be updated to notify developers of Facebook's echo and delivery confirmations. If the message_deliveries and message_echoes webhook events are subscribed to and are not filtered for in the bot's incoming messages, then the user will receive continuous echoes / responses. This is something that does not occur via the Azure Bot Service Facebook channel as that service filte

anoop4real
anoop4real commented Mar 13, 2020

This is not an issue but an observation. I no longer use storyboards for my view. Today I faced an issue with Skeletonview when I added it to my UITableViewCell, animations, frames everything was working wrong... did a lot of permutation combinations turning the properties on and off. Finally found that when you add elements in UITableViewCell you should add it to contentView and not to th

skipcloud
skipcloud commented Apr 13, 2016

Figured I'd open an issue as I've been messing around this with gem today to try create something silly on Facebook, tried to post to a friends wall and got this error

Feed story publishing to other users is disabled for this application, x-fb-trace-id: EZaMJ3t2G8m [HTTP 403] (Koala::Facebook::ClientError)

apparently Facebook removed the ability for apps to post to walls via the Graph API [in

noseparte
noseparte commented Apr 20, 2019

In access to the Game Play Button Reference, they found me. Ramswaroop. Jbot. Core. Facebook.. Models of game_metadata default Button

Button Syntax
`{
"type":"game_play",
"title":"Play",
"payload":"{<SERIALIZED_JSON_PAYLOAD>}",
"game_metadata": { // Only one of the below
"player_id": "<PLAYE

remixz
remixz commented Jul 1, 2016

Facebook just recently added the ability to upload files (images, audio, videos, or a generic file) for a message, instead of having to specify a URL for an attachment.

PascalSenn
PascalSenn commented Mar 17, 2020

We just need a piece of documentation because there is literally no documentation about directive locations except from the spec. The spec is not easy to read. Something like this would make sense

directive @field_definition on FIELD_DEFINITION
directive @argument_definition on ARGUMENT_DEFINITION
directive @object on OBJECT
directive @interface on INTERFACE

interface Foo @inter

Improve this page

Add a description, image, and links to the facebook topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the facebook topic, visit your repo's landing page and select "manage topics."

Learn more

You can’t perform that action at this time.