Fatal error: Uncaught OAuthException: (#200) Requires extended permission: publish_actions thrown - facebook-graph-api

I am working on an app currently in sandbox mode and I need to test out the posting of user's scores... When I try the following I get the above subject matter. The odd thing about this is that I have the been granting the said permission (using my personal user account).
// var PERMS = 'user_likes,friends_likes,publish_stream,user_photos,photo_upload,publish_actions,offline_access';
https://www.facebook.com/dialog/oauth?scope='+PERMS+'&client_id='+APP_ID+'&redirect_uri='
I don't see the permissions in the Auth Dialog(I'm using the Enhanced Auth Dialog. They said its hidden :-S) but I am not "denying" any permissions and process the Auth Dialog successfully....
Can anyone tell me whats up here?

Have you submitted a bug? If not you should, and I will vote on it as well. It is definitely a new bug. I can show my repro on it.
I just got this today as well. Within the last hour. Googled it, and found this post. Last week I successfully moved 5 apps to use timeline open graph, and the enhanced auth dialog. Today, moving a new app, I made sure to add publish_actions, added it to the code, uninstalled the app, and reinstalled it with the new dialog, and tried to run a timeline post. Got the same error. I don't get this error on the apps I moved last week, they work just fine (just tested). I also noticed a couple of other changes to the UI when editing in the dashboard. The preview windows are gone on the auth dialog page. You can still fill in the aggregations in the open graph section. My guess is they made some changes last week, and broke something with new app permission changes.

Related

Unable to enable AWS Amplify Admin UI

I'm currently finding myself unable to enable the Admin UI. It was enabled before and now does not seem to work.
When I looked at my backends I see this.
Image of Amplify backend environment with a button to enable admin UI.
I then clicked the switch to turn on the Admin UI as shown below.
Image of the Admin UI enable screen.
I clicked it and it says it's enabling in a popup here, before saying it succeeded in another popup here.
I thought this was originally something wrong with my project but it's happening on my other amplify project - is the Amplify Admin UI down for some reason?
P.S. I was going to post this on server fault as this post says but there was no tag for Amplify on here.
Sorry this is not an answer, I cannot make comment so I have to write here.
I wasted a whole day by meeting the exactly the same issue.
At the same time, I tried to run Amplify pull --appid --envName several times, it always stuck there.
Amazon status page shows everything is fine now but I cannot believe it.
I also posted a question here but it seems nobody answered it.
I hope this issue was discovered by more people and Amazon finally can fix it, I believe it's not a problem on our side.
The issue was resolved as shown in this ticket I opened.
https://github.com/aws-amplify/amplify-adminui/issues/206
Have you tried selecting the environment and then clicking Open Admin UI?
I also wasnt able to login clicking in the URL and with my credentials, but clicking there worked.

Error when posting achievements with user messages

When posting an achievement with a user message it gives the following error:
{"error":{"message":"(#100) You haven't enabled User Messages for this action type (127701393971353) yet. Please update your Open Graph settings in the App Dashboard","type":"OAuthException","code":100}}
No clue where to enable that.
Managed to get access to the setting by modifying the url manually with the id.
https://developers.facebook.com/apps/your_app_id_here/opengraph/action_type/127701393971353/
In case this helps someone else, I had this issue. My situation was: I had a live app with an approved Open Graph action. I needed to release a new version of the app but I needed a new Open Graph action for this so the earlier version still worked until users upgraded to the new version. When I used the new Open Graph action, I got this error. My problem was that I had made a simple typo error in the bundle id of the new app version so it didn't match with the bundle id I had specified for the iOS settings in the Basic Settings page in the Facebook Developer app. The clue was that in the error given in the Xcode debug console, the app id didn't match up.

Facebook app stopped posting updates to the wall

Since Thursday our Facebook App has stopped posting updates to our page without any changes from our side.The error we got is
"OAuthException: (#200) User does not have sufficient administrative
permission for this action on this page"
but the permissions are all set properly (user = manager, app has access to wall etc) and our server gets the token back with the permission to post.
Has anyone experienced this issue lately and are there any solutions or suggestions to fix this?
I am not sure if this will help you, but solved it for me. Using the graph explorer I found with the APP_TOKEN it would not work, however changing this to the USER_TOKEN worked perfectly.

Action approved - publish_actions still not working

