[Django]-ValueError: Related model u'app.model' cannot be resolved

Try running migrations one by one for every model.

This way you can debug the app you are facing problem with

python manage.py migrate appmname

I just got the same error, but referring to a model that was declared as part of the same migration. It turned out that the first migrations.CreateModel(...) referred to a not yet declared model. I manually moved this below the declaration of the referred model and then everything worked fine.

In my case, It was the cache and previous migrations that resulted in this error. I removed __pycache__ and migrations folder and then re-run the migrations command and it worked.

Remember, when you’ll do python manage.py makemigrations it won’t see any new migrations and will console output no changes detected. You’ll have to do python manage.py makemigrations your_app_name instead to make things work.

I encountered this error when trying to use a child model of a base model as a foreign key. It makes sense that it didn’t work because there’s not an id field on the child model. My fix was to use the parent on the key. Unfortunately this was not immediately intuitive and set me back a couple hours.

Depending on your situation, using run_before may resolve your issue.

For me, I hit the error while running Applying admin.0001_initial.. so django admin was not respecting the order of operations. I added this to my migration file that was adding a new user table:

    run_before = [
        ('admin', '__first__'),
    ]

This resolved my issue.

The detail of my specific issue is that django admin’s migration depends on the first migration of my app whereas my User is added much later. This means my user table doesn’t exist when admin tries to run migrations.

I have found that it looks like this bug was not fixed yet when you scroll down to the bottom.

Django ValueError: Related model cannot be resolved Bug

I am using 1.11.7, they are talking about 1.9.3.

It worked everything on localhost, but was always failing on Heroku, so I tested all the options/answers above and nothing worked.

Then I have noticed, localhost DB in Admin I had 1 profile created (1 DB record), went to Heroku and DB has 0 records for Profile table so I have added 1, pushed the migration, python manage.py migrate and all it went OK.

That validates that I did not need to change any of those migrations manually that all is working.

Maybe it will help to someone.

migrations

# -*- coding: utf-8 -*-
# Generated by Django 1.11.7 on 2017-11-23 21:26
from __future__ import unicode_literals

from django.db import migrations, models
import django.db.models.deletion


class Migration(migrations.Migration):

    dependencies = [
         ('blog', '0005_blog_author'),
    ]

    operations = [
        migrations.AlterField(
             model_name='blog',
             name='author',

field=models.ForeignKey(on_delete=django.db.models.deletion.CASCADE, 
to='core.Profile'),
        ),
    ]

order of dependencies is too important.

in your case, ook must be created first then depend eek on it.

dependencies= [
    ('ook', '0001_initial'),
    ('eek', '0002_auto_20151029_1040'),
    ]