Fix AttributeError: 'NoneType' object has no attribute 'id' in Django

This error occurs when you access the .id attribute on a variable that is None, typically because a Django ORM query returned None instead of a model instance. Fix it by using get_object_or_404 to return a proper 404 response, or add a None check before accessing attributes on the query result.

Reading the Stack Trace

Here's what each line means:

• File "/app/src/views.py", line 24, in user_profile: The view function user_profile at line 24 accesses .id on a variable that is None.
• profile_id = user.id: The user variable is None because the preceding query (e.g., User.objects.filter().first()) found no matching record.
• response = wrapped_callback(request, *callback_args, **callback_kwargs): Django's request handler called the view, which crashed before it could return a response.

Common Causes

def user_profile(request, username):
    user = User.objects.filter(username=username).first()
    profile_id = user.id
    return render(request, 'profile.html', {'profile_id': profile_id})

def dashboard(request):
    user = request.user
    company_id = user.profile.company.id  # profile or company could be None
    return render(request, 'dashboard.html', {'company_id': company_id})

The Fix

Replace the .filter().first() pattern with get_object_or_404, which raises Http404 if no matching record exists. This returns a proper 404 response instead of crashing with an AttributeError.

def user_profile(request, username):
    user = User.objects.filter(username=username).first()
    profile_id = user.id
    return render(request, 'profile.html', {'profile_id': profile_id})

from django.shortcuts import get_object_or_404, render

def user_profile(request, username):
    user = get_object_or_404(User, username=username)
    profile_id = user.id
    return render(request, 'profile.html', {'profile_id': profile_id})

Testing the Fix

import pytest
from django.test import RequestFactory
from django.contrib.auth.models import User
from django.http import Http404
from views import user_profile


@pytest.fixture
def factory():
    return RequestFactory()


@pytest.fixture
def user(db):
    return User.objects.create_user(username='alice', password='testpass')


@pytest.mark.django_db
def test_user_profile_returns_200_for_existing_user(factory, user):
    request = factory.get('/profile/alice/')
    response = user_profile(request, username='alice')
    assert response.status_code == 200


@pytest.mark.django_db
def test_user_profile_returns_404_for_missing_user(factory):
    request = factory.get('/profile/nonexistent/')
    with pytest.raises(Http404):
        user_profile(request, username='nonexistent')

Run your tests:

pytest

Pushing Through CI/CD

git checkout -b fix/attributeerror-nonetype-user,git add src/views.py tests/test_views.py,git commit -m "fix: use get_object_or_404 to handle missing users gracefully",git push origin fix/attributeerror-nonetype-user

Your CI config should look something like this:

name: CI
on:
  pull_request:
    branches: [main]
jobs:
  test:
    runs-on: ubuntu-latest
    services:
      postgres:
        image: postgres:15
        env:
          POSTGRES_DB: test_db
          POSTGRES_USER: postgres
          POSTGRES_PASSWORD: postgres
        ports:
          - 5432:5432
        options: >-
          --health-cmd pg_isready
          --health-interval 10s
          --health-timeout 5s
          --health-retries 5
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-python@v5
        with:
          python-version: '3.11'
      - run: pip install -r requirements.txt
      - run: pytest --tb=short
        env:
          DATABASE_URL: postgres://postgres:postgres@localhost:5432/test_db

The Full Manual Process: 18 Steps

Here's every step you just went through to fix this one bug:

1. Notice the error alert or see it in your monitoring tool
2. Open the error dashboard and read the stack trace
3. Identify the file and line number from the stack trace
4. Open your IDE and navigate to the file
5. Read the surrounding code to understand context
6. Reproduce the error locally
7. Identify the root cause
8. Write the fix
9. Run the test suite locally
10. Fix any failing tests
11. Write new tests covering the edge case
12. Run the full test suite again
13. Create a new git branch
14. Commit and push your changes
15. Open a pull request
16. Wait for code review
17. Merge and deploy to production
18. Monitor production to confirm the error is resolved

Total time: 30-60 minutes. For one bug.

pip install bugstack

import bugstack

bugstack.init(api_key=os.environ["BUGSTACK_API_KEY"])

Deploying the Fix (Manual Path)

1. Run pytest locally to confirm the view handles missing users with a 404.
2. Open a pull request with the get_object_or_404 change.
3. Wait for CI checks to pass on the PR.
4. Have a teammate review and approve the PR.
5. Merge to main and verify the 404 page renders correctly in staging.

Frequently Asked Questions