App Crashes
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Start by reproducing the crash by opening a closed dining hall in the Android app. Trace the resulting failure to its source and verify that closed dining halls can be opened without crashing.
Written by the indexing model from the issue text.
Description
Whenever you click on a closed dining hall on android the app crashes.
- 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
-
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 ·
-
cuappdev/eatery-android#191 · 1 comment · 2 assignees ·
All issues in cuappdev/eatery-android
Similar issues
-
area-deployment area-integrations triage:bot-seen
Difficulty 2/5 Half a day Newbie friendliness 86/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
apache/flink-agents#1156 ·
-
[source-shopify] FAILED bulk operation without partialDataUrl is silently treated as successful Openarea/connectors autoteam community connectors/source/shopify needs-triage team/use type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100