This question has been asked many times before, but they all seem to relate to problems before the Open Graph was 'opened'. As a new user, I also can't make this question useful, i.e no images or links. If you want to see the images I've posted, you'll have to copy and paste.
First of all, my Action is approved.
http://i.stack.imgur.com/hAFHr.png
Additionally, the action shows as being available to all users.
http://i.stack.imgur.com/IrrWW.png
publish_actions has been added to the Auth.
http://i.stack.imgur.com/PdJiA.png
I also have objects and aggregations setup correctly.
The auth preview also shows the correct settings (although the dialog currently doesn't stay open to see it, it used to).
When I try and connect with FB to the site, I don't see publish_actions. Instead I see the second stage of the dialog, for publish_stream. I set this by mistake the first time I saved the app, but quickly changed it.
http://i.stack.imgur.com/n819f.png
http://i.stack.imgur.com/gkXfg.png
This is where I think it gets even stranger. If I take a look at the FB profile for one of the app developers, and click through too the app from there, while not registered, I see the correct permissions.
http://i.stack.imgur.com/SsOVI.png
Yet another twist to the tale, which makes it even harder for me to debug, is that it seems since playing with the aggregations, I can't even get publish_actions permissions despite being listed as an app admin. (I've read that every action needs an aggregation before FB will process any actions sent by the server.)
/**/ FB.ApiServer._callbacks.ff2f1615c({"error":{"message":"(#200) Requires extended permission: publish_actions or App must be on whitelist","type":"OAuthException","code":200}});
That's the error I get when I complete the action on the site, http://purple.fr/boutique
Have I missed a setting somewhere? Have I done something I shouldn't? Should any of this be controlled in the code on the site?
When a user connects to your site, you should be asking for the publish_actions permission instead of the publish_stream permission. The referral dialog settings (where you already ask for publish_actions) only works when a user clicks on the action from within Facebook. It won't work for users already on your website.
In your login function (FB.login), make sure you add the permission publish_actions.
That aside, it looks like it's all working now.
http://i.stack.imgur.com/jAosv.png
http://i.stack.imgur.com/Wbgf5.png

Add To Timeline button not requesting publish_actions permission

I'm using the xfbml Add To Timeline social plugin (https://developers.facebook.com/docs/reference/plugins/add-to-timeline/), but when I click it the permissions dialog I get just says "Access my basic information" and sure enough it isn't actually getting me the publish_actions permission I need to use the timeline. I tried specifying the perm explicitly on the tag like so:<fb:add-to-timeline show-face="false" mode="button" perms="publish_actions"></fb:add-to-timeline> but no luck.
This was working fine yesterday and suddenly now it isn't. I'm wondering if this has something to do with my adding and removing my app from my facebook account multiple times?
This was driving me crazy for a long while. In my case, I fixed it by enabling 'Enhanced Auth Dialog' under the Advanced tab of my app settings.
When asking for publish_actions Facebook shows a preview screen of what sort of aggregations your app will create on their timeline.
In other words, if the preview isn't working, Facebook won't ask for the permission so you're asking in vain. Facebook doesn't make this clear in the docs, but everything needs to be perfectly setup with your app on Facebook to get this to work right.
Enable Enhanced Auth Dialong in the advanced settings of the app
Make sure you have at least one action and one object set up in the open graph section
For each action you must have an aggregation set up.
If you do not do all of these steps, there can be no preview and so Facebook won't ask for permission no matter what.
I faced the same issue. I fixed it by doing the below mentioned two thiings.
a. Enabled 'Enhanced Auth dialog' from 'advanced' setting of the app.
b. blanked 'user and friend permissions' along with 'extended permissions' tab on 'auth dialog' page.
I am not sure what it did, but it started working.
BUT.. Even though the authentication works and the posts are reflecting on my timeline, the add-to-timeline button still shows, 'Add to Timeline'..
The other trick i used is to keep checking the app permissions under account setting tab of my profile page.
Hope this helps !
From Apps -> Settings -> Auth Dialog:
While in Open Graph Beta, the 'publish_actions' permission can only be
requested from developers and test users of your app. The
'publish_actions' permission will be ignored if requested from any
other user.
I had the Enhanced Auth Dialog enabled in the Advanced Settings, yet this did not work until I added a Aggregation Preview for the activity. Strange, but true.
Hope this helps.
The publish_actions permission appears only if the user has added timeline OR if your app is a game. I suppose it will also be available for apps when Timeline will be rolled out to all users...