Notice: Undefined variable: dd_override_start_anchor_id in /home/ijailbre/public_html/wp-content/plugins/digg-digg/digg-digg.php on line 351
Notice: Undefined variable: dd_override_top_offset in /home/ijailbre/public_html/wp-content/plugins/digg-digg/digg-digg.php on line 352
Yesterday, Facebook rolled out an update to their popular iPhone application. Version 3.2 brings a few new features including “Places”, that allows you to let friends know where you are, and “Pull Down to Refresh”, like the Twitter for iPhone app. After the update some jailbroken iPhone users may have noticed some pages not loading in the app, or not being able to log in at all. In my case, i could not log in, and kept getting a connection error.
Well, thanks to our friends at Redmond Pie, I was able to find a solution for this. It turns out, the new version of the Facebook app is not compatible with the popular jailbreak SMS client “biteSMS”. We’re still not sure why, but somehow the SBSettings toggle was blocking Facebook’s connection to the internet. Personally, I never use this toggle, so I just turned it off, and Facebook is working fine again. Unfortunately, this breaks the biteSMS quick send and reply, which is the main reason a lot of people use this SMS client.
Here’s what you have to do:
- Open SBSettings (swipe across the status bar). If you don’t have this installed, it’s a free download from Cydia.
- Tap the “More” button
- Under System Options, tap “Mobile Substrate Addons” (be careful what you do in here)
- Scroll down until you find “biteSMSsb“, and turn it off. Leave “biteSBareClient” on, or you’ll lose the apps functionality
- Exit SBSettings. Your iPhone will respring. Your Facebook app should now be working fine.
This worked for me, hope it works for you. Let us know if this works, or if you have found a different fix, by posting in the comments below. Thanks again to Redmond Pie for posting this fix earlier today.
Don’t forget to follow iJailbreak on Facebook. Click here.
UPDATE: Facebook 3.2.1 has been released, but it does not fix this issue. We’ll just have to keep toggling, until there is an update to biteSMS.
UPDATE 2: biteSMS has a fix for this that they are testing right now. If you want to try it out, go here. All you have to do is download a new plist file from them and install it at Library/MobileSubstrate/DynamicLibraries/ to replace the current plist file. If you’re not comfortable with this, there should be an update sometime next week.