Closed marcosmarxm closed 1 year ago
From @marcosmarxm - "I saw at least 3 users having problem with Facebook Pages"
For folks who experience this issue, please comment on this thread to help us prioritize this in upcoming sprints!
I'm having this issue as well, very critical as we can't use it at all
I tried generating a token with all 32 permissions and It worked though I was told from the docs that only 4 permissions are needed
Running into the same problem here
I'm also having the same issue
I was able to create the connection. Turned out I needed almost admin access level for it to work.
However, I'm now running into the "printing access_token error". Seems to be a bug with the connector, no way to solve it
Same problem here as well.
We're having issues with this as well.
We are having issues with this as well.
I am having issue as well. same Error HTTPError('400 Client Error: Bad Request for url:
Hi Folks, thanks for flagging this issue. We are actively monitoring it, but since this is an alpha connector, we are not prioritizing the issue at this time. As always, we welcome contributions from our community to resolve this problem. Thank you!
I'm had issues with these fields and suggest they could be removed:
nativeoffers
(nonexisting field) also referenced in: #13756 and #12563visitor_posts
(Unavailable Feature On New Page Experience)rtb_dynamic_posts,call_to_actions,canvas_elements,commerce_merchant_settings
(This endpoint requires the 'pages_manage_ads' permission or the 'Page Public Content Access' feature.)With those 6 removed, I can successfully query the API explorer with FB API versions 13/14/15 but v12 throws an error:
You are calling a deprecated version of the Ads API. Please update to the latest version: v14.0.
Duplicate issues: #20117
fixed in https://github.com/airbytehq/airbyte/pull/19788, please double check you use the proper long lived access token. (see the docs)
Remove this with your answer.