[UX] Add Chatbot Retry Button for Failed Messages in Offline State

[dinesh9997]

Files Involved:

frontend/src/screens/ChatbotScreen.tsx

Description:

• When the app is offline, sending a message in the chatbot prints a text message: "Unable to connect. Please check your internet connection and try again." However, the user has no quick way to retry sending the message once connection is restored. They have to type the prompt again manually.

Suggested Fix:

• Render a "Retry" button under failed messages.
• Implement a retry handler that pulls the originalPrompt stored in the failed message metadata and calls performSendMessage(prompt) once the network is connected.

[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 has been triaged as a frontend task (level:intermediate).

Expected Effect & Scope: The issue provides a clear problem statement and a suggested fix for a frontend-mobile UX enhancement. It is within scope and not a duplicate. The complexity is intermediate as it involves UI rendering, state management, and network handling.

It is now open for community contribution!

Hi @dinesh9997, I couldn't assign this to you automatically because you have previously been assigned issue(s) (#1566) that are now closed, but no Pull Request referencing those issues was found.

To be eligible for a new assignment, please submit a Pull Request that explicitly mentions your assigned issue (e.g. Fixes #1566, Closes #1566, or #1566 in the PR body/title).

This rule ensures contributors complete and deliver their work before taking on new tasks. If you believe this is a mistake, please reach out to a maintainer @SB2318.

---

🤖 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 that references that assigned issue before requesting a new one.

[dinesh9997]

Hi @SB2318 — the bot says no PR was found for my previous issue, but #1718 explicitly fixed and closed #1566, and it was merged 3 weeks ago. Could you manually assign this issue to me? Thanks!

[github-actions]

@dinesh9997 You have previously been assigned issue(s) (#1566) that are now closed, but no Pull Request referencing those issues was found.

To be eligible for a new assignment, please submit a Pull Request that explicitly mentions your assigned issue (e.g. Fixes #1566, Closes #1566, or #1566 in the PR body/title).

This rule ensures contributors complete and deliver their work before taking on new tasks. If you believe this is a mistake, please reach out to a maintainer @SB2318.

[saurabhhhcodes]

/assign

[github-actions]

@saurabhhhcodes You have previously been assigned issue(s) (#1908, #1531, #1076, #1018, #676) that are now closed, but no Pull Request referencing those issues was found.

To be eligible for a new assignment, please submit a Pull Request that explicitly mentions your assigned issue (e.g. Fixes #1908, Closes #1908, or #1908 in the PR body/title).

This rule ensures contributors complete and deliver their work before taking on new tasks. If you believe this is a mistake, please reach out to a maintainer @SB2318.

[Babul422]

/assign

[github-actions]

@Babul422 You have previously been assigned issue(s) (#1670) that are now closed, but no Pull Request referencing those issues was found.

To be eligible for a new assignment, please submit a Pull Request that explicitly mentions your assigned issue (e.g. Fixes #1670, Closes #1670, or #1670 in the PR body/title).

This rule ensures contributors complete and deliver their work before taking on new tasks. If you believe this is a mistake, please reach out to a maintainer @SB2318.

[Babul422]

Hi @SB2318,

I believe this might be a mistake. I was previously assigned issue #1670, submitted a PR for it, and it has already been merged. I also received the contribution points.

However, the assignment bot says that no PR referencing the issue was found, so I'm unable to get a new issue assigned.

Could you please check and help resolve this?

Thank you!

[github-actions]

@Babul422 You have previously been assigned issue(s) (#1670) that are now closed, but no Pull Request referencing those issues was found.

To be eligible for a new assignment, please submit a Pull Request that explicitly mentions your assigned issue (e.g. Fixes #1670, Closes #1670, or #1670 in the PR body/title).

This rule ensures contributors complete and deliver their work before taking on new tasks. If you believe this is a mistake, please reach out to a maintainer @SB2318.