Pb with la_facebook_access_token_expires calculation ?

  • Hello

    We often have problems detecting the expiration of authorization tokens for our facebook feeds. I wonder if there is a problem with the calculation of the value “la_facebook_access_token_expires” stored in the database in the “options” table.
    In my case this value always contains a timestamp corresponding to a very distant time (such as 3331348454, year 2075…)
    In these conditions the “isExpiresToken” or “isExpiredToken” methods of the FFFacebookCacheManager class cannot return a correct result.

    This timestamp is in fact roughly 2 times the current timestamp.
    From what I could see there are situations where the action “refresh token” returns a timestamp in $expires (in the method FFFacebookCacheManager->refreshToken), instead of a validity duration in seconds.
    In this case the method FFFacebookCacheManager->save records in “la_facebook_access_token_expires” the current timestamp + the value of $expires, which is in fact a timestamp in that case, and not just a validity period in seconds, which gives me this huge timestamp with a year corresponding to 2075…

    Wouldn’t there be a fix for how the FFFacebookCacheManager class determines and uses this la_facebook_access_token_expires value?

  • The topic ‘Pb with la_facebook_access_token_expires calculation ?’ is closed to new replies.