There apparently is an implementation of that class in your local client .apk. It is very clear from the logs that the client is trying to interact with -some- component in its package, as you can see right in the component name.
On Thu, Feb 12, 2009 at 2:37 PM, Hans <hkess...@gmail.com> wrote: > > On Feb 12, 5:09 pm, Dianne Hackborn <hack...@android.com> wrote: > > I replied to this in the other thread, but if you want to explicitly > > reference a component from one package that is in another, you need to > > explicitly build the ComponentName of both the package and class name of > the > > target. The shorthand new Intent(this, ...) creates ComponentName > objects > > whose package is your own -- it is only for references components in your > > own package. > > Then how was it starting the service, binding it, and calling methods > on the service's interface if the constructor for Intent was somehow > mangling TestService.class? > > TestService.class resolves directly to > com.android.TestService.TestService anyhow. > > Hans > > > > -- Dianne Hackborn Android framework engineer hack...@android.com Note: please don't send private questions to me, as I don't have time to provide private support. All such questions should be posted on public forums, where I and others can see and answer them. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
