lambertf917 / lambertf917/react-native-uber-eats-clone
page rendered nowhere during testing
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 3
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
crashed
To Reproduce
Steps to reproduce the behavior:
happened out of nowhere
Expected behavior
A clear and concise description of what you expected to happen.
image
Desktop (please complete the following information):
OS: Windows
Browser Chrome
Version 122.0.6261.95 (Official Build) (64-bit)
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
The report mentions only a crash and a page that rendered nowhere during testing on Windows with Chrome 122. Start by reproducing the failure in the react-native application and identify the affected page or entry point; done means the page renders normally and the crash no longer occurs in the reported environment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react-native
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100