In the short term, set Facebooker2.oauth2=true in your config. I'll be releasing a new version that makes this the default later today.

from facebooker2.

You need to set Facebooker2.oauth2 = true to be compliant. I am releasing a new gem today where this will be the default.

Mike

On Sep 29, 2011, at 5:38 PM, Alex Sherstinsky wrote:

Hi, Mike:

Could you please help clarify an issue for me -- I think that the answer to the following is "No", but wanted to check with you, just in case.

We got an email from Facebook, which starts with this:

Reminder: Upgrade Your App to OAuth 2.0 and HTTPS by October 1st.

etc.

Does this apply to people who use Facebooker2 and Mogli? If so, could you please tell me what we would need to change?

Thanks a lot.

--Alex

Reply to this email directly or view it on GitHub:
#62

Mike Mangino
http://www.elevatedrails.com

from facebooker2.

Thank you very much, Mike. Looking forward to the updated Facebooker2 gem. Cheers! --Alex

from facebooker2.

I pushed it this morning, so please give it a shot.

Mike

On Sep 30, 2011, at 1:56 PM, Alex Sherstinsky wrote:

Thank you very much, Mike. Looking forward to the updated Facebooker2 gem. Cheers! --Alex

Reply to this email directly or view it on GitHub:
#62 (comment)

Mike Mangino
http://www.elevatedrails.com

from facebooker2.

Hi, Mike:

I am upgrading it now. One thing -- just in case -- I am not noticing any
code with today's date (9/30/2011) in the GitHub source tree (
https://github.com/mmangino/facebooker2). Moreover, there is a line in
https://github.com/mmangino/facebooker2/blob/master/lib/facebooker2.rb
self.oauth2 = hash[:oauth2].blank? ? false : true

Is this something to be concerned about (i.e., do I still need to set
Facebooker2.oauth2 = true to be compliant)?

Thank you,
--Alex

On Fri, Sep 30, 2011 at 11:16 AM, Mike Mangino <
[email protected]>wrote:

I pushed it this morning, so please give it a shot.

Mike

On Sep 30, 2011, at 1:56 PM, Alex Sherstinsky wrote:

Thank you very much, Mike. Looking forward to the updated Facebooker2
gem. Cheers! --Alex

Reply to this email directly or view it on GitHub:
#62 (comment)

Mike Mangino
http://www.elevatedrails.com

Reply to this email directly or view it on GitHub:
#62 (comment)

from facebooker2.

I don't always push to github when I push a new gem. I just pushed the most recent code there now.

Mike

On Sep 30, 2011, at 3:28 PM, Alex Sherstinsky wrote:

Hi, Mike:

I am upgrading it now. One thing -- just in case -- I am not noticing any
code with today's date (9/30/2011) in the GitHub source tree (
https://github.com/mmangino/facebooker2). Moreover, there is a line in
https://github.com/mmangino/facebooker2/blob/master/lib/facebooker2.rb
self.oauth2 = hash[:oauth2].blank? ? false : true

Is this something to be concerned about (i.e., do I still need to set
Facebooker2.oauth2 = true to be compliant)?

Thank you,
--Alex

On Fri, Sep 30, 2011 at 11:16 AM, Mike Mangino <
[email protected]>wrote:

I pushed it this morning, so please give it a shot.

Mike

On Sep 30, 2011, at 1:56 PM, Alex Sherstinsky wrote:

Thank you very much, Mike. Looking forward to the updated Facebooker2
gem. Cheers! --Alex

Reply to this email directly or view it on GitHub:
#62 (comment)

Mike Mangino
http://www.elevatedrails.com

Reply to this email directly or view it on GitHub:
#62 (comment)

Reply to this email directly or view it on GitHub:
#62 (comment)

Mike Mangino
http://www.elevatedrails.com

from facebooker2.

Oh, I see! Sorry for the confusion. We are using MOGLI as a ruby gem and
Facebooker2 as a rails plugin (which is why I was looking around github).
Please let me know if there is anything wrong with this approach. For now,
everything seems to work (I did not set

Facebooker2.oauth2 = true in my configuration). I will let you know if I
run into any issues when Facebook cuts over starting tomorrow. Thanks a
lot! --Alex

On Fri, Sep 30, 2011 at 12:38 PM, Mike Mangino <
[email protected]>wrote:

I don't always push to github when I push a new gem. I just pushed the most
recent code there now.

Mike

On Sep 30, 2011, at 3:28 PM, Alex Sherstinsky wrote:

