debugging-patterns

Debugging Patterns

Systematic debugging patterns for ABP Framework and React applications.

When to Use

• Investigating bugs or test failures
• Analyzing stack traces and error messages
• Diagnosing database query issues (N+1, tracking conflicts)
• Fixing async/await deadlocks
• Resolving React state management bugs

Debugging Process

1. Capture Information

• Error message and full stack trace
• Reproduction steps (reliable vs intermittent)
• Environment (dev/staging/prod)
• Recent code changes

2. Isolate the Problem

• Identify failing component (backend/frontend)
• Narrow down to specific file/function
• Check logs and network requests

3. Form Hypothesis

• Match error pattern to known issues
• Check similar past issues
• Review recent commits

4. Verify and Fix

• Test hypothesis with minimal change
• Verify fix doesn't break other things
• Add test to prevent regression

ABP Framework Issues

Authorization Failure

Error: Authorization failed for the request

Diagnosis Checklist:

1. Is permission defined in {Project}Permissions.cs?
2. Is permission granted to role in PermissionDefinitionProvider?
3. Is [Authorize] attribute using correct permission constant?

// Check permission definition
public static class ClinicPermissions
{
    public static class Patients
    {
        public const string Default = "Clinic.Patients";
        public const string Create = "Clinic.Patients.Create"; // Missing?
    }
}

// Check attribute matches
[Authorize(ClinicPermissions.Patients.Create)]  // Not .Default
public async Task<PatientDto> CreateAsync(...)

Entity Not Found

Error: Entity of type Patient with id X was not found

Diagnosis:

// Debug: Verify entity exists
var exists = await _repository.AnyAsync(x => x.Id == id);
_logger.LogDebug("Patient {Id} exists: {Exists}", id, exists);

// Fix: Use FirstOrDefaultAsync for graceful handling
var patient = await _repository.FirstOrDefaultAsync(x => x.Id == id);
if (patient == null)
{
    throw new UserFriendlyException("Patient not found");
}