Mojca Rojko

@Akay I think that kind of depends on the update strategy that the developer chooses.. Let's for example say we'd just update the device instance on a new token -...

@Akay7 I'm not sure what you mean by recognize. You'd basically just maintain one device instance per user - it shouldn't be that hard to securely upsert the device instance...

Yeah, well I'm guessing most use cases will involve one user having multiple devices but you never know. I'd still add the update date to the base model, it doesn't...

Yes that also sounds like a valid use case with this time based auto-expiry instead of expiry-on-error @Eraldo .

@henriklindgren was kind enough to provide us with a test example in https://github.com/xtrinch/fcm-django/pull/240, so perhaps we can use that to add additional tests for this PR

@henriklindgren / @olzhasar If any of you have any extra time on your hands, maybe throw an eye on this PR 🙏

I don't mind using swapper, overall it looks fine. But since this PR can have so many unintended consequences and unintended issues, I'm reluctant to just merge this and I...

Thanks @Karol-Grabczak, labeled as fix next release

See 2.1.0

See https://github.com/xtrinch/fcm-django/releases/tag/2.2.1 that offers a mysql compatibility setting which will circumvent this error.