Hi, Mike:

I am upgrading it now. One thing -- just in case -- I am not noticing
any
code with today's date (9/30/2011) in the GitHub source tree (
https://github.com/mmangino/facebooker2). Moreover, there is a line in
https://github.com/mmangino/facebooker2/blob/master/lib/facebooker2.rb
self.oauth2 = hash[:oauth2].blank? ? false : true

Is this something to be concerned about (i.e., do I still need to set
Facebooker2.oauth2 = true to be compliant)?

Thank you,
--Alex

On Fri, Sep 30, 2011 at 11:16 AM, Mike Mangino <
[email protected]>wrote:

I pushed it this morning, so please give it a shot.

Mike

On Sep 30, 2011, at 1:56 PM, Alex Sherstinsky wrote:

Thank you very much, Mike. Looking forward to the updated Facebooker2
gem. Cheers! --Alex

Reply to this email directly or view it on GitHub:
#62 (comment)

Mike Mangino
http://www.elevatedrails.com

Reply to this email directly or view it on GitHub:
#62 (comment)

Reply to this email directly or view it on GitHub:
#62 (comment)

Mike Mangino
http://www.elevatedrails.com

Reply to this email directly or view it on GitHub:
#62 (comment)

from facebooker2.

Hi, Mike:

I got the following email from Facebook:

Fwd: Update your app to support OAuth 2.0 before 12/13/11

facebook

Dear Developer,

As part of our continued
effortshttps://developers.facebook.com/docs/oauth2-https-migration/
to migrate all apps to OAuth 2.0, we opted in all apps using the new
JavaScript SDK to OAuth 2.0 this afternoon at 11am PT and reverted at
1:30pm because we noticed that your app has not migrated. Please ensure
that you have set the oauth param in FB.init to true and that you are using
FB.getAuthResponse to obtain the access token.

Read more in the OAuth2 migration
announcementhttps://developers.facebook.com/docs/oauth2-https-migration/
, updates to the new JS SDK https://developers.facebook.com/blog/post/525/
blog post, or our JS SDK
docshttps://developers.facebook.com/docs/reference/javascript/
.

If your app was affected today, please ensure that you have made these
changes by December 13th, 2012 to avoid any disruption with your users.

Thanks,Facebook Developer Relation

Given that in September, I the latest from Facebook2 to address an issue
with OAuth from your github site. Could you please tell me if there is
something else I should do (or if I should get the latest Facebooker2
again), or if what I did back then was sufficient.

Thanks a lot,
--Alex

On Fri, Sep 30, 2011 at 6:27 AM, Mike Mangino <
[email protected]>wrote:

You need to set Facebooker2.oauth2 = true to be compliant. I am releasing
a new gem today where this will be the default.

Mike

On Sep 29, 2011, at 5:38 PM, Alex Sherstinsky wrote:

Hi, Mike:

Could you please help clarify an issue for me -- I think that the answer
to the following is "No", but wanted to check with you, just in case.

We got an email from Facebook, which starts with this:

Reminder: Upgrade Your App to OAuth 2.0 and HTTPS by October 1st.

etc.

Does this apply to people who use Facebooker2 and Mogli? If so, could
you please tell me what we would need to change?

Thanks a lot.

--Alex

Reply to this email directly or view it on GitHub:
#62

Mike Mangino
http://www.elevatedrails.com

Reply to this email directly or view it on GitHub:
#62 (comment)

Alex Sherstinsky
V.P. of Product Development
*
*catchfree
3434 Via Lido, Suite 300
Newport Beach, CA 92663
D: (949) 336-4802
M: (650) 260-3913
F: (949) 209-0370
EMail: [email protected]_asherstinsky@[email protected]
*
IM/Skype: AlexSherstinsky
Twitter: @alexsherstinsky http://twitter.com/alexsherstinsky_
*LinkedIn: http://www.linkedin.com/in/alexsherstinskyhttp://www.linkedin.com/in/alexsherstinsky
About.me: http://about.me/alexsherstinsky

from facebooker2.

The latest Facebooker2 and mogli should support OAuth2

Mike

On Dec 9, 2011, at 1:38 PM, Alex Sherstinsky wrote:

Hi, Mike:

I got the following email from Facebook:

Fwd: Update your app to support OAuth 2.0 before 12/13/11

facebook

Dear Developer,

