[Bug] MobileFormInput.tsx unhandled promise in useEffect with void operator

[RUKAYAT-CODER]

Overview

MobileFormInput.tsx calls an async function inside useEffect using the void operator to suppress the TypeScript warning. This discards any rejection from the async call, leaving form initialization errors completely silent.

Specifications

Features:

• Remove the void suppression
• Handle the promise properly with a try/catch inside the effect
• Surface form cache loading errors to the user or log them to Sentry

Tasks:

• Refactor the effect to use an inner async IIFE with try/catch
• Add an error state that disables the field with an error message on failure
• Write a test that mocks the cache call to reject and confirms error state

Impacted Files:

• src/components/common/MobileFormInput.tsx

Acceptance Criteria

• Form cache errors are not silently swallowed
• Field shows an error state if cache load fails
• Error is logged to Sentry

[sheyman546]

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

please i will love to work on these issue

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

[Dhivine-stack]

@Dhivine-stack has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hello! I've reviewed the issue and understand what's required. I have a clear plan for the implementation and will ensure the solution is maintainable, aligns with the project's standards, and satisfies the acceptance criteria. Kindly assign it to me.

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

[benzeneCLI]

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

Hi, I'd like to take this on.

I have hands-on experience with backend development, databases, and API design, as well as frontend work with React and modern CSS. I write tested, maintainable code and enjoy contributing to open source projects.

I've reviewed the issue and I'm confident I can implement a solid solution while following the project's conventions.

I'd appreciate being assigned to this issue and look forward to contributing.

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

[drips-wave]

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

🧑‍💻 @benzeneCLI: 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 @benzeneCLI as part of the Stellar Wave Program's 7th Wave 🥳

😎 @benzeneCLI: You earned 200 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.