Pressing ✓ causes damage to the application - EliFUT 1.0.6

in #utopian-io6 years ago (edited)

Project Information

Repositories:
Github : https://github.com/EliFUT/android
Project name: EliFUT Android
Publisher: Felipe five

expected behavior

As I leave the league and hit, this app is still running well. so users can choose the country and see other leagues.

Real behavior

When I turn off internet data and leave the league, then I hit suddenly the application is broken.

How to reproduce

  • Download the app in the play store.
  • Run the app.
  • Select a country and press Ok.
  • Wait until the loading process is complete.
  • Then turn off internet data.
  • Press point 3 in the top right corner.
  • Select abandon league
  • Now click in the bottom right corner.
  • Bugs are visible, app is corrupted.
DEVICESANDROID VERSION
Xiomi Redmi Note 5ANougat, 7.12 N2G47H (RAM: 2 GB)
  • Browser: EliFUT v1.0.6

Recording Of The Bug

Proof of Work Done

Github account

Problem already reported here

Log Cat

05-28 00:59:20.859  9452  9452 E AndroidRuntime: FATAL EXCEPTION: main
05-28 00:59:20.859  9452  9452 E AndroidRuntime: Process: com.elifut, PID: 9452
05-28 00:59:20.859  9452  9452 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.elifut/com.elifut.activity.MatchProgressActivity}: java.lang.NullPointerException: Attempt to invoke virtual method 'com.elifut.models.MatchResult com.elifut.models.Match.result()' on a null object reference
05-28 00:59:20.859  9452  9452 E AndroidRuntime:    at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2449)
05-28 00:59:20.859  9452  9452 E AndroidRuntime:    at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2509)
05-28 00:59:20.859  9452  9452 E AndroidRuntime:    at android.app.ActivityThread.access$1000(ActivityThread.java:153)
05-28 00:59:20.859  9452  9452 E AndroidRuntime:    at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1373)
05-28 00:59:20.859  9452  9452 E AndroidRuntime:    at android.os.Handler.dispatchMessage(Handler.java:102)
05-28 00:59:20.859  9452  9452 E AndroidRuntime:    at android.os.Looper.loop(Looper.java:154)
05-28 00:59:20.859  9452  9452 E AndroidRuntime:    at android.app.ActivityThread.main(ActivityThread.java:5527)
05-28 00:59:20.859  9452  9452 E AndroidRuntime:    at java.lang.reflect.Method.invoke(Native Method)
05-28 00:59:20.859  9452  9452 E AndroidRuntime:    at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:739)
05-28 00:59:20.859  9452  9452 E AndroidRuntime:    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:629)
05-28 00:59:20.859  9452  9452 E AndroidRuntime: Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'com.elifut.models.MatchResult com.elifut.models.Match.result()' on a null object reference
05-28 00:59:20.859  9452  9452 E AndroidRuntime:    at com.elifut.activity.MatchProgressActivity.onCreate(MatchProgressActivity.java:156)
05-28 00:59:20.859  9452  9452 E AndroidRuntime:    at android.app.Activity.performCreate(Activity.java:6303)
05-28 00:59:20.859  9452  9452 E AndroidRuntime:    at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1108)
05-28 00:59:20.859  9452  9452 E AndroidRuntime:    at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2402)
05-28 00:59:20.859  9452  9452 E AndroidRuntime:    ... 9 more
05-28 00:59:20.861  9452  9452 E MQSEventManagerDelegate: failed to get MQSService.
Sort:  

Hi @syahrul-explorer

Thanks for your contribution.

I appreciate the fact that you opened the issue. Unfortunately, this post cannot be reviewed due to recent changes within the bug-hunting category.

We had some changes in the bug-hunting category you can read more about these changes using the link below:

https://steemit.com/utopian-io/@utopian-io/utopian-weekly-ai-arrives-on-utopian-io-bug-hunting-on-request-only-and-more-june-1st-2018

We have shifted the bug-hunting category to a TR (task-request) only category, this means that contributions to projects which are not in the whitelist will be not eligible for review, this change is effective following the announcement.

Your bug-report is on a project which is not whitelisted and we don't have proper consent to accept this contribution from you. You can keep up to date with the whitelisted project using the link below:

https://docs.google.com/spreadsheets/d/1S7ayFTEy5CBMyeJvFRgq5JUjlqZxFjWAWhhrBL0GC60/edit#gid=1954068373

Sorry for the inconvenience caused and look forward to your contributions in the future.