Passport: Got issue when upgrade to laravel 8

Created on 25 Nov 2020  路  6Comments  路  Source: laravel/passport

Hi Guys,

I've just tried to upgrade laravel to 8x from 7x and it require passport 10x, but after successful upgraded i got issue with message
"Using integers for registered date claims is deprecated, please use DateTimeImmutable objects instead."

image

can anyone help me to fix it? thanks

Most helpful comment

I'm not on Laravel 8. I'm on 7 but I'm getting the same error.

Looks like updating https://github.com/lcobucci/jwt to 3.4.x from 3.3.0 is also causing this.

Given that 3.4.0 was only released a few hours ago, this seems to be the culprit.

Peg your dependency of lcobucci/jwt to ~3.3.0 and then update it again.

All 6 comments

Hello,
have the same

Hi there,

Thanks for reporting but it looks like this is a question which can be asked on a support channel. Please only use this issue tracker for reporting bugs with the library itself. If you have a question on how to use functionality provided by this repo you can try one of the following channels:

However, this issue will not be locked and everyone is still free to discuss solutions to your problem!

Thanks.

I'm not on Laravel 8. I'm on 7 but I'm getting the same error.

Looks like updating https://github.com/lcobucci/jwt to 3.4.x from 3.3.0 is also causing this.

Given that 3.4.0 was only released a few hours ago, this seems to be the culprit.

Peg your dependency of lcobucci/jwt to ~3.3.0 and then update it again.

I'm not on Laravel 8. I'm on 7 but I'm getting the same error.

Looks like updating https://github.com/lcobucci/jwt to 3.4.x from 3.3.0 is also causing this.

Given that 3.4.0 was only released a few hours ago, this seems to be the culprit.

Peg your dependency of lcobucci/jwt to ^3.3.0 and then update it again.

thanks, it works for me just need to downgrade to 3.3.0 馃憤

Specifically it is thephpleague/oauth2-server that uses this dependency. Is passport. oauth2-server have lcobucci/jwt set to ^3.3.1 and so following closer to semantic versioning, expects 3.4 to not break compatibility. Technically it does not break compatibility, but rather exposes those production servers that have E_DEPRECATED in their error_reporting settings, and so they aren't considering it a BC break.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

Adesubomi picture Adesubomi  路  4Comments

duccanh0022 picture duccanh0022  路  3Comments

huiyonghkw picture huiyonghkw  路  3Comments

mind-control picture mind-control  路  3Comments

rudolfdobias picture rudolfdobias  路  3Comments