Egor Poderiagin

> * I would have auto expired all tokens that have an `updated_at` date (not `created_at` older than 30 days. @Eraldo There are nuances to this way of doing things,...

@xtrinch example [here](https://github.com/xtrinch/fcm-django-web-demo/pull/32) . Let me know if you would like have any changes in this PR.

so i have todo: - [x] 1. Move pytest to pyproject - [x] 2. Add docs about there will be two separate models if swapper used, and you have to...

@xtrinch If there is expected anything else than let me know.

@xtrinch , @olzhasar Is there a decision to be made? Or are we not moving in that direction with swapper yet?

> this PR can have so many unintended consequences and unintended issues I can't imagine any of that problem. In this PR most of the code is documentation and changes...

I bet it's the same error as it was with [MySQL](https://github.com/xtrinch/fcm-django/commit/f3699515f97cabb278d6f5d0b98ed73f4f9f3a6d) https://github.com/xtrinch/fcm-django/issues/236 Solution was to skip that migration on DB that doesn't supports such constraints.

> Is there any chance we could get a proper fix for this? I see few solution here 1. Run those migrations as `--fake` flag since they doesn't supported by...

> Do you know when 2.2.0 will be fully released? @jonesnc No, I don't know. But you can specify rc version `2.2.0rc0` during installation. I think we expect someone to...

I though that is not trouble of django-rest-auth. You get CSRF error because forget setup way for authenticate. And if you use SessionAuthentication you must send CSRF token with every...