No, this is not a real Sinatra error :).
This is the personal homepage of Elad Meidar, a web developer and an entrepreneur specializing in Ruby on Rails. I hang around in Israel, and i am currently having the best time of my life over at Fiverr.com
I am a proud member of RailsBridge, Helping new Rails developers get into our world and also contributed a few Patches to the Ruby on Rails core.
Facebooker is the most commonly used ruby interface to the Facebook API. It is considered stable and generally is being kept up to date with the frequent-and-annoying Facebook API changes.
Facebook has some strict rules you have to consider when using their API and FacebookConnect integration, one hidden rule for example, says something like that:
“If you use Facebook Connect on your site, the cookie that we are going to use, is the same cookie we keep for our main site,
Meaning basically that if a user is connected to your application (via Connect or through FBML, doesn’t really matter if it’s FBML) and he or she logs out of the main facebook site, they will also log out from the Facebook session on your application. Basically saying, that the user’s facebook session in your application, can be reseted without an explicit action from the user on your site. epic win facebook.
In order to handle that kind of situation you’ll have to rescue the
Facebooker::Session::SessionExpired and use the failsafe Rails method named
This will clear up all the Facebook remnants in your user’s session and will force him to reload.
Note that if the user granted you with the “offline access” permission and you saved the credentials, you will be able to restore the session without notifying the user.
You're seeing this error because I think it is funny.