Richard Tibbles

Hi @AlexVelezLl - to avoid the issues you're seeing it might be simpler to artificially restrict the space available by setting this option: https://github.com/learningequality/kolibri/blob/develop/kolibri/utils/options.py#L659 If you set it to close...

OK, so as I understand it the issue is that the user field on the LearnerDeviceStatus model is set as `OneToOneField`: https://github.com/learningequality/kolibri/blob/release-v0.16.x/kolibri/core/device/models.py#L613 Which enforces the constraint on both sides of...

The other thing I think we'd need to consider is the fact this is a syncable model, so I'd need to get a double check on how this might impact...

OK, in that case loosening the OneToOneField to a ForeignKeyField seems appropriate. Alternatively, if the intention is only to have a single LearnerDeviceStatus model per user, then we should be...

So, it seems that we want to change the OneToOneField to a ForeignKeyField. To handle the backwards compatibility issue, we will need to add some special sauce to ensure that...

Fixed in #12620

I guess that takes the uncertainty out of this! > This may well break Android

Looking at the logs, this is the same error you saw on my PR: https://github.com/learningequality/kolibri/pull/11974 - and doesn't seem to be directly related to this PR at all.

I will come back to this PR when the other one has been merged.

@radinamatic can you confirm the fix manually here, and then we can merge?