-
Notifications
You must be signed in to change notification settings - Fork 159
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
does not work in Symfony 4.3 but does in 4.2 - doctrine .yml problem? #151
Comments
@24HOURSMEDIA did you men doesn't work in Symfony 4.4 but works ok in 4.3? Is symfony 4.4 enforcing to upgrade to any doctrine package version? |
Sorry, I meant Symfony 4.2 -> 4.3 |
Hi same problem in 4.3 Property "refreshToken" does not exist in class "Gesdinet\JWTRefreshTokenBundle\Entity\RefreshToken" |
This is not related to this library itself but with symfony auto validator symfony/symfony#31715 |
thanks @norkunas we'll wait for this issue be resolved to mark this issue as closed |
Can you confirm that symfony/symfony#31836 fixes the issue? |
This fix symfony/symfony#31836 (comment) does fix the issue. |
Solved in Symfony 4.3.1 release, please update your project. |
When upgrading from Symfony 4.2 to 4.3, the mappings did not work correctly anymore and I got errors like 'Property "refreshToken" does not exist in class "Gesdinet\JWTRefreshTokenBundle\Entity\RefreshToken"'
Downgrading the refresh token bundle to v0.3.3 seems to work fine
It seems doctrine .yml mappings will be deprecated, see:
doctrine/DoctrineBundle#776
maybe that's the cause?
(the downgraded bundle still uses annotations)
The text was updated successfully, but these errors were encountered: