How to resolve "django.core.exceptions.ImproperlyConfigured: Application labels aren't unique, duplicates: foo" in Django 1.7?

Question

On upgrading to Django 1.7 I'm getting the following error message from ./manage.py

$ ./manage.py 
Traceback (most recent call last):
  File "./manage.py", line 16, in <module>
    execute_from_command_line(sys.argv)
  File "/home/johnc/.virtualenvs/myproj-django1.7/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 427, in execute_from_command_line
    utility.execute()
  File "/home/johnc/.virtualenvs/myproj-django1.7/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 391, in execute
    django.setup()
  File "/home/johnc/.virtualenvs/myproj-django1.7/local/lib/python2.7/site-packages/django/__init__.py", line 21, in setup
    apps.populate(settings.INSTALLED_APPS)
  File "/home/johnc/.virtualenvs/myproj-django1.7/local/lib/python2.7/site-packages/django/apps/registry.py", line 89, in populate
    "duplicates: %s" % app_config.label)
django.core.exceptions.ImproperlyConfigured: Application labels aren't unique, duplicates: foo

What's the problem and how do I resolve it?

If you want to back older version, command pip install django==1.6.7 — KyungHoon Kim
– KyungHoon Kim, Commented Sep 13, 2014 at 0:02
You have twice the same app in the INSTALLED_APPS probably. — Anton Danylchenko
– Anton Danylchenko, Commented Feb 5, 2020 at 15:00

John Carter · Accepted Answer · 2016-05-16 23:14:55Z

122

The problem is that with the changes to apps in Django 1.7, apps are required to have a unique label.

By default the app label is the package name, so if you've got a package with the same name as one of your app modules (foo in this case), you'll hit this error.

The solution is to override the default label for your app, and force this config to be loaded by adding it to __init__.py.

# foo/apps.py

from django.apps import AppConfig

class FooConfig(AppConfig):
    name = 'full.python.path.to.your.app.foo'
    label = 'my.foo'  # <-- this is the important line - change it to anything other than the default, which is the module name ('foo' in this case)

and

# foo/__init__.py

default_app_config = 'full.python.path.to.your.app.foo.apps.FooConfig'

See https://docs.djangoproject.com/en/1.7/ref/applications/#for-application-authors

edited May 16, 2016 at 23:14

answered Jun 20, 2014 at 3:40

John Carter

55.7k28 gold badges116 silver badges144 bronze badges

Sign up to request clarification or add additional context in comments.

7 Comments

Brett Over a year ago

Questioner didn't accept his own answer, but it is correct. Once you do this, you place 'full.python.path.to.your.app.foo.apps.FooConfig' into your INSTALLED_APPS and everything works as expected.

Diego Sarmiento Over a year ago

Just wanted to mention, once you add the label run the migration like this: python manage.py makemigrations my.foo

Andrew Schmitt Over a year ago

Does this work for apps with existing database tables? I get a "dependencies reference nonexistent parent node" error when I make migrations after making these changes.

Gabe Rogan Over a year ago

@John_Carter What's a 'full.python.path.to.your.app.foo' normally look like? Does it involve os.path? Is it from the project root?

Mcmil Over a year ago

From my observation it's better to avoid dots in label name. The problem was with: AUTH_USER_MODEL = 'apps.auth.User' (won't work). Changing the label name and AUTH_USER_MODEL to 'apps_auth.User' solved the problem.

|

Julia Tamsma · Accepted Answer · 2015-03-18 16:11:04Z

102

I found simple solution for this. In my case following line is added twice under INSTALLED_APPS,

'django.contrib.foo',

Removed one line fixes the issue for me.

edited Mar 18, 2015 at 16:11

Julia Tamsma

151 silver badge4 bronze badges

answered Mar 15, 2015 at 18:30

yasirnazir

1,1851 gold badge7 silver badges12 bronze badges

3 Comments

jax Over a year ago

nice observation... it was a silly mistake .. worked for me :)

AlirezaAsadi Over a year ago

In my case there were two django.contrib.staticfiles. tnx alot =)

WHOATEMYNOODLES Over a year ago

@AlirezaAsadi that solved my problem! Thanks

David Wolf · Accepted Answer · 2022-04-05 10:29:24Z

25

I had the same error - try this:

In INSTALLED_APPS, if you are including 'foo.apps.FooConfig', then Django already knows to include the foo app in the application, there is therefore no need to also include 'foo'.

Having both 'foo' and 'foo.apps.FooConfig' under INSTALLED_APPS could be the source of your problem.

