Expired Token issue?

[amcglathery]

Sometimes, if a user has not logged out, they cannot get to the login page at all, or any page that requires login. (They get an EDAM user exception)

[mjrussell]

Omg I got that bug yesterday. Ridiculously frustrating. Did you get it locally or on heroku?

[amcglathery]

heroku, got around it by going to /about

[mjrussell]

Same! We need to fix that ASAP. Work tonight? If you get an exception could
you redirect to login?

On Mon, Jul 2, 2012 at 2:13 PM, Andrew McGlathery <
reply@reply.github.com

wrote:

heroku, got around it by going to /about

---

Reply to this email directly or view it on GitHub:

#12 (comment)

[amcglathery]

I can't really work much tonight, but it is really easy to redirect to login on an exception. The one problem is reproducing it...

[mjrussell]

Right...I don't remember the line # either.

On Mon, Jul 2, 2012 at 2:18 PM, Andrew McGlathery <
reply@reply.github.com

wrote:

I can't really work much tonight, but it is really easy to redirect to
login on an exception. The one problem is reproducing it...

---

Reply to this email directly or view it on GitHub:

#12 (comment)

[amcglathery]

My guess is that it is from trying to se an expired auth token, so just putting try except statements around all of the calls to Evernote should do it.

[akhaku]

I've had this issue before with facebook tokens, it's probably the same issue. I'm assuming you're still working on sandbox? The fix is to refresh the token (there's an API call for that) when there's some amount of time left such as 1 day. Store the token expires time in the database and use that.

[mjrussell]

We are on production now! Due date is tonight. Can you refresh an expired
token?

On Mon, Jul 2, 2012 at 4:16 PM, Ammar Khaku <
reply@reply.github.com

wrote:

I've had this issue before with facebook tokens, it's probably the same
issue. I'm assuming you're still working on sandbox? The fix is to refresh
the token (there's an API call for that) when there's some amount of time
left such as 1 day. Store the token expires time in the database and use
that.

---

Reply to this email directly or view it on GitHub:

#12 (comment)

[akhaku]

I don't know, you might have to refresh it before it expires. Use the expires_time to check whether it will expire within 24 hours. I'm gonna see if I can find the API call...

[akhaku]

Nevermind, according to seth, you can't refresh tokens. You shouldn't have this problem with production tokens though, they're valid for a year. It'll be a year before this breaks...right?

[mjrussell]

Even on the production our token says only good for 1 day. I checked and
it's set right in the Auth call. Could it have been a mistake by Evernote?
It's right in the settings file I have
On Jul 2, 2012 4:30 PM, "Ammar Khaku" <
reply@reply.github.com>
wrote:

Nevermind, according to seth,
you can't refresh tokens. You shouldn't have this problem with production
tokens though, they're valid for a year. It'll be a year before this
breaks...right?

---

Reply to this email directly or view it on GitHub:

#12 (comment)

[akhaku]

Remove your current token from the database and re-authorize with Evernote. It should get you a new one that's valid for a year

[mjrussell]

I think I found the issue. Google Instant destroys the page by somehow
skipping the authentication. I found where the exception is and I'll just
throw them back to the login page.

On Mon, Jul 2, 2012 at 5:16 PM, Ammar Khaku <
reply@reply.github.com

wrote:

Remove your current token from the database and re-authorize with
Evernote. It should get you a new one that's valid for a year

---

Reply to this email directly or view it on GitHub:

#12 (comment)