The generated migration drops the entire database about jwtrefreshtokenbundle HOT 3 OPEN

I think there is a clue as to why this is happening. I don't use doctrine mapping to manage my data. So it must be messing up the migration generation.

On the other hand, I think it should be fixed so that the migration generation only creates the bundle requirement without considering the rest of the db.

from jwtrefreshtokenbundle.

You should add the tables that you aren't using Doctrine to manage the mapping/schema for to your migrations configuration so that the Migrations library ignores them (see https://symfony.com/bundles/DoctrineMigrationsBundle/current/index.html#manual-tables for more on that). Otherwise, any time you run the doctrine:migrations:diff command, you're going to have the same type of issue.

None of the doctrine commands are coming from this bundle, and if it tried to do anything to manipulate them, it would just break other parts of your app.

from jwtrefreshtokenbundle.

I had the same problem and I changed the RefreshToken entity to the following which solved the problem:

use Doctrine\ORM\Mapping as ORM;
use Gesdinet\JWTRefreshTokenBundle\Entity\RefreshToken as BaseRefreshToken;
use Gesdinet\JWTRefreshTokenBundle\Entity\RefreshTokenRepository;

#[ORM\Entity(repositoryClass: RefreshTokenRepository::class)]
or
#[ORM\Entity]
#[ORM\Table(name: 'refresh_token')]
class RefreshToken extends BaseRefreshToken
{
}

Doctrine does not handle Attributes and Annotations used together in one project.
You can use the repository class or the second one, both works in my case

from jwtrefreshtokenbundle.