As part of our continued
effortshttps://developers.facebook.com/docs/oauth2-https-migration/
to migrate all apps to OAuth 2.0, we opted in all apps using the new
JavaScript SDK to OAuth 2.0 this afternoon at 11am PT and reverted at
1:30pm because we noticed that your app has not migrated. Please ensure
that you have set the oauth param in FB.init to true and that you are using
FB.getAuthResponse to obtain the access token.

Read more in the OAuth2 migration
announcementhttps://developers.facebook.com/docs/oauth2-https-migration/
, updates to the new JS SDK https://developers.facebook.com/blog/post/525/
blog post, or our JS SDK
docshttps://developers.facebook.com/docs/reference/javascript/
.

If your app was affected today, please ensure that you have made these
changes by December 13th, 2012 to avoid any disruption with your users.

Thanks,Facebook Developer Relation

Given that in September, I the latest from Facebook2 to address an issue
with OAuth from your github site. Could you please tell me if there is
something else I should do (or if I should get the latest Facebooker2
again), or if what I did back then was sufficient.

Thanks a lot,
--Alex

On Fri, Sep 30, 2011 at 6:27 AM, Mike Mangino <
[email protected]>wrote:

You need to set Facebooker2.oauth2 = true to be compliant. I am releasing
a new gem today where this will be the default.

Mike

On Sep 29, 2011, at 5:38 PM, Alex Sherstinsky wrote:

Hi, Mike:

Could you please help clarify an issue for me -- I think that the answer
to the following is "No", but wanted to check with you, just in case.

We got an email from Facebook, which starts with this:

Reminder: Upgrade Your App to OAuth 2.0 and HTTPS by October 1st.

etc.

Does this apply to people who use Facebooker2 and Mogli? If so, could
you please tell me what we would need to change?

Thanks a lot.

--Alex

Reply to this email directly or view it on GitHub:
#62

Mike Mangino
http://www.elevatedrails.com

Reply to this email directly or view it on GitHub:
#62 (comment)

Alex Sherstinsky
V.P. of Product Development
*
*catchfree
3434 Via Lido, Suite 300
Newport Beach, CA 92663
D: (949) 336-4802
M: (650) 260-3913
F: (949) 209-0370
EMail: [email protected]_asherstinsky@[email protected]
*
IM/Skype: AlexSherstinsky
Twitter: @alexsherstinsky http://twitter.com/alexsherstinsky_
*LinkedIn: http://www.linkedin.com/in/alexsherstinskyhttp://www.linkedin.com/in/alexsherstinsky
About.me: http://about.me/alexsherstinsky

---

Reply to this email directly or view it on GitHub:
#62 (comment)

Mike Mangino
http://www.elevatedrails.com

from facebooker2.

Mike,

Thank you very much. Have a great weekend.

--Alex

Sent from my iPhone

On Dec 9, 2011, at 10:58 AM, Mike [email protected] wrote:

The latest Facebooker2 and mogli should support OAuth2

Mike

On Dec 9, 2011, at 1:38 PM, Alex Sherstinsky wrote:

Hi, Mike:

I got the following email from Facebook:

Fwd: Update your app to support OAuth 2.0 before 12/13/11

facebook

Dear Developer,

As part of our continued
effortshttps://developers.facebook.com/docs/oauth2-https-migration/
to migrate all apps to OAuth 2.0, we opted in all apps using the new
JavaScript SDK to OAuth 2.0 this afternoon at 11am PT and reverted at
1:30pm because we noticed that your app has not migrated. Please ensure
that you have set the oauth param in FB.init to true and that you are using
FB.getAuthResponse to obtain the access token.

Read more in the OAuth2 migration
announcementhttps://developers.facebook.com/docs/oauth2-https-migration/
, updates to the new JS SDK https://developers.facebook.com/blog/post/525/
blog post, or our JS SDK
docshttps://developers.facebook.com/docs/reference/javascript/
.

If your app was affected today, please ensure that you have made these
changes by December 13th, 2012 to avoid any disruption with your users.

Thanks,Facebook Developer Relation

Given that in September, I the latest from Facebook2 to address an issue
with OAuth from your github site. Could you please tell me if there is
something else I should do (or if I should get the latest Facebooker2
again), or if what I did back then was sufficient.

Thanks a lot,
--Alex

On Fri, Sep 30, 2011 at 6:27 AM, Mike Mangino <
[email protected]>wrote:

You need to set Facebooker2.oauth2 = true to be compliant. I am releasing
a new gem today where this will be the default.

Mike

On Sep 29, 2011, at 5:38 PM, Alex Sherstinsky wrote:

