1

I've already integrated facebook login in an app with the previous sdk version. After upgrading to version 3.5, it isn't working. When I want to login, the app crashes, with several [FBSession authorizeWithPermissions:defaultAudience....] callings in the thread. I've already done all the steps described in Upgrading documentation. Somebody with the same problem? Thanks in advance.

The app is for iOS.

Magyari Beáta
  • 11
  • 1
  • 1
    I think I have the same problem, see my question: http://stackoverflow.com/questions/16118314/parse-com-and-facebook-login-runs-infinite-loop – MartinHN Apr 20 '13 at 22:07
  • Exact the same problem. If you find something useful, please let me know. Thanks. – Magyari Beáta Apr 21 '13 at 10:21
  • Are you presenting the login viewcontroller in a modal, like I do? – MartinHN Apr 21 '13 at 11:54
  • I think, that doesn't matter. I've found that the problem is a reported bug: https://developers.facebook.com/bugs/188127071335876?browse=search_5174e73fbe3965769089278 – Magyari Beáta Apr 22 '13 at 07:34
  • Same thing happening to me. I did notice that if I got rid of FacebookDisplayName the problem goes away, but that doesn't seem correct. I think it is just covering up the real problem. I reported bug also: https://developers.facebook.com/bugs/188127071335876 – Skotch Apr 22 '13 at 18:52
  • As an answer to my questions states, turning off sandbox mode worked for me: http://stackoverflow.com/a/16153697/2972 – MartinHN Apr 22 '13 at 19:07
  • Also see http://facebook.stackoverflow.com/questions/16135087/facebook-sdk-3-5-cant-log-in-crashes-app . There was a problem server-side that we found and has been addressed. Thanks! – Chris Pan Apr 23 '13 at 04:21

2 Answers2

0

Set Sandbox Mode to disabled. This will fix this problem for now.

enter image description here

Piotr Tomasik
  • 9,074
  • 4
  • 44
  • 57
0

Facebook has fixed part of the problem on the server side. Try it again and it will probably work for you.

https://developers.facebook.com/bugs/188127071335876?browse=search_51770009e1ec62f68874486

This was a server error that was causing this for a lot of developers. However, the server fix only makes the infinite loop problem less likely to happen. It is still there. I created a new bug to track the infinite loop problem.

https://developers.facebook.com/bugs/446010282155033

Skotch
  • 3,072
  • 2
  • 23
  • 43