You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Im migrating a django 1.10 app from PSA==0.3.5 to social-auth-app-django==1.0.0 +
social-auth-core==1.0.1 and am running into some migration issues on a related table.
class SocialAuthExpiration(models.Model):
social_auth = models.OneToOneField(
UserSocialAuth,
on_delete=models.CASCADE,
related_name='token_expiration'
)
...
Im encountering this error: ValueError: Related model u'social_django.UserSocialAuth' cannot be resolved
Social Django is installed. Plus I'm able to create new UserSocialAuth objects. I've attempted changing the to field to 'social.UserSocialAuth' as well, to no avail.
INSTALLED_APPS = [
...
# Social Auth
'social_django',
# Local dev utils/runserver
'django_extensions',
# Hueya Apps
'accounts', <<< New model and migration live here
...
]
Thank you for the response and quick update. I suspected this had to do with my migrations getting out of sync. So I went nuclear & blew out that migration history and dropped those tables.
I had no issue applying the 1.0.1 social-auth-django migrations. Nor did anything go awry with the loaddata command. Subsequent migrations with relations to social_django are also working as intended.
Im migrating a django 1.10 app from PSA==0.3.5 to social-auth-app-django==1.0.0 +
social-auth-core==1.0.1 and am running into some migration issues on a related table.
While applying this migration:
For this model:
Im encountering this error:
ValueError: Related model u'social_django.UserSocialAuth' cannot be resolved
Social Django is installed. Plus I'm able to create new UserSocialAuth objects. I've attempted changing the to field to 'social.UserSocialAuth' as well, to no avail.
django_migrations table relevant rows:
Im hoping someone has had some experience with this and might be able to point me in the right direction. Thanks.
The text was updated successfully, but these errors were encountered: