Sameer Shanbhag (Inactive) added a comment - 07/Aug/19 4:35 PM Error :URL namespace 'social' isn't unique. You may not be able to reverse all URLs in this namespace File: "users/urls.py" Line: path(r'', include('social_django.urls', namespace='social')) Explanation: The namespace='social' is a problem here, Usually this warning occurs when same namespace is used to define different paths. Can be solved by changing the namespace to something else other than social at on of the places where namespace is mentioned. Error: submit_app.AppPending.dependencies: (fields.W340) null has no effect on ManyToManyField. File: submit_app/models.py Line: dependencies = models.ManyToManyField(Release, related_name='+', blank=True, null=True) Explanation: As mentioned at : https://stackoverflow.com/questions/18243039/migrating-manytomanyfield-to-null-true-blank-true-isnt-recognized "null" doesn't mean anything at the database level when used with a ManyToManyField. The declaration of a ManyToManyField causes the creation of an intermediate table to hold the relationship, and although Django will create a standard attribute on your model instance for your convenience, there is no actual column representing it that could be nulled. By definition there can always be zero instances of the relationship. blank=True/False, though, does have an effect on the admin app, forcing the user to choose at least one relation. Solution: removing null=true will allow us to get rid of the warning.