In the Open Graph Dashboard of my Facebook application I get error for my story saying "Unable to generate story" after creating both custom or storys with standard object.
So under the page facebookdeveloper/apps/myapp/story/openGraph where I usually have nice storys for different scenarios (one on one, multiple people, past tence) it just says error "Unable to generat story" everywhere.
My story titles says for example: "Mr X read a book.title on myApp" and then "Unable..."
There is no more information on why I get the error.
I had storys with similiar object etc. for the application previously which I removed. Cant his affect the creation of new stories?
Anyone else who has the same problem and a solution?
I had "Unable to generate story" until I completed the steps at :
Facebook Open Graph Story
Setup the Backend Server (just put the PHP example on a server you can access)
Test it using the Object Debugger
(Once you resolve any errors from Debugger) Publish a test action
OpenGraph can then generate the different scenario stories.
Hope that helps.
Try clicking on Manage Sample Data, create the sample object first, then the sample action. Setup the sample action to use the sample object you just created. This worked for me, just in time to stop me going mad. I got this solution from a Japanese site : http://konifar.com/1185
This error comes up because facebook has no examples of the story to render. It does not inhibit your ability to post the actions.
I know it's too late to provide an answer but it will be helpful to others who are having the same issue,I was having the same issue and it held me back by a couple of hours after one successful post you will be able to get the preview until then you can't get a preview.
Another point when publishing a test action:
It needs to be from your account, so if you have an account just for testing that's not the same as the admin account, it won't work
It can't be from a test user - I think this is related to the first point
Related
What is the correct way to start using Instagram oEmbed feature? Documentation (https://developers.facebook.com/docs/instagram/oembed/) claims that I have to pass App Review to start using the feature. And application form says Please provide a URL where we can test Oembed Read. Which I don't have because I have no access to the feature.
What I have tried with no success:
I requested instagram_oembed resource with:
app token of application in live mode
app token of application in
development mode
passed URL to a post by official Instagram account
(e.g. https://www.instagram.com/p/CQG4gZxMzzO/)
passed URL to a post
of a user who is Admin of the app
In all cases I receive (#10) To use 'Oembed Read', your use of this endpoint must be reviewed and approved by Facebook. To submit this 'Oembed Read' feature for review please read our documentation on reviewable features: https://developers.facebook.com/docs/apps/review.
Example of the request I do https://graph.facebook.com/v11.0/instagram_oembed?url=https%3A%2F%2Fwww.instagram.com%2Fp%2FCQG4gZxMzzO%2F&access_token=appAccessToken
We're also suffering from this issue, but so far, we thought we already figured out how to do that.
Big picture
Facebook had not sorted this thing out correctly. Or at least, we don't know why they put such a restriction to this API.
The official document is not correct. (or at least not accurate for now, for some part)
Which part was not correct?
The access token part is not right. Or at least, it's the most confusion part.
How can we resolve this?
Use the Graph API Explorer
Adjust your token(App token, Client access token, user token) with the official URLs(see below) to see if you can get the result
most of us should be able to get the result with user access token, which means you have to access this API after login!
Integrate into your app for review
The review page is also confusing:
Please provide a URL where we can test Oembed Read. Include the URL of a page, post or video from our official Facebook or Instagram pages, or the pages themselves., it means you can only use links like https://www.facebook.com/instagram or https://www.facebook.com/facebook
With that in mind, so far, the only way to get approved is integrate your oembed usage into your normal UI with facebook user access token ready
Question to the big picture
So, we have to ask user to login with our facebook app, then we can provide this oembed read API returned embed HTML? I'm afraid that's what we have now.
big companies might be able to apply for App Token, I guess in that scenario, facebook login is not necessary
for small companies, indie developers, hmmm, I don't know any better solutions so far.
I have run into this too. I do not have an answer at this time, I just want to report on the frustrations of their 'app review' process. Which makes it feel like you are unlikely to get it to work any time soon.
We have a custom embed code for our weblog authors to use (a shortcode kind of thing) which does the oEmbed call. We just take the HTML from the resulting JSON, and insert it into the weblog article page, and that is it. It stopped working, presenting this same error - in live mode, and in development mode.
The kicker is, I then tried submitting it for app review. Filled out everything I could to the best of my knowledge. Provided them a test account and post on our weblog to show the shortcode editing and expected placement. We got rejected. Why? Your embedding resulted in an error, we can't see it in action to approve you.
Yes. The error I am getting is that I need my 'app' to be reviewed and approved.
This is an infuriating process. This is the only Facebook / Instagram API feature we use at this point. No user data. No attempt to make an Instagram clone app or anything like that. Just an embed.
And they are making this simple use case as impossible to use as they can. And the documentation also feels like an infinite loop. They say users of the old Instagram embed call have until September 7 2021 to get approved. But the call does not work at all because we are not approved. So we cannot get approved.
Same loop here. I've managed to report it to Facebook team and get answer "Just submit your Instagram post URL"! I can't believe it, its can't be so simple. I've confirmed it few times with Facebook team person and.... get rejected!
Also, second form in App Review process will LOWERCASE all of your links and I've spent few days just to explain it to reviewers and support person. Still rejected after submitting proper url. This is insane.
My another attempt was about to build a test page where I can auth via Facebook account, parse connected Instagram accounts and GET embed endpoint with user access key in hope that reviewer HAS access to oembed feature - REJECTED. I can't even find what permission I need to add to auth URL to obtain oembed thing.
Will update my answer with new information later.
UPDATE: After reporting about the issue with lowercase URL in submission form they just APPROVED my app without APP REVIEW. Well... Facebook style...
I had exactly the same problem recently. Updated the packages with compose, changed the API version from 10 to 11... without any change.
The error was also occurring in development mode, it didn't make sense that Facebook was asking to approve in dev mode.
For me, the problem came from the management of scopes in my application, depending on the version of the Facebook API used.
My advice: check the scopes defined with API version in your code first.
I had the same issue and the solution is very simple. The only thing you need to do is copy paste an instagram url in the input field saying: Please provide a URL where we can test Oembed Read.
I did the this link: https://www.instagram.com/p/G/
Which is actually the first instagram post :) Got approved. Hope this helps everybody!
I am making edits to a client's Sharepoint site.
I checked out the page, made all the changes required, checked it back in, and am waiting on their go-ahead to publish.
I want to double-check that certain elements are the same as they were before I started editing. Generally I would go to site contents > pages > version history of the page I am working on, and look at the currently published version (because, as an editor, it seems to only show me the unpublished draft when I am on the page URL).
Tried to do that today and am getting an error: Sorry, something went wrong
Exception from HRESULT: 0x80131904.... Insightful and intuitive Microsoft error - well done guys (NOT).
Is there any other way that is more straightforward to just view what is currently published?
The quickest way to do this is to either log on as a test account that has only got read only permissions, or to ask one of your colleagues that doesn't have edit permissions to browse to the page and you can see what they see.
Version history, while is helpful when you need to roll back, won't show changes to web parts or other hidden elements when viewing it, so it's not always that helpful when using it for a case like yours.
As a side note, to log in as another user in SP2013, append this to your URL: http://yoursite/_layouts/15/closeconnection.aspx?loginasanotheruser=true
Background
I'm creating a simple Facebook application, first time working with Facebook.
* Using an "Action Type" of "Read"
* Using an "Object Type" of "Article"
I can't submit the application because the Action Type shows an error "You, or this app's Open Graph Test User, must have published this action at least once."
Immediate question:
I'm trying to publish the Action using the Graph API Explorer so that I can then submit the app for review.
I tried a GET /me/news.reads which didn't generate an error but only returned a blank results {"data":[]}
Also when I go back to look at the Action Type, it still shows the same error about needing to publish.
I tried the same request as a POST which did give an error "The action you're trying to publish is invalid because it does not specify any reference objects. At least one of the following properties must be specified: article."
On another notes, a more generic GET request I tried /me?fields=posts,feed gets me the data I want in the Graph API Explorer, but what would I set as my Action Type and Object Type to use that request?
Any comments on the overall approach I'm using would also be welcome.
More background: The underlying goal of this is that we want our separate corporate website to pull in the latest post to the Wall on our Page.
Any help would be much appreciated. Thanks.
I am working on an app that uses facebook's check in feature from mobile phones. I have created multiple versions of the app on facebook so that i can keep production, test and development separated. All good. However, all my checkins whether test or dev or prod are going to the live facebook platform leading to check ins like "this is a test" or "blah blah" on live facebook pages. Is there a way to be able to check in but not on these real/live pages? In other words, is there a sandbox or development version where developers can freely update content?
Thanks you guys!
Best,
Sachin
So, as with many other things in life, banging my head against the problem helped a bit. I found out that I can create test users for my app - upto 500 of them. The documentation is at http://developers.facebook.com/docs/test_users/. I was able to create test users for my app, login to facebook with those test users and verify that my actions did not show up on public pages. Phew, now i need to deface these public property no more. :-) When doing this, you need to use the app access token not the regular user accesss token. To get that, follow this link: https://developers.facebook.com/docs/authentication/applications/. The last gotcha I faced was that the second link above states that you should have a parameter named grant_type=client_credentials in your graph request. I kept looking for types of client credentials that i could substitute what i thought was a place holder named "client_credentials". That term needs to go in verbatim. (GOTCHA). Also, twice when I tried to create a user, facebook responded with an error json saying that an "unknown error has occured". I was almost ready to give up... but like i said before, banging head against the problem helps. Facebook responded with a json like so after the third request:
{
"id":"*******1832",
"access_token":"*****",
"login_url":"https://www.facebook.com/platform/test_account_login.php?user_id=*****&n=*****",
"email":"****",
"password":"*****"
}
Hope this helps someone else who might also be looking for this info.
I followed the guide on creating action links here: https://developers.facebook.com/docs/opengraph/actionlinks/
However, when I'm testing them with a new facebook app that I created it is not displaying the test action link. Is there some secret to making these work that is not included in the guide, or am I just rather unlucky?
Jesse, non-https action links should still be visible to developers, with an error message shown on the link itself.