(BUG) (BirthdayBuddy version 1.1) App failed to open

in #utopian-io5 years ago

Project Information

Expected behavior

When I open the application, all feature should appear and the application should not be crashed.

Actual behavior

The application crashes when I open the application

How to reproduce

  • Download the application

  • open the application

  • Note the Error

  • Browser/App version: 1.1

  • Operating system: 6.0

Recording Of The Bug

20190701_100835

Logcat

D/AndroidRuntime(22963): Shutting down VM

E/AndroidRuntime(22963): FATAL EXCEPTION: main

E/AndroidRuntime(22963): Process: com.procrastimax.birthdaybuddy, PID: 22963

E/AndroidRuntime(22963): d.g: null cannot be cast to non-null type android.support.v7.widget.SearchView

E/AndroidRuntime(22963): at c.b.a.a.D.a()

E/AndroidRuntime(22963): at a.b.g.a.i.b()

E/AndroidRuntime(22963): at a.b.g.a.v.a()

E/AndroidRuntime(22963): at a.b.g.a.k.onCreatePanelMenu(:1)

E/AndroidRuntime(22963): at a.b.h.a.x$c.onCreatePanelMenu(:1)

E/AndroidRuntime(22963): at a.b.h.g.i.onCreatePanelMenu()

E/AndroidRuntime(22963): at a.b.h.a.C.run(:1)

E/AndroidRuntime(22963): at android.os.Handler.handleCallback(Handler.java:739)

E/AndroidRuntime(22963): at android.os.Handler.dispatchMessage(Handler.java:95)

E/AndroidRuntime(22963): at android.os.Looper.loop(Looper.java:135)

E/AndroidRuntime(22963): at android.app.ActivityThread.main(ActivityThread.java:5910)

E/AndroidRuntime(22963): at java.lang.reflect.Method.invoke(Native Method)

E/AndroidRuntime(22963): at java.lang.reflect.Method.invoke(Method.java:372)

E/AndroidRuntime(22963): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1405)

E/AndroidRuntime(22963): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1200)

Sort:  

Hi @friendsmobile, thanks for providing this report

I can see that the contribution has been acknowledged by the PO. He has self assigned the issue. Hopefully, a fix is in the works. I love that you included a logcat but these days we expect a bit of analysis to complement the stack trace. Some explanations on what could have possibly gone wrong

Still a good post. We look forward to more of your reports

Your contribution has been evaluated according to Utopian policies and guidelines, as well as a predefined set of questions pertaining to the category.

To view those questions and the relevant answers related to your post, click here.


Need help? Chat with us on Discord.

[utopian-moderator]

Thank you for your review, @fego! Keep up the good work!

Hi @friendsmobile!

Your post was upvoted by @steem-ua, new Steem dApp, using UserAuthority for algorithmic post curation!
Your post is eligible for our upvote, thanks to our collaboration with @utopian-io!
Feel free to join our @steem-ua Discord server

Hey, @friendsmobile!

Thanks for contributing on Utopian.
We’re already looking forward to your next contribution!

Get higher incentives and support Utopian.io!
Simply set @utopian.pay as a 5% (or higher) payout beneficiary on your contribution post (via SteemPlus or Steeditor).

Want to chat? Join us on Discord https://discord.gg/h52nFrV.

Vote for Utopian Witness!