Margaret-Petersen / Margaret-Petersen/uber-eats-clone-using-react-native
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)
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
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.
Smartphone (please complete the following information):
Device: [e.g. Samsung A15]
OS: [e.g. Android]
Browser [e.g. Chrome]
Version [e.g. 22]
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue from the Chat with Rider screen on Android and iOS. Inspect the chat message receiving and Send-button handling, including rapid taps and empty messages. Done means incoming rider messages appear in real time, repeated taps do not crash the app, and empty messages are not sent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react-native
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100