My understanding is that "almost" all calls are made on the main dispatch thread, including the onCreate call. The only exceptions are calls from specialized threads like the OpenGL drawing thread.
This means calls are always sequential, and in particular onCreate and onProgressChanged will be called sequentially from the dispatch thread. Is it possible that "target" gets reset to null at some other point in your code? On Nov 20, 7:53 pm, jotobjects <jotobje...@gmail.com> wrote: > On Nov 20, 5:30 am, Don <donal.morris...@gmail.com> wrote: > > > Anyway, i was able to tidy up the code and remove the bug. But still, > > there really should be no differences like this on various android > > devices (unless they are at diffenet firmware versions, of course). > > I don't know if you can count on onCreate completing before any other > code in the activity executes. Does the API guarantee that? > > Even minor differences in execution speed or linux multitasking on the > device could account for this kind of bug showing up on one device and > not on another. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