Hi, Mike:

Could you please help clarify an issue for me -- I think that the answer
to the following is "No", but wanted to check with you, just in case.

We got an email from Facebook, which starts with this:

Reminder: Upgrade Your App to OAuth 2.0 and HTTPS by October 1st.

etc.

Does this apply to people who use Facebooker2 and Mogli? If so, could
you please tell me what we would need to change?

Thanks a lot.

--Alex

Reply to this email directly or view it on GitHub:
#62

Mike Mangino
http://www.elevatedrails.com

Reply to this email directly or view it on GitHub:
#62 (comment)

Alex Sherstinsky
V.P. of Product Development
*
*catchfree
3434 Via Lido, Suite 300
Newport Beach, CA 92663
D: (949) 336-4802
M: (650) 260-3913
F: (949) 209-0370
EMail: [email protected]_asherstinsky@[email protected]
*
IM/Skype: AlexSherstinsky
Twitter: @alexsherstinsky http://twitter.com/alexsherstinsky_
*LinkedIn: http://www.linkedin.com/in/alexsherstinskyhttp://www.linkedin.com/in/alexsherstinsky
About.me: http://about.me/alexsherstinsky

---

Reply to this email directly or view it on GitHub:
#62 (comment)

Mike Mangino
http://www.elevatedrails.com

---

Reply to this email directly or view it on GitHub:
#62 (comment)

from facebooker2.

Hi, Mike:

I had the latest Mogli (0.0.36) and got the latest facebooker2. Now I
sometimes get the OAuthException with the message of "Session has expired
at unix time [...]". I found this discussed at
http://developers.facebook.com/blog/post/500/ but only with a PHP example.
By grepping for OAuthException in the mogli gem, I found some coverage of
this exception, but not with the above message. Do you have a
recommendation for how best to handle this?

Thanks a lot,
--Alex

On Fri, Dec 9, 2011 at 11:35 AM, Alex Sherstinsky <
[email protected]> wrote:

Mike,

Thank you very much. Have a great weekend.

--Alex

Sent from my iPhone

On Dec 9, 2011, at 10:58 AM, Mike Mangino<
[email protected]>
wrote:

The latest Facebooker2 and mogli should support OAuth2

Mike

On Dec 9, 2011, at 1:38 PM, Alex Sherstinsky wrote:

Hi, Mike:

I got the following email from Facebook:

Fwd: Update your app to support OAuth 2.0 before 12/13/11

facebook

Dear Developer,

As part of our continued
effortshttps://developers.facebook.com/docs/oauth2-https-migration/
to migrate all apps to OAuth 2.0, we opted in all apps using the new
JavaScript SDK to OAuth 2.0 this afternoon at 11am PT and reverted at
1:30pm because we noticed that your app has not migrated. Please ensure
that you have set the oauth param in FB.init to true and that you are
using
FB.getAuthResponse to obtain the access token.

Read more in the OAuth2 migration
announcement<
https://developers.facebook.com/docs/oauth2-https-migration/>
, updates to the new JS SDK <
https://developers.facebook.com/blog/post/525/>
blog post, or our JS SDK
docshttps://developers.facebook.com/docs/reference/javascript/
.

If your app was affected today, please ensure that you have made these
changes by December 13th, 2012 to avoid any disruption with your users.

Thanks,Facebook Developer Relation

Given that in September, I the latest from Facebook2 to address an issue
with OAuth from your github site. Could you please tell me if there is
something else I should do (or if I should get the latest Facebooker2
again), or if what I did back then was sufficient.

Thanks a lot,
--Alex

On Fri, Sep 30, 2011 at 6:27 AM, Mike Mangino <
[email protected]>wrote:

You need to set Facebooker2.oauth2 = true to be compliant. I am
releasing
a new gem today where this will be the default.

Mike

On Sep 29, 2011, at 5:38 PM, Alex Sherstinsky wrote:

Hi, Mike:

Could you please help clarify an issue for me -- I think that the
answer
to the following is "No", but wanted to check with you, just in case.

We got an email from Facebook, which starts with this:

Reminder: Upgrade Your App to OAuth 2.0 and HTTPS by October 1st.

etc.

Does this apply to people who use Facebooker2 and Mogli? If so, could
you please tell me what we would need to change?

Thanks a lot.

--Alex

Reply to this email directly or view it on GitHub:
#62

Mike Mangino
http://www.elevatedrails.com

Reply to this email directly or view it on GitHub:
#62 (comment)

