I have developed an android watch face.
Under the google play console there is a tab for CRASHES & ANRS.
From what I read in the documentation and in some SO questions these reports are automatically created when the app crashes.
But from my experience so far that does not happen for a wear application.
What do I need to do or am I missing something?
Currently, there's no way to do this. The Play Store team is aware of this request, but have not yet released support for it.
Related
We have had our app published to Play Store for a very long time. but recently we got this issue in Android 12.
Image showing Google Play Console
There are two types of APK in Play Console
Original File
Distribution APK
this problem is happening in the distribution app
I checked the logcat with adb but it's only showing WINDEATH and there is no other crash
I have checked all over Google and StackOverflow but there is no such question asked that I came across
After opening the app it's showing it like this
App Crash Screenshot
Also, we are using Firebase but there is nothing captured related to this
Use a crash reporting service such as Firebase
or Sentry.io.
These will help you log the crash, get some data about when it happened, why it happened etc. Flutter apps are not meant to crash, so check out your interactions with 3rd party plugins that are initiated on app start. Also, check your signing keys, maybe there is a mismatch between the debug ones and the production ones.
Good luck!
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.
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 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.
I have developed and put an android application in Google Play store.
Someone inform me that the app is crashing while doing something in application.
As a application developer,
How to find the problem and fix it in android?
Is there any tool or framework to debug the crashed app in android?
There are many sdks out there which can be incorporated in your app.
You can use
1. crashlytics
2. localytics
3. crittercism
Its always a best practice to include some analytics tools in your android application to know where users are spending a lot of their time. I personally like flurry Analytics.
Since you have already uploaded the apk you should check it out in the google play developer console. Even google will provide the crash data, and it is the only resource you have.
As far as fixing the application goes you can do it only by uploading a new apk and asking the users to update the app.
ACRA is a right choice for you to analyze the crash report. Please refer the following link to implement in your project.
https://github.com/ACRA/acra
And also, You can find the crash report in your developer console if the the user has sent the crash report while force closing of the application.
Please ensure that you have not enabled the proguard. if you have enabled proguard, try decode the lines using the following link
http://developer.android.com/tools/help/proguard.html#decoding