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. :)
Related
I have developed a react-native app and deployed it into the play store. I have used react-native-exception-handler to catch exceptions. But, play store reports indicate many crashes.
Will the exceptions caught by react-native-exception-handler be shown as crashes If NO, then what might be the reasons for these crashes ?
To answer your question one by one:
Will the exceptions caught by react-native-exception-handler be shown as crashes?
No
If NO, then what might be the reasons for these crashes?
There can be many driving factor for crashes, better thing will be to do some more unit testing and have that application tested by some beta tester before shipping it to play-store again.
Now since you are new to stack-overflow i would suggest you take a tour.
I've recently published my very first app to Play Store. I asked a friend to download and test it and it crashed on his phone. However, I have an exact phone as him with the same version of Android, and when I tested it the app runs without error. So what do I need to know about a device to re-create the bug?
So I've just figured out that Google Play Console there is a feature called Pre-launch report which give you the log of the bugs from user's devices, it is under Release Management tab on the left of the web page.
If you are a developer then can not re-create bugs because you would test with best-cases of app.You should test with worst-case scenario.
I will recommend to use a professional Tester to test your application. He/She must find out the bugs.
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?
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.
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.