Crashing on Clicking "In Progress" in My Orders Section - Enatega Multivendor Rider App
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- mobile-dev
Research direction
Reproduce the crash in the Enatega Multivendor Rider App by opening My Orders and selecting an in-progress order on both iPhone and Android. Examine available crash logs to identify the failing area; done means the In Progress section opens and users can view and manage order details without the app crashing.
Written by the indexing model from the issue text.
Description
Describe the bug
Users of the Enatega Multivendor Rider App are encountering a critical issue where the application crashes consistently when attempting to access the "In Progress" section within the "My Orders" feature.
To Reproduce
Steps to reproduce the behavior:
Launch the Enatega Multivendor Rider App.
Navigate to the "My Orders" section.
Select an order that is currently in progress.
Attempt to access the "In Progress" section within the selected order.
Expected behavior
Users should be able to view and manage the details of orders currently in progress without any application crashes.
Smartphone:
Device: iPhone and android both
Additional context
The issue is replicable across different devices running the Enatega Multivendor Rider App.
Users have reported that the problem persists even after reinstalling the application.
Error messages or crash logs, if available, should be examined to identify the root cause.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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 gray-mueller/full-stack-document-solution
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
All issues in gray-mueller/full-stack-document-solution
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
aiko-chan-ai/DiscordBotClient#380 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
vercel/ai-elements#507 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 Half a day Newbie friendliness 84/100
anaclumos/qa-interns#148 · 1 comment ·
Maintainers usually reply within 1 day