I am trying to understand Bug Reporting in Android
I successfully Captured the bug reports as mention in Android Docs from my Android device
But don't know how to understand these files, log messages and identify & fix bugs in my App
The documentation also did not go into much detail about it.
Can anyone tell how to understand, identify & fix bugs from Bug Reporting UnZipped Documents or
link any useful Documentation that states the main files in Documents
Related
An app I published in Google Play got flagged by Google as being in breach of their malicious behavior policy. Specifically they stated that: “Your app contains the following dynamic code downloading: https://redirector.gvt1.com/edgedl/android/appdatasearch/libAppDataSearchExt_armeabi_v7a.v7.so”
I was completely unaware of this behavior and would like to remedy the situation. However, even after a few days researching this subject online, I still have no idea how to locate the root cause and fix it.
The google play support team can’t or won’t give any more information/guidance other than the statement above.
I suspect this behavior could stem from one of the external libraries used in the project (since I don’t perform this action directly in my code), but have yet to find the way to check this hypothesis
Does anyone have any advice on how to proceed?
Any diagnosis tools that monitor this sort of behavior by an app?
Thank You,
I'm building a game in Unity for iOS and Android, and we're working with an external QA team to test the game. One recurring issue on Android is that a tester will report a crash, and provide an ADB log of the issue, but the log itself contains very little useful data. Sometimes, the only log output corresponding to the crash will be something like "Process x.y.z has died."
So, I started looking into Android Developer documentation and searching around online for the most effective ways to investigate Android crashes. It seems like I should be able to find a crash dump somewhere, or do some instrumentation to provide more helpful information about the crash. I'm basically trying to find clues as to why a crash occurred. But I'm surprisingly finding no documentation or tutorials on the subject!
Can anyone point me in the right direction on this? Is there a documentation page I've missed, or a detailed tutorial on the subject? Is there some file beyond the ADB logs I should request from the tester? Am I lacking some vital app instrumentation that would report crash information in an online dashboard?
bugreport command creates a report that contains device logs, stack traces, and other diagnostic information to help you find and fix bugs in your app. You can capture a bug report from your device using
$ adb bugreport
You can find more information about this command at Capture and Read Bug Reports
This is an information question rather than a technical question. I have an app in Google Market. I need to know stracktrace of errors happens in other phones.
I have investigated but I have not seen anything about it. Does anyone know if Google offers some service to look at the errors that your application is giving in the market and thus to be able to reproduce it?
Thanks in advance!
Well google offers one really powerful tool "Firebase" it provides great analytics and crash reporting. In addition to analytics and crashes it provides others utilities like Cloud-Testing, Push Notifications and many others.
Other popular solution is Crashlytics offered by twitter.
Open your app at the developer console and select "disruptions and ANR". Here you can select on of disruptions you have, then you can see error stack trace!
Or you can use appmetrica from yandex. Link to yandex.metrica It's very simple to integrate yandex.metrica to your app and get all data about crashes and statistic (country, city, android version and so on).
Link to console
I want you to know I'm a newbie to Android Development.
I have developed an Android application (not uploaded on Google Play Store) with Crashlytics implemented.
This app is used by 50-60 users per day. Before releasing the app I tested it many times on my device and several others to check if it crashes or not. The app passed all the tests.
Now the app is crashing on some of the user's device and I can see the reason why it is crashing in Crashlytics dashboard.
But the app is crashing on specific devices only and working fine on other user's device and even after reproducing the issue on my device the app does not crash so I'm a bit confused about how to tackle problems like this.
And I can not purchase a device just for the purpose of testing.
So my questions are,
How can I solve the bugs in my app which are not reproducible on my devices?
Is it possible to know the exact reason why the app crashed using other bug reporting tools so that I can reproduce the bug on my device.
Any help is appreciated
Thank You :)
Try ACRA. You can implement sending crash reports to your email which will have model of the phone, android version, and stack trace of the crash.
There is a very high chance that many bugs and performance issue might get missed out during testing. Using production level SDKs like Finotes or Crashlytics to capture bugs with a detailed report which makes it easy to do the root cause analysis.
Crashlytics captures only crashes, Finotes captures many other types of bugs as well. Both SDKs are so lightweight and don't affect apps performance in production.
Somehow managed to fix bugs my app by using Mixpanel. Tracking an event was so much helpful.
Thanks Guys. :)
I have developed a free Android app and placed in on the market. I have fully tested the app on one device (LG Ally) and tested it with the whole range of emulators. I am getting reports of crashes on some 2.2 devices. The people reporting the crashes are not being at all helpful. I am looking for some expert help here.
The application and a description of the problems can be found at:
BASIC! v00.03
If having access to the source would help, send me an email.
Any help that could be provided would be greatly appreciated.
Have any of your users submitted an error report? Usually that will include a stack trace of some sort to give you an idea of what is causing the error.