it was not broken. The old code was uisng ``expires`` as the lifetime for facebook. the new code uses it the same way. and facebook sends it this way.
My comment came from the confusing name (and the assumption that your ``- time()`` fix attempt in the PR initially could be related to an issue with Facebook sending ``expires`` with an expiration date, like the HTTP header with this name, but it is not the case)