I know this is a *really* old thread now, but there is a credible issue
raised for it.
http://code.google.com/p/android/issues/detail?id=32470
So those that are experiencing it can go and star if you want to add your
weight to getting it noticed and fixed.
William
On Monday, October 3,
I have a manifest-registered receiver for WiFi events, which can get
triggered quite often (e.g. the signal level change).
Third party ROMs is one thing, causing plenty of weird shit for sure,
but this could be something else.
Will try to find the time to make a synthetic test case.
--
I just discovered today that the Samsung Galaxy S and/or the Nexus S are
among those devices listed as OTHER, while tracking a
NullPointerException in RingtonePickerActivity:
http://stackoverflow.com/questions/5874372/nullpointerexception-when-calling-ringtonepreference-on-samsung-galaxy-s
So
On Mon, Oct 3, 2011 at 4:38 AM, Kostya Vasilyev kmans...@gmail.com wrote:
It seems very unusual and wrong to list a device from a major manufacturer
that sold over 10 million units as, effectively, unknown, and doesn't help
at all with analyzing the crash reports.
The Market's bug reporting
Ok, thanks for sharing.
But... package installation is presumably handled by the core OS, and
not the Market itself (or so we are told). Pretty amazing.
03.10.2011 19:23, TreKing пишет:
Yup. I don't have receivers, but I see this from time to time with my
Activity classes, which are
Thank you for sharing this information, William.
I'm not hung up on this being exclusively a Market issue, in fact, my point
is, if it's a core platform bug, it's a very serious one, affecting large
numbers of users and developers alike, and I hope it gets fixed.
However, a quick search in the
I've seen this kind of installation corruption happen with a dev
deployment. So don't get hung up on it being a Market issue.
I second TreKing's suggestion to use an external bug reporter. I think
it's mandatory.
I initially used ACRA with results sent to a GoogleDoc spreadsheet,
but now use ACRA
I haev a few receivers, but I can't say I've ever seen one of those
ClassNotFound exceptions. That said, I've seen plenty of weird sh*t,
some of them I suspect to be real problems with my app, some of them I
think are bugs in either the core platform or some 3rd party ROM. But
I will never find
HTTP post is only one of the send methods for ACRA.
You can configure to have the user email you a report. That doesn't
require internet permission but you aren't delivered a particularly
corralled output.
William
On Oct 4, 9:58 am, Zsolt Vasvari zvasv...@gmail.com wrote:
A 3rd party tool is
Once you have your app published for a while, you will see all kinds
of weird crash reports. I, for example, cannot duplicate 80% of the
crash reports I get. Of course, Google's refusal to actually share
any info about the device, such as device type, OS version, etc, makes
it extremely
10 matches
Mail list logo
