Mobile Error Monitoring & Auto-Fix

Overview

BlueClerk automatically collects crash reports from the mobile app and uses AI to fix bugs before they impact more users. When the mobile app encounters an error, it sends a report to the server, which deduplicates similar crashes, tracks fix attempts, and triggers an automated bug-fix workflow using Claude AI.

How It Works

Automatic Crash Reporting

When the mobile app crashes or encounters an error:

1. Error report is sent to /api/mobile/error-report with type, message, stack trace, screen, and platform info
2. BlueClerk checks for duplicates - Same error message + stack trace in the last hour counts as a duplicate
3. Duplicates increment a counter instead of creating new reports
4. New errors trigger auto-fix - GitHub Actions workflow runs on the mobile repo

Auto-Fix Pipeline

For new, unique errors:

1. GitHub Actions receives the error via repository_dispatch event
2. Claude AI analyzes the stack trace to identify the bug
3. Claude generates a fix and pushes the code to the mobile repo
4. Error is marked as fix attempted with a timestamp

Recurring Error Detection

If the same error occurs again after a fix attempt:

• fixSuccessful is set to false - Indicates the fix didn't work
• Alerts developers that manual intervention is needed

What Gets Tracked

Each error report includes:

• Error type - JavaScript error, network failure, etc.
• Error message - What went wrong
• Stack trace - Code path that led to the error
• Screen name - Which screen the user was on
• Platform - iOS or Android
• App version - Which build encountered the error
• User ID - Who experienced the crash (if logged in)
• Metadata - Additional context like device info

Admin Visibility

Administrators can view error reports and fix status:

• Error count - How many times each error has occurred
• Fix attempts - Which errors have been addressed
• Recurring errors - Fixes that didn't resolve the issue
• Recent errors - Latest crash reports from the field

Tips

• Errors are deduplicated by message + stack trace - Minor variations still count as separate errors
• 48-hour window - Duplicates are only counted if they occur within an hour of each other
• Auto-fix is best-effort - Complex bugs may require manual developer intervention
• Recurring errors get flagged - If an error happens again after a fix, it's marked for manual review

Questions

Q: Will I be notified when my app crashes?
A: No, crash reports are collected silently. Admins can review error logs in the admin panel.

Q: Does this slow down the app?
A: No, error reporting happens asynchronously and doesn't block the UI.

Q: What if the auto-fix doesn't work?
A: The system marks it as a recurring error and alerts developers to investigate manually.

Q: Can I see which errors are most common?
A: Yes, admins can view error counts and frequency in the error log dashboard.