4cf3252fb0
* Our AccountManager listener was getting unregistered due to the way ApplicationContext caches AccountManager in a static member * The result was that AccountManager registers its listeners against the FIRST context it is instantiated with! Future calls will all obtain this pre-initialized AccountManager. * In this case, AccountSetupOptions was the first caller (to create the AccountManager Account for Exchange) * The subsequent call to register a listener therefore had its registration tied to the context of AccountSetupOptions, and was therefore leaked when AccountSetupOptions finished! * This caused a chain of problems - the leaked receiver, an Exception in AccountManager when trying to ping the listener in an expired context, and eventually the bug referenced above, which became a P1 issue Change-Id: I478e28d21ca77419afa8011e4ed8101cdf67ab79 |
||
---|---|---|
assets | ||
docs | ||
images | ||
res | ||
src | ||
tests | ||
.classpath | ||
.project | ||
Android.mk | ||
AndroidManifest.xml | ||
MODULE_LICENSE_APACHE2 | ||
NOTICE |