Skip to content
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

Closed
24HOURSMEDIA opened this issue May 31, 2019 · 8 comments
Closed

Comments

@24HOURSMEDIA
Copy link

24HOURSMEDIA commented May 31, 2019

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)

@markitosgv
Copy link
Owner

@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?

@24HOURSMEDIA
Copy link
Author

24HOURSMEDIA commented May 31, 2019

Sorry, I meant Symfony 4.2 -> 4.3
If I write a custom entity for the refresh token (using annotations) the latest version works

@oschwartz
Copy link

Hi same problem in 4.3 Property "refreshToken" does not exist in class "Gesdinet\JWTRefreshTokenBundle\Entity\RefreshToken"

@norkunas
Copy link
Contributor

This is not related to this library itself but with symfony auto validator symfony/symfony#31715

@markitosgv
Copy link
Owner

thanks @norkunas we'll wait for this issue be resolved to mark this issue as closed

@markitosgv markitosgv changed the title does not work in Symfony 4.3 but does in 4.3 - doctrine .yml problem? does not work in Symfony 4.3 but does in 4.2 - doctrine .yml problem? May 31, 2019
@xabbuh
Copy link

xabbuh commented Jun 4, 2019

Can you confirm that symfony/symfony#31836 fixes the issue?

@lsv
Copy link

lsv commented Jun 6, 2019

This fix symfony/symfony#31836 (comment) does fix the issue.
I havent tried symfony/master yet.

@markitosgv
Copy link
Owner

Solved in Symfony 4.3.1 release, please update your project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants