I had the same problem because I used FBConnect. Facebook has scheduled several "breaking changes". This particular one was forced on everyone on Aug 1st 2012. So, disabling the Breaking Change won't help anymore.
Technically speaking, ShareKit should fix the problem. However, you should really check to see if the feature was working for you. Go to:
Apps>>your app>>Insights>>See All
Then apply the formula:
Value = extra app sales just for having the feature + sales due to sharing on FB - yearly maintenance cost to update FB software - customer service cost for FB bugs - lost sales due to disgruntled FB users.
In my case, Value was negative so I removed the feature from my top-selling iOS app. FBConnect was the most buggy part of my app and it unfortunately did more damage than good.
For those interested, here are the bugs we encountered:
- FBConnect would break when people changed their password on FB but the session key was still valid. There was no way to detect this so people just got hung.
- FBConnect would time out quite often for no particular reason (assume this was server issues on their end).
- FBConnect didn't handle out-of-coverage (no internet) connections very well.
I'm not ranting here, I'm just providing a technical insight which is important to consider before determining the correct way to fix the problem. Updating the SDK is the right solution for some people, but not everyone.