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.
Related
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
I have some androids phones that have recently started crashing. Is there a way to help narrow down this crash information I retrieved from the Google Play Console?
Thanks for any direction!
enter image description here
If you have access to the devices/users, a device crash report would help to troubleshoot the issue further:
$ adb bugreport E:\Reports\MyBugReports
From the stack trace you provided, it looks similar to the issue described here, caused by a third-party library. In your case, it can be either your code or any third-party library which can cause the crash. I would recommend trying to identify which code created Spannable in your app and isolate/remove/replace it.
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. :)
[![enter image description here][1]][1]We have posted one app for Hong Kong Market and when users try to download the app it always gives an error named as "Package file is invalid". So for testing we did enable the app for India but here we are getting the same error. Please help us out
Reply from google support
Thank you for your patience while we've investigated this issue.
It appears that installations are failing due to your app's
incompatibility with some devices that are running Gingerbread or
Froyo. This issue has been discussed at length in multiple developer
forums. To find out how to make your app work better with older
devices with smaller buffers, please check developer discussions by
searching 'dexopt failed gingerbread froyo' on forums listed at
http://developer.android.com/support.html. Here you can find links to
developer support forums and IRC chat communities where developers
help each other solve development-related issues.
Unfortunately our team does not have the capacity to offer development
advice on per-app basis. However, if you find that installs are still
failing on Gingerbread or Froyo after implementing the changes we
mentioned, please let us know, and we'll investigate further.
Thank you for your understanding. If you have any further questions,
please let us know.
Send one more reply on same but not get anything right now
Question :
I am still getting an error after downloading the application from play store. I have also checked with manifest file here is my SDK setting.
android:minSdkVersion="11"
android:targetSdkVersion="18"
It's downloaded successfully from there but at the time of installing the app we getting again the same error " Package file is invalid ".
This is happened first time but when I try second time to install on same device at that time we are getting different error "Unknown error code during application install -24".
I am developing android application for client. Now client testing my application in various device. While testing, my application is crash at times. Now I need to know when and where the application crash.
How can I get the crash report from the device? Since my client does not have sdk and eclipse to view logcat error report.
There are mechanisms like ACRA that will let you obtain the crash reports from Android apps.
Instabug is a bug & crash reporting service and it’s just what you’re looking for.
It automatically sends a report containing all crash and device details once a crash occurs, plus it only takes a line of code to integrate in your app.
For full disclosure, I work at Instabug. Let me know if I can help.
By adding the Crash Report SDK in the project, You can view the released application crash log, which will help to locate problems.
Here is a demo page