Brb login without WiFi infinitely spins
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 45/100
Research direction
Start by locating the login flow and its network-request error handling in the Android project. Reproduce login without WiFi, then identify the existing loading state and error display. Done means a failed network request shows the requested message instead of spinning indefinitely.
Written by the indexing model from the issue text.
Description
Make an error display of "failed due to bad network request" to the user
- Dominant language
- Java
- Stars
- 7
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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 cuappdev/eatery-android
-
App Crashes Open
Difficulty 3/5 1-2 days Newbie friendliness 35/100
cuappdev/eatery-android#224 ·
-
Priority: Low Type: Design
Difficulty 3/5 1-2 days Newbie friendliness 35/100
cuappdev/eatery-android#211 ·
-
Priority: Low Starter Task Type: Bug
Difficulty 3/5 1-2 days Newbie friendliness 38/100
cuappdev/eatery-android#202 ·
-
Priority: High Starter Task Type: Maintenance
Difficulty 3/5 1-2 days Newbie friendliness 35/100
cuappdev/eatery-android#198 · 1 comment ·
-
cuappdev/eatery-android#192 · 1 assignee ·
All issues in cuappdev/eatery-android
Similar issues
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
inu-appcenter/memorIN-backend#288 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
frontend maui-pilot pilot-ask question
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
area/plugin
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
kestra-io/plugin-kestra#190 ·