Note that there are some explanatory texts on larger screens.

plurals
  1. POFBConnect Issues: Authentication and post won't work the first time
    text
    copied!<p>I've two issues with Facebook Connect:</p> <p>1) I use the new Single Sign On Authentication. It works great, but the first time, I authenticate an user with my App when I request the token, i immediately want to post a link to the users wall, but then I get this error:</p> <pre><code>2011-10-11 15:42:44.831 [1717:707] Dialog DidFail With Error: Error Domain=NSURLErrorDomain Code=-999 "The operation couldn’t be completed. (NSURLErrorDomain error -999.)" UserInfo=0x7487290 {NSErrorFailingURLKey=https://m.facebook.com/dialog/feed?link=http%3A%2F%2Fwww.example.it%2Findex.php%3Fid%3D4%26no_cache%3D1%26tx_ttnews%5Btt_news%5D%3D103184&amp;access_token=_test-Z0Ru37mpEAbffAn9n5wlWUaIVOH2tsF8.eyJpdiI6IjYyUXVBOTJKZVVwWjF5bmxZUmluUGcifQ.VxaUq2QcPXUgcYTjvqtnhLcBK27wflAIv3XoNVNcRT6dtQqfJZZ9NdLqLXxPdpBFl1U1DGF8xetLy8TOcLuLmU9l2AQ0JzYKmm9d-7azAYCYiZc51BiXKgHlpzw9Hsplr-tTKAfkXF2oJSOkbeN7UDMyLqDdCyhwiFTdVX3tGzA&amp;app_id=1535027294&amp;redirect_uri=fbconnect%3A%2F%2Fsuccess&amp;user_message_prompt=Teilen&amp;sdk=2&amp;display=touch, NSErrorFailingURLStringKey=https://m.facebook.com/dialog/feed?link=http%3A%2F%2Fwww.example.it%2Findex.php%3Fid%3D4%26no_cache%3D1%26tx_ttnews%5Btt_news%5D%3D103184&amp;access_token=_Wtest_modifiedF8.eyJpdiI6IjYyUXVBOTJKZVVwWjF5bmxZUmluUGcifQ.VxaUq2QcPXUgcYTjvqtnhLcBK27wflAIv3XoNVNcRT6dtQqfJZZ9NdLqLXxPdpBFl1U1DGF8xetLy8TOcLuLmU9l2AQ0JzYKmm9d-7azAYCYiZc51BiXKgHlpzw9Hsplr-tTKAfkXF2oJSOkbeN7UDMyLqDdCyhwiFTdVX3tGzA&amp;app_id=688535027294&amp;redirect_uri=fbconnect%3A%2F%2Fsuccess&amp;user_message_prompt=Teilen&amp;sdk=2&amp;display=touch} </code></pre> <p>The second time I try to post something to the wall I get a success, there I don't need to request the permissions again. But the first time it always fauls. With the facebook.app installed, but also with the redirect from Safari.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload