gray-mueller / gray-mueller/ride-management-system-react-native
Payment Method Hangs on Loading - Enatega Multivendor Customer App (PayPal)
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
Users are encountering a critical issue in the Enatega Multivendor Customer App when attempting to switch the payment method to PayPal. The app becomes unresponsive and gets stuck on the loading screen, preventing users from progressing further in the payment process.
To Reproduce
Steps to reproduce the behavior:
Open the Enatega Multivendor Customer App.
Navigate to the payment section during the checkout process.
Choose PayPal as the payment method.
Observe the app behavior as it attempts to load the PayPal payment interface.
Expected behavior
Issue Description: Payment Method Hangs on Loading - Enatega Multivendor Customer App (PayPal)
Issue Summary:
Users are encountering a critical issue in the Enatega Multivendor Customer App when attempting to switch the payment method to PayPal. The app becomes unresponsive and gets stuck on the loading screen, preventing users from progressing further in the payment process.
Steps to Reproduce:
Open the Enatega Multivendor Customer App.
Navigate to the payment section during the checkout process.
Choose PayPal as the payment method.
Observe the app behavior as it attempts to load the PayPal payment interface.
Expected Behavior:
After selecting PayPal as the payment method, the app should seamlessly transition to the PayPal payment interface without any delays or hang-ups.
Screenshots
https://github.com/ninjas-code-official/food-delivery-multivendor/assets/152266796/5aac52a1-0c5d-44f2-83f0-06339da6c7f1
Smartphone:
Device: iOS and Android
Contributor guide
Research direction
Reproduce the checkout flow on iOS and Android by selecting PayPal, then trace the payment-method loading flow in the customer app. Done means selecting PayPal reaches the payment interface without hanging; no specific source file or test is named, so the relevant entry point must first be located.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native, typescript
- Domain
- mobile, payments
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100