fix(mobile): resolve hardcoded Supabase anon key and document env vars (Fixes #1401)

[mvmax-dev]

This PR updates the MobileApp Supabase client configuration to correctly read credentials from environment variables using Expo's runtime prefix (EXPO_PUBLIC_). It removes hardcoded project credentials and completes the environment documentation in Frontend/.env.example.

Fixes #1401

[vercel]

@mvmax-dev is attempting to deploy a commit to the ritesh Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: c071b3ba-cf35-450e-a64c-a599ddaac02b

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[ritesh-1918]

Hi @mvmax-dev! 🙌

Thank you so much for your excellent contribution: "fix(mobile): resolve hardcoded Supabase anon key and document env vars (Fixes #1401)"! We really appreciate the high-quality code and effort you have put into the platform.

Just a quick, friendly heads-up as we prepare our manual merging and verification queues—please make sure to complete all the mandatory community steps listed below.

⚠️ Quick leaderboard tip: To secure the absolute highest GSSoC point tier for your contribution, please make sure you are following our project admin @ritesh-1918 manually on GitHub. Having all four onboarding steps cleared is highly preferable for manual PR approvals! ✨

Once those manual steps are verified, we'll get your PR officially merged into the gssoc branch (or keep it neatly cataloged if closed as integrated) and assign it the highest possible GSSoC S-Tier labels to maximize your leaderboard points!

Let's build something amazing together! 🚀🔥

---

🌟 Project Support & Developer Network (Show Some Love!)

As we prepare our manual verification and merging queues, please take a quick moment to ensure you have completed all four community steps:

1. ⭐ Star this repository: Helps our AI helpdesk get noticed! Star the repo here
2. 🍴 Fork this repository: Keep a copy to build your own cool tools! Fork here
3. 👤 Follow @ritesh-1918 on GitHub: Stay updated on real-time open-source projects! Follow ritesh-1918 here
4. 💼 Connect on LinkedIn: Let's build a strong engineering connection! Connect with Ritesh on LinkedIn

Note: Having all four steps completed manually is required before your PR points are officially cleared.

[ritesh-1918]

Merged locally into gssoc branch. Thank you for your GSSoC contribution! 🚀🔥

[mvmax-dev]

@ritesh-1918 Claiming bounty. My USDC (Base/Ethereum) Wallet Address for payout: 0x9758AdAe878bD4EA0d0aa24408c56D7d4aEC29a5