Enatega Customer App: Chat with Rider not receiving real-time messages and crashes on multiple send taps (Android) and empty msg being send on (IOS)

Open
#814 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript
Domain
mobile

Research direction

Start at the Customer App's "Chat with Rider" screen and reproduce the reported real-time message delay and Android crash when Send is tapped repeatedly. Also verify the reported iOS empty-message behavior; done means incoming messages update in real time, repeated sends do not crash, and empty messages are not sent.

Written by the indexing model from the issue text.

Description

Describe the bug
The chat functionality between users and riders is not working as expected. Messages from the rider are not received in real time, causing a delay or failure in updating the chat view. Additionally, when the "Send" button is tapped rapidly multiple times, the application crashes unexpectedly.

Steps to Reproduce:

Open the "Chat with Rider" screen.
Wait for incoming messages from the rider.
Observe that messages are not received/displayed in real time.
Type a message in the input field.
Tap the Send button rapidly multiple times.
Observe that the app crashes.
Expected behavior

Incoming messages should appear in the chat view in real time.
Tapping the Send button multiple times should not crash the app. Ideally, the button should be disabled temporarily after the first tap until the message is sent.
Screenshots

XRecorder_20250506_01.mp4
Smartphone (please complete the following information):

Device: [e.g. Samsung A15]
OS: [e.g. Android]
Browser [e.g. Chrome]
Version [e.g. 22]

Dominant language
JavaScript
Stars
0
Forks
0
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from raymondjames090/food-ordering-system-java-eclipse

All issues in raymondjames090/food-ordering-system-java-eclipse

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.