Chat Bar Reappearance and Transcript Email Prompt
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- javascript, react-native
- Domain
- mobile
Research direction
Start in the Enatega Multivendor Customer App's chat feature and trace the flow triggered by the End Session action. Reproduce the issue on iOS or Android, then verify that ending a session leaves only the transcript email prompt visible while the chat bar stays hidden.
Written by the indexing model from the issue text.
Description
Describe the bug
Within the Enatega Multivendor Customer App's chat feature, there is an issue where, upon clicking "End Session," the chat bar reappears along with a prompt to input the user's email address for the chat transcript. However, the intended behavior is for only the email input bar to be displayed, not the chat bar again.
To Reproduce
Open the Enatega Multivendor Customer App.
Initiate a chat session with a vendor.
Engage in the chat conversation.
When ready to end the session, click on "End Session."
Observe that the chat bar disappears momentarily but reappears along with a prompt to input the user's email address for the chat transcript.
Expected behavior
Upon clicking "End Session," the chat bar should disappear, indicating the termination of the chat session.
A prompt to input the user's email address for the chat transcript should appear without the reappearance of the chat bar.
The user should be able to input their email address for the transcript without distraction from the chat interface.
Screenshots
Untitled.video.-.Made.with.Clipchamp.mp4
Smartphone:
Device: IOS & Android
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
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.
More from raymondjames090/uber-eats-app-clone-using-react-native
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
raymondjames090/uber-eats-app-clone-using-react-native#2069 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
raymondjames090/uber-eats-app-clone-using-react-native#2003 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
raymondjames090/uber-eats-app-clone-using-react-native#2002 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
raymondjames090/uber-eats-app-clone-using-react-native#1979 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
raymondjames090/uber-eats-app-clone-using-react-native#1978 ·
All issues in raymondjames090/uber-eats-app-clone-using-react-native
Similar issues
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100