-
Notifications
You must be signed in to change notification settings - Fork 160
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
"Gesdinet\JWTRefreshTokenBundle\Entity\RefreshToken" is not a valid entity or mapped super class. #333
Comments
Hello I have exactly the same problem. I tried following these instructions: But the result is the same. I'm on SF 6 and PHP 8 In the documentation we have to update our database with the new RefreshToken entity and absolutely nothing happens even when forcing the update. |
@LambertHumans after looking a second time the Following procedure : I have change the entity and It works now
|
@Lugh-Web, thanks for dropping this in! This also fixed my issue. |
I've been struggling for a while to set up this refresh token using SF 6.2 + API platform 3.1 using PHP8.2 It looks like there are conflicts between annotations and attributes, and that the RefreshTokenRepository cannot be reached inside the vendor directory. I searched on the web for similar issues, found several in 2022 but nothing really recent. Anyway I finally made it work by modifying the RefreshToken.php and placing the RefreshTokenRepository inside the project Repository folder. Here is the adjusted Entity
And the Repository simply copied from the vendor dir and pasted in the project
Hope this will help others |
Hi everyone,
I just installed Gesdinet JWT refresh token, but can't make it works. I'm facing this error :
Class "App\Entity\RefreshToken" sub class of "Gesdinet\JWTRefreshTokenBundle\Entity\RefreshToken" is not a valid entity or mapped super class.
I didn't made any change on bundle configuration, I only replaced refresh token route.
I'm using Sf6 with postgresql and php8.1.
Do you guys have an idea on how I can solve this ?
Thank you !
The text was updated successfully, but these errors were encountered: