[Enhancement] Implement per-screen error boundaries to prevent full app crash on component errors

[RUKAYAT-CODER]

Overview

The app has a global error boundary at the root level but no screen-level boundaries. A runtime error in MobileProfile unmounts the entire navigation tree, showing the root error boundary UI (likely a blank screen or generic 'Something went wrong') and forcing a full app reload. With per-screen boundaries, only the affected screen shows an error UI while the rest of the app remains functional.

Specifications

Features:

• ScreenErrorBoundary component wrapping each major screen
• Error UI: 'This screen encountered an error' with 'Retry' and 'Go Home' buttons
• Error details sent to Sentry from componentDidCatch
• User can recover without full app restart

Tasks:

• Create src/components/common/ScreenErrorBoundary.tsx as class component
• componentDidCatch sends error to Sentry with screen context tag
• Wrap each screen in expo-router layout with ScreenErrorBoundary
• 'Retry' button calls this.setState({ hasError: false }) to unmount/remount screen
• Add unit test rendering error state and confirming recovery

Impacted Files:

• src/components/common/ScreenErrorBoundary.tsx (create)
• src/app/ or expo-router layout files

Acceptance Criteria

• Error in MobileProfile does not crash navigation or other screens
• Error UI shows with Retry and Go Home buttons
• Sentry receives error event with screen name context tag
• Retry button successfully re-renders screen after dismissing error state

[Killerjunior]

@Killerjunior has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi maintainer, I have read and understood the issue requirements and checked the necessary documentation. I’m confident I can work on this task effectively and deliver a proper solution.

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

[ayshadogo]

@ayshadogo has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Good day

I have read the requirements of this issue and i am confident that i can solve this

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

[drips-wave]

Congratulations, @ayshadogo! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @ayshadogo: 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 🌊