Ahh yeah that makes total sense now. Can't believe I didn't notice
that
Thanks again
On Nov 11, 10:16 pm, Mark Murphy wrote:
> Lee Jarvis wrote:
> > Yeah, my bad..
>
>
>
> > 11-11 21:47:02.280: ERROR/AndroidRuntime(797): Caused by:
> > java.lang.RuntimeException: Can't create handler inside thr
Lee Jarvis wrote:
> Yeah, my bad..
> 11-11 21:47:02.280: ERROR/AndroidRuntime(797): Caused by:
> java.lang.RuntimeException: Can't create handler inside thread that
> has not called Looper.prepare()
General rule: always look for the "Caused by:" entry in the stack trace.
Your problem isn't the
Yeah, my bad..
11-11 21:47:01.811: INFO/InetAddress(797): Unknown host
thishostdoesntexist.net, throwing UnknownHostException
11-11 21:47:02.270: ERROR/AndroidRuntime(797): Uncaught handler:
thread AsyncTask #1 exiting due to uncaught exception
11-11 21:47:02.260: WARN/dalvikvm(797): threadid=15:
Lee Jarvis wrote:
> So I've been sifting through example after example of android code,
> and I see most web requests don't actually catch that many exceptions,
> maybe because their path is hard coded so there is no room for user
> error?
>
> I'm still confused as the best way to exit my backgrou
So I've been sifting through example after example of android code,
and I see most web requests don't actually catch that many exceptions,
maybe because their path is hard coded so there is no room for user
error?
I'm still confused as the best way to exit my background task
gracefully if my get()
5 matches
Mail list logo
