Why do I have "native crash" issues on my app? - android

Background
I have a simple app-manager app, which doesn't have any native code in it.
The problem
In the recent few weeks, I got crash reports from users via the developer console, seeing various "native crash" logs:
Some of those devices seem to be on quite a new Android version (7.0, for example), so I thought this shouldn't occur.
I don't even use so many libraries. Most are of Google itself.
What I tried
There are similar questions on Google's website being reported, but they don't have an answer.
The question
Why do those crashes occur?
Is there anything I can do about it?

Related

Android app displays a high "User-perceived crash rate" in Play Console, but not many actual crashes

I've got a gamified app for iOS and Android that we've developed in Unity, engine version 2020.3.27f1. After an update a few weeks ago, we saw our our numbers for the Android version's "User-perceived crash rate" start skyrocketing in the Google Play Console. Strangely, our numbers for actual reported crashes don't seem to have been affected at all.
The most likely culprit would be the upgraded Unity IAP package. In the first update (red circle on the graphs below), we upgraded from package version 4.5.0 to 4.5.1. In a later update (blue circle) we upgraded to 4.5.2 hoping it would alleviate the issue. In fact it seems to have made it worse.
User-perceived crash rate graph
Actual crashes graph
We have received no reports at all through any of our review or support channels that users are having issues with frequent crashing. We have a system for reporting users' error logs to us automatically when something goes wrong on their app, and the logs show nothing that suggests a new or very frequent issue. (Though it's always possible for the app to crash before being able to send off the log data.) Based on all available evidence, this seems to be an error on the Play Console's part.
Anyway, the obvious next step is to roll back the Unity IAP package version to 4.5.0. Thankfully we should be able to do that easily enough.
But I'm asking this question because I am at a loss for why this might happen like this, and what I could even do to start diagnosing this issue. Any thoughts or advice are appreciated.

log stacktrace from another user with error: Unfortunately, Application has stopped

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

Fixing bugs in Android App

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. :)

App crash when opened by clicking on icon, but not through Play Store

I just received reports from some of my users who's running Lollipop, they're saying that my app would crash (with the message: App Stop Working) if they tried to launch it by clicking on my app's icon on their home screen. But if they launch my app from Google Play Store, the app would work without any problem.
What could be the cause of this? If it's any help, here's my app https://play.google.com/store/apps/details?id=com.imincode.meniti
Btw there's no mention of any Crashes/ANR in my Google Play Developer Console.
The issue is you need to get the stack trace. Google Developer console is not sufficient in tracking bugs in your app. It misses the vast majority of in app crashes. I think there are a few options here.
1) I would try replicating this with the emulator and see if you can get the stack trace there.
2) I would embed a high quality crash tracking library in your application to be able to better handle this in the future. Currently I would recommend using Crashlytics. In my opinion they have the best crash reporting library on the market today. ACRA was very good several years ago before professional products came out, but does not hold up compared to modern trackers like Crashlytics.

Android Developer Console Stacktrace

I have an App available in the Android Market.
From time to time i get error reports in the Developer Console. For about 6 month there have been no more stack-traces visible. At first I though no more post-froyo bugs: 'yay'!
Recently I did some testing using a droid 2 which I am sure is not pre-froyo, I ran into an error, reported it, and never received this report in the Console.
Did I miss some configuration or option that enables me to receive stacktraces?
Is there something I can do about it?
I have no idea why you don't receive stack traces anymore nor how could you enable them. I have always felt Android Market is a somewhat unreliable service: reports are not accurate, downloads/active counts randomly change at times, crash reports not received, and so on.
However, I have suggestions how to implement similar functionality yourself and with a more reliable fashion: How do I obtain crash-data from my Android application?
Basically there are two options:
Use an existing component (like acra)
DIY by catching all uncaught exceptions.
(So you would have an option should you fail to receive a real solution)
I'd suggest you to stop listening to android market and work with other tools.
You should consider using a crash report tool like http://www.bugsense.com/ which is simple effective and meaningful
NOTE: i am not linked nor affiliated in any way with bugsense owners. I am just a simple user.

Categories

Resources