Inconsistent Checkout Behavior on Enatega Multivendor Customer App
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- javascript, react-native
- Domain
- mobile
Research direction
Reproduce the issue in the Enatega Multivendor Customer App by adding items to the cart, opening checkout, and switching between Credit/Debit Card and PayPal; review the attached WhatsApp video for the reported behavior. Done means the card option shows accurate information and the PayPal section opens so users can proceed with payment.
Written by the indexing model from the issue text.
Description
Description:
When users proceed to the checkout section in the Enatega Multivendor Customer App and attempt to switch payment methods, two distinct issues are observed:
Credit/Debit Card Section Displaying Incorrect Information:
Upon switching to the Credit/Debit Card payment option, the displayed information is inconsistent.
PayPal Section Not Opening:
When attempting to switch to the PayPal payment option, the app fails to open the PayPal section.
Steps to Reproduce:
Open the Enatega Multivendor Customer App.
Add items to the cart.
Proceed to the checkout section.
Switch to the Credit/Debit Card payment option and observe the displayed information.
Attempt to switch to the PayPal payment option and observe if the PayPal section opens as expected.
Expected Results:
When switching to the Credit/Debit Card payment option, accurate and consistent payment information should be displayed.
When switching to the PayPal payment option, the app should smoothly open the PayPal section, allowing users to proceed with PayPal payment.
Actual Results:
The Credit/Debit Card section displays inconsistent or incorrect information.
The PayPal section fails to open, preventing users from proceeding with PayPal payment.
WhatsApp.Video.2023-12-19.at.16.44.49_fec88836.mp4
- 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