Django allauth创建用户时触发IntegrityError问题求助

Alright, let's tackle this frustrating duplicate user issue you're facing. The error duplicate key value violates unique constraint "auth_user_username_key" popping up even when the username didn't exist initially, and then seeing the user appear in the database, points to the system triggering user creation twice during a single signup attempt. Let's break down the likely causes and fixes:

First, Let's Rule Out Common Culprits #

You already confirmed you didn't set ACCOUNT_USER_MODEL_USERNAME_FIELD=None, so we can cross that off the list. Now let's look at the parts you shared:

1. Check Your Custom Signup Form (UserCreateForm) #

Since you're using ACCOUNT_SIGNUP_FORM_CLASS, this form is integrated into allauth's signup flow. A common mistake here is:

• Incorrect form inheritance: If your UserCreateForm inherits from Django's built-in UserCreationForm instead of allauth.account.forms.SignupForm, allauth might end up running its own user creation logic on top of your form's logic, leading to duplicate saves.
• Redundant save() calls: If you overrode the save() method in your form and accidentally called user.save() twice, or called it in addition to the parent class's save() (which allauth already uses to persist the user), that would create duplicates.

Fix:
Ensure your form inherits from allauth's base signup form, and keep the save() method clean:

from allauth.account.forms import SignupForm

class UserCreateForm(SignupForm):
    # Add your custom fields here (if any)
    
    def save(self, request):
        # Let allauth handle the core user save
        user = super().save(request)
        # Add your custom logic here (e.g., setting profile fields)
        # Only save additional objects here, not the user itself again
        return user

2. Prevent Frontend Double Submissions #

It's easy for users to double-click the signup button, sending two identical POST requests to your server. The first request creates the user successfully, the second hits the unique constraint error.

Fix:
Add a simple JavaScript snippet to disable the submit button after the first click:

document.getElementById('signup_form').addEventListener('submit', function(e) {
    const submitBtn = this.querySelector('button[type="submit"]');
    submitBtn.disabled = true;
    submitBtn.textContent = 'Signing Up...'; // Optional: Give feedback
});

3. Check for Duplicate Request Handling #

Sometimes middleware or misconfigured URL patterns can cause a request to be processed twice. For example:

• Accidentally mapping the account_signup URL to two different views in your urls.py
• A middleware that's re-sending the request or processing it multiple times

Fix:

• Review your urls.py to ensure the signup URL is only defined once.
• Temporarily disable non-essential middleware one by one to see if the issue goes away.

4. Verify Allauth's Signup Flow Hooks #

If you've customized allauth's adapters (e.g., a custom AccountAdapter), check if your save_user method is being called twice or has extra user creation logic. Allauth's default adapter handles user creation once during signup—any extra calls here would cause duplicates.

Debugging Step:
Add logging to track how many times user creation is triggered:

• In your custom form's save() method: print("Form save called")
• Enable DEBUG logging for allauth in settings.py to see its internal flow:

LOGGING = {
    'version': 1,
    'disable_existing_loggers': False,
    'handlers': {
        'console': {
            'class': 'logging.StreamHandler',
        },
    },
    'loggers': {
        'allauth': {
            'handlers': ['console'],
            'level': 'DEBUG',
        },
    },
}

This will show you exactly when allauth is trying to create the user.

Final Notes #

Since you've narrowed this down to a minimal reproducible case, start with the frontend fix first (it's quick to test), then move on to checking your custom form inheritance. These are the most likely causes for this specific duplicate creation issue with allauth.

内容的提问来源于stack exchange，提问作者victor james