Interesting. I don't understand why another thread could make the
classloader go bananas on loading AsyncTask though.
Do you have more detail on what the unrelated thread did ? What was the
unhandled exception ?
In my app I'm not using any add API but I have a lot of threads launched
early on,
Was faced with the same error when trying to launch an AsyncTask and found
that the reason it would fail was that an unrelated thread would throw
an unhanded exception early on. It seems the AsyncTask and the other thread
(used to fetch ad banners) shared resources and when the ad thread
More on this Exception. I triggered it accidently by quitting and
relaunching my app quickly and got the following logcat
Application.onCreate() is called
...
08-25 15:41:33.003: WARN/ActivityThread(16118): ClassLoader.loadClass: The
class loader returned by Thread.getContextClassLoader() may
On Aug 21, 3:02 am, TreKing treking...@gmail.com wrote:
On Sat, Aug 20, 2011 at 6:02 PM, b0b pujos.mich...@gmail.com wrote:
Does anyone have seen such crash reports in its own apps ?
I've gotten a few randoms that seem impossible like this. My current theory
is a bad install that f***s up
On Sun, Aug 21, 2011 at 2:14 AM, b0b pujos.mich...@gmail.com wrote:
I'm also starting to think it is due to a broken install of the app.
In any case not API level related since min API is 7.
It could be a pirated copy of your app, hacked to try running on an
old version of Android or on some
On Aug 21, 12:02 am, b0b pujos.mich...@gmail.com wrote:
I have an app on the Market that works well for most users but for a
few of them and very rarely, I get crash reports with exception:
java.lang.NoClassDefFoundError: android.os.AsyncTask
AsyncTask was introduced in api level 3. Any
On Sat, Aug 20, 2011 at 8:19 PM, Peter Sinnott psinn...@gmail.com wrote:
It would nice if the developer console error page had the Android version
and device in it.
Technically it does, but the information is presented so horribly it's
impossible to determine which app version was running on
I have 23 others , 2 nexus ones and 3 droids. There are I think half a
dozen Android phones called droid and that is an awful lot of phones
tagged other. From a practical point of view I wouldn't consider the
device to be reported. The error reporting was nice when it arrived
but after a couple of
On Sat, Aug 20, 2011 at 8:40 PM, Peter Sinnott psinn...@gmail.com wrote:
I have 23 others , 2 nexus ones and 3 droids. There are I think half
a dozen Android phones called droid and that is an awful lot of
phones tagged other. From a practical point of view I wouldn't consider
the device to
9 matches
Mail list logo
