publish_actions 权限错误
我正在尝试创建一个具有自定义操作的应用程序，因此我已将“publish_actions”添加到使用访问令牌请求的权限列表中。我当前未使用该应用程序的测试用户无法获取访问令牌，我收到不透明错误。请参阅
我看到其他关于人们将应用程序更改为“游戏”来解决问题的帖子“publish_actions”存在问题，但这没有任何区别。一旦我从范围中删除“publish_actions”，我的测试用户就可以获得访问令牌，但是当它尝试发布自定义操作时，响应是 OAuthException 错误“(200#) 需要扩展权限：publish_actions
”如何开发和测试自定义操作将不胜感激。
I'm trying to create an app with custom actions so I've added "publish_actions" to the list of permissions requested with the access token. My test user that doesn't currently use the app can't get an access token, I get an opaque error. see
I saw other posts about people changing their app to "Games" to work around problems with "publish_actions" but that has made no difference whatsoever. As soon as I remove "publish_actions" from the scope, my test user can get an access token fine but when it tries to post a custom action, the response is OAuthException error "(200#) Requires extended permission: publish_actions"
Some clarity on how one can develop and test custom actions would be appreciated.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
事实证明，问题出在“App”>“配置”下配置的示例保存没有聚合。 “应用程序名称”> “聚合预览”部分中的“身份验证对话框”。一旦完成，它就起作用了。不幸的是，Facebook 的错误没有表明这就是问题所在，也没有表明忽略配置“聚合预览”将导致publish_actions 权限失败。这看起来像是 Facebook 方面的一个错误。
It turns out that the problem was not having an aggregation with sample save configured under "App" > "App Name" > "Auth Dialog" in the 'Aggregation Previews' section. Once that was done, it worked. Unfortunately, Facebook's error provided no indication that that was the problem or that neglecting to configure the 'Aggregation Preview' will make the publish_actions permission fail. This looks like a bug on the Facebook side.
我也有类似的问题。我已经使用开放图测试用户完成了一些测试，因此，该测试用户已接受该应用程序。
之后，我将“publish_actions”添加到权限列表中。然而，由于测试用户已经接受了该应用程序，因此不会再次请求授权。
要解决此问题，请转到“设置”>“应用程序并删除您的应用程序（当您以测试用户身份登录时）。
下次运行该应用程序时，它应该再次请求授权。
I was having a similar problem. I had done some tests using the Open Graph Test User and, therefore, this test user had accepted the app.
After that, I added "publish_actions" to the list of permissions. However, as the test user had already accepted the app, it wasn't asking again for authorisation.
To solve this, go to settings > apps and delete your app (while you're logged in as the test user).
Next time you run the app, it should ask again for authorisation.