Alex Sherstinsky
V.P. of Product Development
*
*catchfree
3434 Via Lido, Suite 300
Newport Beach, CA 92663
D: (949) 336-4802
M: (650) 260-3913
F: (949) 209-0370
EMail: asherstinsky@[email protected]<
[email protected]>
*
IM/Skype: AlexSherstinsky
Twitter: @alexsherstinsky http://twitter.com/alexsherstinsky_
*LinkedIn: http://www.linkedin.com/in/alexsherstinsky<
http://www.linkedin.com/in/alexsherstinsky>
About.me: http://about.me/alexsherstinsky

---

Reply to this email directly or view it on GitHub:
#62 (comment)

Mike Mangino
http://www.elevatedrails.com

---

Reply to this email directly or view it on GitHub:
#62 (comment)

Alex Sherstinsky
MustExist, Inc. (http://www.mustexist.com/)
[email protected]
Skype: AlexSherstinsky
http://twitter.com/AlexSherstinsky
650.260.3913
http://www.linkedin.com/in/alexsherstinsky

from facebooker2.

Hi, Mike:

I forgot the stack trace (just in case):

<RAILS_ROOT>/vendor/bundle/ruby/1.9.1/gems/mogli-0.0.36/lib/mogli/client.rb:79:in
raise_error_by_type_and_message' <RAILS_ROOT>/vendor/bundle/ruby/1.9.1/gems/mogli-0.0.36/lib/mogli/client.rb:70:in raise_client_exception'
<RAILS_ROOT>/vendor/bundle/ruby/1.9.1/gems/mogli-0.0.36/lib/mogli/client.rb:52:in
create_from_code_and_authenticator' <RAILS_ROOT>/vendor/plugins/facebooker2/lib/facebooker2/rails/controller.rb:231:in oauth2_fetch_client_and_user_from_cookie'
<RAILS_ROOT>/vendor/plugins/facebooker2/lib/facebooker2/rails/controller.rb:221:in
`oauth2_fetch_client_and_user'
<RAILS_ROOT>/vendor/plugins/facebooker2/lib/facebooker2/rails/controller.rb:16:in

`current_facebook_user'

The exception itself was:

<My Controller's Name> (Mogli::Client::OAuthException) "Code was invalid or
expired. Session has expired at unix time 1323784800. The current unix time

is 1323789695."

Thank you,
--Alex

On Tue, Dec 13, 2011 at 8:45 AM, Alex Sherstinsky <
[email protected]> wrote:

Hi, Mike:

I had the latest Mogli (0.0.36) and got the latest facebooker2. Now I
sometimes get the OAuthException with the message of "Session has expired
at unix time [...]". I found this discussed at
http://developers.facebook.com/blog/post/500/ but only with a PHP
example. By grepping for OAuthException in the mogli gem, I found some
coverage of this exception, but not with the above message. Do you have a
recommendation for how best to handle this?

Thanks a lot,
--Alex

On Fri, Dec 9, 2011 at 11:35 AM, Alex Sherstinsky <
[email protected]> wrote:

Mike,

Thank you very much. Have a great weekend.

--Alex

Sent from my iPhone

On Dec 9, 2011, at 10:58 AM, Mike Mangino<
[email protected]>
wrote:

The latest Facebooker2 and mogli should support OAuth2

Mike

On Dec 9, 2011, at 1:38 PM, Alex Sherstinsky wrote:

Hi, Mike:

I got the following email from Facebook:

Fwd: Update your app to support OAuth 2.0 before 12/13/11

facebook

Dear Developer,

As part of our continued
effortshttps://developers.facebook.com/docs/oauth2-https-migration/
to migrate all apps to OAuth 2.0, we opted in all apps using the new
JavaScript SDK to OAuth 2.0 this afternoon at 11am PT and reverted at
1:30pm because we noticed that your app has not migrated. Please ensure
that you have set the oauth param in FB.init to true and that you are
using
FB.getAuthResponse to obtain the access token.

Read more in the OAuth2 migration
announcement<
https://developers.facebook.com/docs/oauth2-https-migration/>
, updates to the new JS SDK <
https://developers.facebook.com/blog/post/525/>
blog post, or our JS SDK
docshttps://developers.facebook.com/docs/reference/javascript/
.

If your app was affected today, please ensure that you have made these
changes by December 13th, 2012 to avoid any disruption with your users.

Thanks,Facebook Developer Relation

Given that in September, I the latest from Facebook2 to address an
issue
with OAuth from your github site. Could you please tell me if there is
something else I should do (or if I should get the latest Facebooker2
again), or if what I did back then was sufficient.

Thanks a lot,
--Alex

On Fri, Sep 30, 2011 at 6:27 AM, Mike Mangino <
[email protected]>wrote:

You need to set Facebooker2.oauth2 = true to be compliant. I am
releasing
a new gem today where this will be the default.

Mike

On Sep 29, 2011, at 5:38 PM, Alex Sherstinsky wrote:

Hi, Mike:

Could you please help clarify an issue for me -- I think that the
answer
to the following is "No", but wanted to check with you, just in case.

We got an email from Facebook, which starts with this:

Reminder: Upgrade Your App to OAuth 2.0 and HTTPS by October 1st.

etc.

Does this apply to people who use Facebooker2 and Mogli? If so,
could
you please tell me what we would need to change?

Thanks a lot.

--Alex

Reply to this email directly or view it on GitHub:
#62

Mike Mangino
http://www.elevatedrails.com

Reply to this email directly or view it on GitHub:

#62 (comment)

Alex Sherstinsky
V.P. of Product Development
*
*catchfree
3434 Via Lido, Suite 300
Newport Beach, CA 92663
D: (949) 336-4802
M: (650) 260-3913
F: (949) 209-0370
EMail: asherstinsky@[email protected]<
[email protected]>
*
IM/Skype: AlexSherstinsky
Twitter: @alexsherstinsky http://twitter.com/alexsherstinsky_
*LinkedIn: http://www.linkedin.com/in/alexsherstinsky<
http://www.linkedin.com/in/alexsherstinsky>
About.me: http://about.me/alexsherstinsky

---

Reply to this email directly or view it on GitHub:
#62 (comment)

Mike Mangino
http://www.elevatedrails.com

---

Reply to this email directly or view it on GitHub:
#62 (comment)

from facebooker2.

I think you just to send the user through the auth process again to get a new session.

Mike

On Dec 13, 2011, at 11:06 AM, Alex Sherstinsky wrote:

Hi, Mike:

I forgot the stack trace (just in case):

<RAILS_ROOT>/vendor/bundle/ruby/1.9.1/gems/mogli-0.0.36/lib/mogli/client.rb:79:in
raise_error_by_type_and_message' <RAILS_ROOT>/vendor/bundle/ruby/1.9.1/gems/mogli-0.0.36/lib/mogli/client.rb:70:in raise_client_exception'
<RAILS_ROOT>/vendor/bundle/ruby/1.9.1/gems/mogli-0.0.36/lib/mogli/client.rb:52:in
create_from_code_and_authenticator' <RAILS_ROOT>/vendor/plugins/facebooker2/lib/facebooker2/rails/controller.rb:231:in oauth2_fetch_client_and_user_from_cookie'
<RAILS_ROOT>/vendor/plugins/facebooker2/lib/facebooker2/rails/controller.rb:221:in
`oauth2_fetch_client_and_user'
<RAILS_ROOT>/vendor/plugins/facebooker2/lib/facebooker2/rails/controller.rb:16:in

`current_facebook_user'

The exception itself was:

<My Controller's Name> (Mogli::Client::OAuthException) "Code was invalid or
expired. Session has expired at unix time 1323784800. The current unix time

is 1323789695."

Thank you,
--Alex

On Tue, Dec 13, 2011 at 8:45 AM, Alex Sherstinsky <
[email protected]> wrote:

Hi, Mike:

I had the latest Mogli (0.0.36) and got the latest facebooker2. Now I
sometimes get the OAuthException with the message of "Session has expired
at unix time [...]". I found this discussed at
http://developers.facebook.com/blog/post/500/ but only with a PHP
example. By grepping for OAuthException in the mogli gem, I found some
coverage of this exception, but not with the above message. Do you have a
recommendation for how best to handle this?

Thanks a lot,
--Alex

On Fri, Dec 9, 2011 at 11:35 AM, Alex Sherstinsky <
[email protected]> wrote:

Mike,

Thank you very much. Have a great weekend.

--Alex

Sent from my iPhone

On Dec 9, 2011, at 10:58 AM, Mike Mangino<
[email protected]>
wrote:

The latest Facebooker2 and mogli should support OAuth2

Mike

On Dec 9, 2011, at 1:38 PM, Alex Sherstinsky wrote:

Hi, Mike:

I got the following email from Facebook:

Fwd: Update your app to support OAuth 2.0 before 12/13/11

facebook

Dear Developer,

As part of our continued
effortshttps://developers.facebook.com/docs/oauth2-https-migration/
to migrate all apps to OAuth 2.0, we opted in all apps using the new
JavaScript SDK to OAuth 2.0 this afternoon at 11am PT and reverted at
1:30pm because we noticed that your app has not migrated. Please ensure
that you have set the oauth param in FB.init to true and that you are
using
FB.getAuthResponse to obtain the access token.

Read more in the OAuth2 migration
announcement<
https://developers.facebook.com/docs/oauth2-https-migration/>
, updates to the new JS SDK <
https://developers.facebook.com/blog/post/525/>
blog post, or our JS SDK
docshttps://developers.facebook.com/docs/reference/javascript/
.

If your app was affected today, please ensure that you have made these
changes by December 13th, 2012 to avoid any disruption with your users.

Thanks,Facebook Developer Relation

Given that in September, I the latest from Facebook2 to address an
issue
with OAuth from your github site. Could you please tell me if there is
something else I should do (or if I should get the latest Facebooker2
again), or if what I did back then was sufficient.

Thanks a lot,
--Alex

On Fri, Sep 30, 2011 at 6:27 AM, Mike Mangino <
[email protected]>wrote:

You need to set Facebooker2.oauth2 = true to be compliant. I am
releasing
a new gem today where this will be the default.

Mike

On Sep 29, 2011, at 5:38 PM, Alex Sherstinsky wrote:

Hi, Mike:

Could you please help clarify an issue for me -- I think that the
answer
to the following is "No", but wanted to check with you, just in case.

We got an email from Facebook, which starts with this:

Reminder: Upgrade Your App to OAuth 2.0 and HTTPS by October 1st.

etc.

Does this apply to people who use Facebooker2 and Mogli? If so,
could
you please tell me what we would need to change?

Thanks a lot.

--Alex

Reply to this email directly or view it on GitHub:
#62

Mike Mangino
http://www.elevatedrails.com

Reply to this email directly or view it on GitHub:

#62 (comment)

Alex Sherstinsky
V.P. of Product Development
*
*catchfree
3434 Via Lido, Suite 300
Newport Beach, CA 92663
D: (949) 336-4802
M: (650) 260-3913
F: (949) 209-0370
EMail: asherstinsky@[email protected]<
[email protected]>
*
IM/Skype: AlexSherstinsky
Twitter: @alexsherstinsky http://twitter.com/alexsherstinsky_
*LinkedIn: http://www.linkedin.com/in/alexsherstinsky<
http://www.linkedin.com/in/alexsherstinsky>
About.me: http://about.me/alexsherstinsky

---

Reply to this email directly or view it on GitHub:
#62 (comment)

Mike Mangino
http://www.elevatedrails.com

---

Reply to this email directly or view it on GitHub:
#62 (comment)

---

Reply to this email directly or view it on GitHub:
#62 (comment)

from facebooker2.

Hi, Mike:

So I will just catch the exception and ask the user to re-authenticate. I
was hoping, though, that this could be done seamlessly, without user
impact, because the exception is due to the default 2-hour session time
expiring.

Thanks,
--Alex

On Tue, Dec 13, 2011 at 9:09 AM, Mike Mangino <
[email protected]

wrote:

I think you just to send the user through the auth process again to get a
new session.

Mike

On Dec 13, 2011, at 11:06 AM, Alex Sherstinsky wrote:

Hi, Mike:

I forgot the stack trace (just in case):

<RAILS_ROOT>/vendor/bundle/ruby/1.9.1/gems/mogli-0.0.36/lib/mogli/client.rb:79:in
`raise_error_by_type_and_message'

<RAILS_ROOT>/vendor/bundle/ruby/1.9.1/gems/mogli-0.0.36/lib/mogli/client.rb:70:in
`raise_client_exception'

<RAILS_ROOT>/vendor/bundle/ruby/1.9.1/gems/mogli-0.0.36/lib/mogli/client.rb:52:in
`create_from_code_and_authenticator'

<RAILS_ROOT>/vendor/plugins/facebooker2/lib/facebooker2/rails/controller.rb:231:in
`oauth2_fetch_client_and_user_from_cookie'

<RAILS_ROOT>/vendor/plugins/facebooker2/lib/facebooker2/rails/controller.rb:221:in
`oauth2_fetch_client_and_user'

<RAILS_ROOT>/vendor/plugins/facebooker2/lib/facebooker2/rails/controller.rb:16:in

`current_facebook_user'

The exception itself was:

<My Controller's Name> (Mogli::Client::OAuthException) "Code was invalid
or
expired. Session has expired at unix time 1323784800. The current unix
time

is 1323789695."

Thank you,
--Alex

On Tue, Dec 13, 2011 at 8:45 AM, Alex Sherstinsky <
[email protected]> wrote:

Hi, Mike:

I had the latest Mogli (0.0.36) and got the latest facebooker2. Now I
sometimes get the OAuthException with the message of "Session has
expired
at unix time [...]". I found this discussed at
http://developers.facebook.com/blog/post/500/ but only with a PHP
example. By grepping for OAuthException in the mogli gem, I found some
coverage of this exception, but not with the above message. Do you have
a
recommendation for how best to handle this?

Thanks a lot,
--Alex

On Fri, Dec 9, 2011 at 11:35 AM, Alex Sherstinsky <
[email protected]> wrote:

Mike,

Thank you very much. Have a great weekend.

--Alex

Sent from my iPhone

On Dec 9, 2011, at 10:58 AM, Mike Mangino<
[email protected]>
wrote:

The latest Facebooker2 and mogli should support OAuth2

Mike

On Dec 9, 2011, at 1:38 PM, Alex Sherstinsky wrote:

Hi, Mike:

I got the following email from Facebook:

Fwd: Update your app to support OAuth 2.0 before 12/13/11

facebook

Dear Developer,

As part of our continued
efforts<https://developers.facebook.com/docs/oauth2-https-migration/

to migrate all apps to OAuth 2.0, we opted in all apps using the new
JavaScript SDK to OAuth 2.0 this afternoon at 11am PT and reverted at
1:30pm because we noticed that your app has not migrated. Please
ensure
that you have set the oauth param in FB.init to true and that you are
using
FB.getAuthResponse to obtain the access token.

Read more in the OAuth2 migration
announcement<
https://developers.facebook.com/docs/oauth2-https-migration/>
, updates to the new JS SDK <
https://developers.facebook.com/blog/post/525/>
blog post, or our JS SDK
docshttps://developers.facebook.com/docs/reference/javascript/
.

If your app was affected today, please ensure that you have made
these
changes by December 13th, 2012 to avoid any disruption with your
users.

Thanks,Facebook Developer Relation

Given that in September, I the latest from Facebook2 to address an
issue
with OAuth from your github site. Could you please tell me if there
is
something else I should do (or if I should get the latest Facebooker2
again), or if what I did back then was sufficient.

Thanks a lot,
--Alex

On Fri, Sep 30, 2011 at 6:27 AM, Mike Mangino <
[email protected]>wrote:

You need to set Facebooker2.oauth2 = true to be compliant. I am
releasing
a new gem today where this will be the default.

Mike

On Sep 29, 2011, at 5:38 PM, Alex Sherstinsky wrote:

Hi, Mike:

Could you please help clarify an issue for me -- I think that the
answer
to the following is "No", but wanted to check with you, just in
case.

We got an email from Facebook, which starts with this:

Reminder: Upgrade Your App to OAuth 2.0 and HTTPS by October 1st.

etc.

Does this apply to people who use Facebooker2 and Mogli? If so,
could
you please tell me what we would need to change?

Thanks a lot.

--Alex

Reply to this email directly or view it on GitHub:
#62

Mike Mangino
http://www.elevatedrails.com

Reply to this email directly or view it on GitHub:

#62 (comment)

Alex Sherstinsky
V.P. of Product Development
*
*catchfree
3434 Via Lido, Suite 300
Newport Beach, CA 92663
D: (949) 336-4802
M: (650) 260-3913
F: (949) 209-0370
EMail: asherstinsky@[email protected]<
[email protected]>
*
IM/Skype: AlexSherstinsky
Twitter: @alexsherstinsky http://twitter.com/alexsherstinsky_
*LinkedIn: http://www.linkedin.com/in/alexsherstinsky<
http://www.linkedin.com/in/alexsherstinsky>
About.me: http://about.me/alexsherstinsky

---

Reply to this email directly or view it on GitHub:

#62 (comment)

Mike Mangino
http://www.elevatedrails.com

---

Reply to this email directly or view it on GitHub:

#62 (comment)

---

Reply to this email directly or view it on GitHub:
#62 (comment)

---

Reply to this email directly or view it on GitHub:
#62 (comment)

from facebooker2.