edited Apr 5, 2022 at 10:29

David Wolf

1,7382 gold badges14 silver badges21 bronze badges

answered May 2, 2017 at 12:32

Sean

2693 silver badges2 bronze badges

Comments

MBI · Accepted Answer · 2021-01-12 12:49:02Z

19

Well, I created a auth app, and included it in INSTALLED_APP like src.auth (because it's in src folder) and got this error, because there is django.contrib.auth app also. So I renamed it like authentication and problem solved!

edited Jan 12, 2021 at 12:49

answered Oct 5, 2017 at 23:11

MBI

1,42019 silver badges21 bronze badges

Comments

Pengyy · Accepted Answer · 2018-05-25 04:40:10Z

6

enter image description here I got the same problem. Here my app name was chat and in the settings.py , under installed apps i have written chat.apps.ChatConfig while i have already included the app name chat at the bottom. When i removed the chat.apps.ChatConfig mine problem was solved while migrations. This error may be due to the same instance that you might have defined you app name foo twice in the settings.py. I hope this works out!!

edited May 25, 2018 at 4:40

Pengyy

38.3k15 gold badges85 silver badges73 bronze badges

answered May 25, 2018 at 4:23

Alisha Sharma Chapai

1481 silver badge3 bronze badges

Comments

Ankush Sahu · Accepted Answer · 2020-04-17 10:40:53Z

6

please check if anything is duplicated in INSTALLED_APPS of settings.py

answered Apr 17, 2020 at 10:40

Ankush Sahu

6488 silver badges14 bronze badges

Comments

Obinna Onuoha · Accepted Answer · 2019-10-16 18:29:43Z

3

Had same issue, read through the settings.py of the root folder, removed any INSTALLED APPS causing conflict... works fine. Will have to rename the apps names

answered Oct 16, 2019 at 18:29

Obinna Onuoha

311 bronze badge

Comments

Leo · Accepted Answer · 2019-11-12 04:00:03Z

3

This exception may also be raised if the name of the AppConfig class itself matches the name of another class in the project. For example:

class MessagesConfig(AppConfig):
    name = 'mysite.messages'

and

class MessagesConfig(AppConfig):
    name = 'django.contrib.messages'

will also clash even though the name attributes are different for each configuration.

answered Nov 12, 2019 at 4:00

Leo

4696 silver badges5 bronze badges

Comments

sogu · Accepted Answer · 2020-04-03 14:54:04Z

3

In previous answer 'django.contrib.foo', was mentioned, but basically adding any app twice can cause this error just delete one (Django 3.0)

for me it was in settings.py

INSTALLED_APPS = [
  ...
  'accounts.apps.AccountsConfig',
  'accounts.apps.AccountsConfig',
  ...
]

just delete one of them

answered Apr 3, 2020 at 14:54

sogu

3,1467 gold badges43 silver badges98 bronze badges

Comments

Dan Swain · Accepted Answer · 2021-10-06 20:18:04Z

3

As therefromhere said this is a new Django 1.7 feature which adds a kind of “app registry” where applications must be determined uniquely (and not only having different python paths).

The name attribute is the python path (unique), but the label also should be unique. For example if you have an app named 'admin', then you have to define the name (name='python.path') and a label which must be also unique (label='my admin' or as said put the full python path which is always unique).

edited Oct 6, 2021 at 20:18

Dan Swain

3,1081 gold badge20 silver badges40 bronze badges

answered Oct 1, 2014 at 14:12

gdoumenc

5997 silver badges10 bronze badges

Comments

Saurabh Chandra Patel · Accepted Answer · 2020-02-13 08:08:35Z

2

Need to check in two file

1- apps.py

code something like

from django.apps import AppConfig
from django.utils.translation import ugettext_lazy as _
class ModuleConfig(AppConfig):
    name = "ocb.module_name"
    verbose_name = _("Module Name")

2 - init.py code something like

default_app_config = "ocb.users.apps.ModuleConfig"

default_app_config is pointed to your apps.py's class name

answered Feb 13, 2020 at 8:08

Saurabh Chandra Patel

13.7k7 gold badges94 silver badges80 bronze badges

Comments

Kolappan N · Accepted Answer · 2021-01-12 04:59:28Z

2

Basically this problem has been created due to duplication of name of installed app in the settings:

This is how I resolved the problem. In settings.py file:

Check the install app in the setting.py if the install app are duplicate
Error shown due to duplication of app name
Remove the duplicate name in the install file
After problem is resolved, you will see interface in your screen

For this I have created application name as polls instead of foo

edited Jan 12, 2021 at 4:59

Kolappan N

4,0413 gold badges40 silver badges45 bronze badges

answered Sep 12, 2020 at 16:09

nawaraj1111

671 bronze badge

Comments

CodeToLife · Accepted Answer · 2019-09-14 09:01:06Z

1

in my case, in mysite settings.py , in INSTALLED_APPS array variable I put the name of the app twice by mistake.

answered Sep 14, 2019 at 9:01

CodeToLife

4,2592 gold badges50 silver badges34 bronze badges

Comments

Laban · Accepted Answer · 2019-09-17 05:47:29Z

1

I had almost the same issue.

```File "/Users/apples/.local/share/virtualenvs/ecommerce-pOPGWC06/lib/python3.7/site-packages/django/apps/registry.py", line 95, in populate
"duplicates: %s" % app_config.label)

django.core.exceptions.ImproperlyConfigured: Application labels aren't unique, duplicates: auth```

I had installed Django.contrib.auth twice. I removed one and it worked well.

answered Sep 17, 2019 at 5:47

Laban

2,5521 gold badge16 silver badges15 bronze badges

Comments

DannyMoshe · Accepted Answer · 2020-06-22 19:11:45Z

1

From my experience, this exception was masking the real error. To see the real error (which in my case was an uninstalled python package) comment out the following in django/apps/registry.py:

if app_config.label in self.app_configs:
    # raise ImproperlyConfigured(
    #     "Application labels aren't unique, "
    #     "duplicates: %s" % app_config.label)
    pass

answered Jun 22, 2020 at 19:11

DannyMoshe

6,3257 gold badges36 silver badges57 bronze badges

Comments

Rakesh Gombi · Accepted Answer · 2021-07-24 14:03:18Z

0

Check for duplicates in INSTALLED_APPS inside the settings.py...If so remove one of it and rerun the command

answered Jul 24, 2021 at 14:03

Rakesh Gombi

3611 gold badge3 silver badges11 bronze badges

1 Comment

Eric Aya Over a year ago

This is the same solution as in this other answer.

rockikz · Accepted Answer · 2021-11-07 13:52:04Z

0

I had Django==3.2.9 when tried to test my existing Django app on a new environment. I had this exact issue and fixed it by downgrading to Django==3.1.13.

There seems to be an update to applications, check the Django 3.2 documentation for detailed information.

answered Nov 7, 2021 at 13:52

rockikz

6461 gold badge8 silver badges18 bronze badges

Comments

Paul Munyao · Accepted Answer · 2022-03-27 09:59:18Z

0

This error occurs because of duplication in your INSTALLED_APPS in settings.py file which is inside your project.

answered Mar 27, 2022 at 9:59

Paul Munyao

3352 silver badges12 bronze badges

Comments

Anay Damle · Accepted Answer · 2022-04-28 17:03:01Z

0

For me, the problem was that I had copy-pasted entire app instead of creating it using command line. So, the app name in the apps.py file was same for 2 apps. After I corrected it, the problem was gone.

answered Apr 28, 2022 at 17:03

Anay Damle

1

Comments

Artem_34_35 · Accepted Answer · 2023-07-25 18:57:10Z

0

I was able to solve the same problem. As I understand it, this happened due to the fact that I performed an incorrect copy of the folder when creating static files. In general, try to find all duplicates in the code. Look in the urls

answered Jul 25, 2023 at 18:57

Artem_34_35

1

Comments

Saicharan K R · Accepted Answer · 2019-11-14 09:21:24Z

-1

In case if you have added your app name in settings.py example as shown in figure than IN settings.py Remove it and Try this worked for me. give it a try . This Worked Because settings.py assumes installing it twice and does not allow for migration

answered Nov 14, 2019 at 9:21

Saicharan K R

214 bronze badges

Comments

idkthisnik · Accepted Answer · 2023-10-05 14:17:24Z

-1

just add unique label in apps.py and add path in init.py file of app.

answered Oct 5, 2023 at 14:17

idkthisnik

342 bronze badges

1 Comment

Community Over a year ago

Your answer could be improved with additional supporting information. Please edit to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers in the help center.

Collectives™ on Stack Overflow

How to resolve "django.core.exceptions.ImproperlyConfigured: Application labels aren't unique, duplicates: foo" in Django 1.7?

22 Answers 22

7 Comments

3 Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

1 Comment

Comments

Comments

Comments

Comments

Comments

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

22 Answers 22

7 Comments

3 Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

Comments

1 Comment

Comments

Comments

Comments

Comments

Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related