Add automatic error log reporting and user log submission button

[yedidyakfir]

Summary

When the app encounters a failure, logs should be automatically sent to the developer for debugging. Additionally, users should have the ability to manually send logs along with a description of the error they experienced.

Features / Details

• Automatic log reporting on failure: When the app crashes or encounters an unhandled error, automatically collect and send relevant logs to the developer
• User-facing "Send Logs" button: Add a UI button that allows users to manually report issues
• Error description field: When the user clicks the button, show a form where they can describe what went wrong
• Log collection: Gather relevant application logs, error traces, and system context to include in the report

Use Cases

• App crashes unexpectedly — developer receives logs automatically without user intervention
• User encounters a bug or unexpected behavior — they click "Send Logs", describe the issue, and submit it
• Developer can correlate automatic crash reports with user-submitted descriptions for faster debugging

Implementation Considerations

• Decide on log transport mechanism (email, webhook, external service, etc.)
• Define what log data to collect (last N lines, error traces, system info)
• Consider privacy — ensure no sensitive user data is sent without consent
• Add rate limiting to prevent log spam
• UI placement of the "Send Logs" button (settings page, error screen, persistent footer, etc.)

Tasks

• Design log collection strategy (what data to capture, retention, format)
• Implement automatic error detection and log dispatch on app failure
• Build "Send Logs" button in the UI
• Create error description form/modal for user submissions
• Set up backend endpoint or service to receive and store log reports
• Add user consent/privacy notice before sending logs
• Test automatic reporting with simulated failures
• Test manual log submission flow end-to-end