It appears it's because there is some caching going on where my authenticator service is getting launched, the bind fails to return an authenticator IBinder, and then binding is not tried again for future runs of the application. Even if I install a new authenticator, the OS never bothers to try it again unless I restart the OS.
Should I file a bug on this, since re-installing the authenticator should cause the service's onBind to call again, instead of using the cached one? On Nov 24, 12:43 pm, Micah <mi...@zoltu.net> wrote: > I have written a simple Authenticator service to work with the new > AccountManager API introduced in 2.0. When I launch a test app that > uses the authenticator the authenticator service is launched (as > expected) and it's onBind method is called. However, if I run my test > application a second time in the same emulator (without restarting the > emulator) my service is not launched and onBind is not called. > > So far the only way I have found to get my service to launch and > onBind to call again is to restart the emulator, which is a very time > consuming process. I have looked at the Devices view in Eclipse and > ensured that all of my processes have been killed, just in case one of > them was just being rebound to or something. -- 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
