Add Local Development Troubleshooting section to CONTRIBUTING.md

[ankitasahu83964]

Description

The current CONTRIBUTING.md provides clear setup instructions for contributors, but it does not include guidance for resolving common local development issues that contributors may encounter during setup.

Adding a Local Development Troubleshooting section would help contributors quickly identify and resolve common problems, reducing setup time and improving the overall onboarding experience.

Proposed Changes

• Add a new Local Development Troubleshooting section to CONTRIBUTING.md.
• Include solutions for common setup issues such as:
  • Dependency installation failures (yarn install / pnpm install)
  • Node.js version mismatch
  • Expo CLI or Android emulator issues
  • pnpm quality check failures
  • Cache-related problems and recommended cleanup commands
• Add links to relevant documentation where appropriate.

Benefits

• Helps new contributors troubleshoot common setup problems.
• Reduces repetitive setup-related questions.
• Improves the onboarding experience.
• Makes the contribution process smoother and more efficient.

[github-actions]

Thank you for creating this issue! We'll look into it as soon as possible. Your contributions are highly appreciated! 😊

---

🤖 Assignment Guidelines

To get assigned to this issue, simply leave a comment requesting assignment.
The AI bot will automatically assign you if you meet the following eligibility criteria:

1. You do not currently have any other active assigned issues in this repository.
2. If you were previously assigned an issue, you must have submitted a Pull Request for it before requesting a new one.

[github-actions]

This issue covers a broad scope or requires architectural decisions.

Analysis: The issue provides a clear problem statement and proposed solution for enhancing contributor documentation, which is in scope. It is not a duplicate and does not involve doctor-related content. The task of adding a new troubleshooting section is of intermediate difficulty. It does not meet the criteria for maintainer escalation.

Escalating to @SB2318 for maintainer review.

[ankitasahu83964]

Hi @SB2318,

Just following up on this issue. I would love to work on it as part of GSSoC 2026. If it looks good, could you please assign it to me?

Thank you!

[github-actions]

Hello @ankitasahu83964! Your issue #2184 has been closed. Thank you for your contribution!