Created By
Vincent Germain
08/24/2012 2:48am

Subscribers (45)

BugsCrash on SBJSON when using iOS SDK 3.0.8 & FB App 5.0

  • Status: Fixed
  • Priority: Medium
  • Updated: October 15, 2012 at 1:46pm
Latest response from Facebook
Shireesh Asthana
This should now be resolved with the latest iOS SDK 3.1.1 . Thanks for your patience.
Status changed to Fixed · October 15, 2012 at 1:46pm
Shireesh Asthana
It seems like a JSON framework conflict issue and as pointed out by many of the subscribers, updating the frameworks can solve the issues.
Priority changed to Medium · August 28, 2012 at 1:48pm
Shireesh Asthana
Task has been assigned. Thanks for the report. We're looking into this.
Status changed to Assigned · August 24, 2012 at 11:44am
Shireesh Asthana
HI VIncent,

I tried to repro this bug. I have FB app 5.0 installed along with my app which uses FB iOS SDK 3.0.8 and it functions perfectly. For sanity check, can you please verify that the sample apps as part of the SDK work fine with the FB app 5.0 installed. Else please provide more detailed repro steps to track down the bug.

Once you have prepared this information, you can add it to this bug using the "Add More Info" button to the right. Commenting on this bug will not re-open it. If no further information is provided within seven days, we will automatically close this bug.
Status changed to Need More Info · August 24, 2012 at 10:07am
Shireesh Asthana
Thanks for the report. We will follow up.
Status changed to Triaged · Priority changed to High · August 24, 2012 at 9:57am
Hi.

We implemented the FB iOS SDK 3.0.8 in our app.
When using it and having on our iPhone/iPad the FB App 5.0 (so the one from today), there is a crash with SBJSON
"[SBJsonParser errorTrace]: unrecognized selector sent to instance 0x11fb250"
We are 100% sure it's coming from the FB framework.

We tried to use the master version on the github project (commit 682535050207c771706823cbf0fc31a206b12956) and it doesn't crash at all. But we would like to use a "stable" version, which doesn't crash.

Any idea ?

Thanks.
7 people can reproduce this issue by following these steps
Repro