Michael,
Whew! Very sorry for the delay. Lots of testing and investigation to see how to fix this best. The issue is actually a bug in Joomla 3.2.0. It's a very simple, 1-line fix, described below. Unfortunately, due to the bug's nature, there really is *no* way we can work around this in our code.
Fix removed. Implemented in JFBConnect v5.2.0. Previous versions of JFBConnect have this, and other, issues on Joomla 3.2 and it's recommended to upgrade to get all the updates.
Please test and let me know how that goes. There's actually a separate bug we found with Joomla when you've disabled the "Use Strong Encryption" setting. That's on by default, but if you want to disable it, let us know and we can give you the other fix as well.
I hope that helps, but please keep us posted on what you find,
Alex