Crash Reporting Not Integrated

[RUKAYAT-CODER]

Description

Overview
Crash reporting service exists but may not be properly initialized.

Background
src/services/crashReporting.ts exists but may not be wired to app startup, leaving unhandled errors untracked.

Specifications

• Initialize crash reporting at app startup
• Add global error handlers
• Send crash reports on unhandled rejections

Tasks:

• Initialize crashReporting at startup
• Add error listeners
• Set up alerts for production

Impacted Files:

• src/services/crashReporting.ts
• App.tsx

Labels: monitoring, priority-medium

🙌Contribution Guidelines:
Assignment required before PR submission
Timeframe: 48-72 hours
PR description must include: Close #11
Star the repo⭐
For more context, please refer to the mobile README

[felladaniel36-hash]

@felladaniel36-hash has applied to work on this issue as part of the Stellar Wave Program's 4th wave.

I would like to tackle this issue by properly integrating the existing crash reporting service into the teachLink_mobile application lifecycle. My technical approach involves wiring the crashReporting.ts service directly into the app startup in App.tsx and implementing global error listeners to capture unhandled exceptions and promise rejections. By setting up these production alerts, I will ensure that the development team has full visibility into critical failures, allowing for proactive debugging and a more stable user experience.
I have expertise on this issue and would love to tackle this issue again because I have a strong background in mobile application monitoring and stability. I understand the importance of capturing telemetry at the earliest possible stage of execution to ensure no edge-case crashes go untracked. My commitment to the 48-72 hour timeframe ensures that your monitoring infrastructure will be fully operational and properly documented according to your contribution guidelines.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @felladaniel36-hash to this issue.

[drips-wave]

Congratulations, @felladaniel36-hash! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on April 29, 2026.

🧑‍💻 @felladaniel36-hash: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been completed by @felladaniel36-hash as part of the Stellar Wave Program's 4th Wave 🥳

😎 @felladaniel36-hash: You earned 150 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.