AccountManager.addAccount()

?

        public AccountManagerFuture<Bundle> addAccount(final String accountType,

            final String authTokenType, final String[] requiredFeatures,

            final Bundle addAccountOptions,

            final Activity activity, AccountManagerCallback<Bundle> callback, Handler handler) {

        ...

    }
  

?

?

在程序中創(chuàng)建指定類型的系統(tǒng)帳號，需要提供一個AccountManagerCallback類型的回調(diào)，后面會講到其作用。

本方法要求用戶添加指定類型的帳號。
此種帳號類型對應的authenticator將加載對應的UI來處理這個請求。
方法返回一個AccountManagerFuture對象，可解析出一個Bundle，包含以下信息：
- KEY_ACCOUNT_NAME: 創(chuàng)建的帳號的名稱
- KEY_ACCOUNT_TYPE: 帳號類型

本方法創(chuàng)建一個匿名AmsTask實例并啟動：

?

            return new AmsTask(activity, handler, callback) {

            public void doWork() throws RemoteException {

                mService.addAcount(mResponse, accountType, authTokenType,

                        requiredFeatures, activity != null, optionsIn);

            }

        }.start();
  

這里，以異步的方式請求AccountManagerService.addAccount()
start()方法立即返回，返回值是AccountManagerFuture類型的。

?

AccountManagerService.addAccount()

這個方法中，創(chuàng)建一個Session類型的匿名實例，并調(diào)用其bind()方法，最終捆綁到應用程序提供的authenticator service：

?

                new Session(accounts, response, accountType, expectActivityLaunch,

                    true /* stripAuthTokenFromResult */) {

                public void run() throws RemoteException {

                    mAuthenticator.addAccount(this, mAccountType, authTokenType, requiredFeatures,

                            options);

                }



                protected String toDebugString(long now) {

                    return super.toDebugString(now) + ", addAccount"

                            + ", accountType " + accountType

                            + ", requiredFeatures "

                            + (requiredFeatures != null

                              ? TextUtils.join(",", requiredFeatures)

                              : null);

                }

            }.bind();
  

這是Session.bind()方法的相關細節(jié)：

?

?

            void bind() {

            ...

            if (!bindToAuthenticator(mAccountType)) {

                Log.d(TAG, "bind attempt failed for " + toDebugString());

                onError(AccountManager.ERROR_CODE_REMOTE_EXCEPTION, "bind failure");

            }

        }


  

bindToAuthenticator()方法找到對應的組件名稱（應用程序中定義的相關service），并且對Service發(fā)起綁定：

?

?

            private boolean bindToAuthenticator(String authenticatorType) {

            final AccountAuthenticatorCache.ServiceInfo<AuthenticatorDescription> authenticatorInfo;

            authenticatorInfo = mAuthenticatorCache.getServiceInfo(

                    AuthenticatorDescription.newKey(authenticatorType), mAccounts.userId);

            ...



            Intent intent = new Intent();

            intent.setAction(AccountManager.ACTION_AUTHENTICATOR_INTENT);

            intent.setComponent(authenticatorInfo.componentName);

            ...



            if (!mContext.bindService(intent, this, Context.BIND_AUTO_CREATE, mAccounts.userId)) {

                ...

            }



            return true;

        }
  

Session類實現(xiàn)了ServiceConnection接口，因此，當成功綁定到對應的應用程序中的Service，其實現(xiàn)的onServiceConnected()方法將被調(diào)用：

?

?

            public void onServiceConnected(ComponentName name, IBinder service) {

            mAuthenticator = IAccountAuthenticator.Stub.asInterface(service);

            try {

                run();

            } catch (RemoteException e) {

                onError(AccountManager.ERROR_CODE_REMOTE_EXCEPTION,

                        "remote exception");

            }

        }
  

這里的service，即是AbstractAuthenticator抽象類提供的IBinder:

?

?

    public abstract class AbstractAccountAuthenticator {

    ...



    private class Transport extends IAccountAuthenticator.Stub {

        public void addAccount(IAccountAuthenticatorResponse response, String accountType,

                String authTokenType, String[] features, Bundle options)

                throws RemoteException {

            ...



            try {

                final Bundle result = AbstractAccountAuthenticator.this.addAccount(

                    new AccountAuthenticatorResponse(response),

                        accountType, authTokenType, features, options);

                ...

            }

            ...

        }

        ...

    }

    ...

    private Transport mTransport = new Transport();

    

    /**

     * @return the IBinder for the AccountAuthenticator

     */

    public final IBinder getIBinder() {

        return mTransport.asBinder();

    }

    ...

}
  

AbstractAccountAuthenticator的內(nèi)部類Transport是IAccountAuthenticator接口的一個實現(xiàn)。后者規(guī)定了Authenticator的一組行為。
以添加帳號的操作為例，作為接口實現(xiàn)的Transport的addAccount()方法調(diào)用了AbstractAccountAuthenticator類的addAccount()抽象方法，這個方法的具體實現(xiàn)，則由應用程序中定義的authenticator子類來完成。

這里涉及到IPC，應用程序是服務端，提供服務的實現(xiàn)，而AccountManagerService則是客戶端，負責通過代理對象發(fā)起調(diào)用。

?

Email的authenticator實現(xiàn)：

?

        class PopImapAuthenticator extends AbstractAccountAuthenticator {

        ...



        @Override

        public Bundle addAccount(AccountAuthenticatorResponse response, String accountType,

                String authTokenType, String[] requiredFeatures, Bundle options)

                throws NetworkErrorException {

            // There are two cases here:

            // 1) We are called with a username/password; this comes from the traditional email

            //    app UI; we simply create the account and return the proper bundle

            if (options != null && options.containsKey(OPTIONS_PASSWORD)

                    && options.containsKey(OPTIONS_USERNAME)) {

                final Account account = new Account(options.getString(OPTIONS_USERNAME),

                        AccountManagerTypes.TYPE_POP_IMAP);

                AccountManager.get(PopImapAuthenticatorService.this).addAccountExplicitly(

                            account, options.getString(OPTIONS_PASSWORD), null);



                ...



                Bundle b = new Bundle();

                b.putString(AccountManager.KEY_ACCOUNT_NAME, options.getString(OPTIONS_USERNAME));

                b.putString(AccountManager.KEY_ACCOUNT_TYPE, AccountManagerTypes.TYPE_POP_IMAP);

                return b;

            // 2) The other case is that we're creating a new account from an Account manager

            //    activity.  In this case, we add an intent that will be used to gather the

            //    account information...

            } else {

                Bundle b = new Bundle();

                Intent intent =

                    AccountSetupBasics.actionSetupPopImapIntent(PopImapAuthenticatorService.this);

                intent.putExtra(AccountManager.KEY_ACCOUNT_AUTHENTICATOR_RESPONSE, response);

                b.putParcelable(AccountManager.KEY_INTENT, intent);

                return b;

            }

        }
  

1) 如果是Email應用程序內(nèi)部添加新的電子郵件帳號，此時已經(jīng)取得了帳號的用戶名和密碼，那么直接創(chuàng)建對應的系統(tǒng)帳號，并調(diào)用AccountManager.addAccountExplicitly()將其添加到系統(tǒng)帳號數(shù)據(jù)庫中，并返回帳號名稱和類型。
2) 如果是從外部，比如系統(tǒng)設置中添加Email帳號，則創(chuàng)建指向Email應用中創(chuàng)建帳號對應的activity的Intent，并返回。這樣，AmsTask實例在完成時會通過Handler機制調(diào)用AddAccountSettings活動提交的一個回調(diào)：

?

?

       private AccountManagerCallback<Bundle> mCallback = new AccountManagerCallback<Bundle>() {

        public void run(AccountManagerFuture<Bundle> future) {

            boolean done = true;

            try {

                Bundle bundle = future.getResult();

                //bundle.keySet();

                Intent intent = (Intent) bundle.get(AccountManager.KEY_INTENT);

                if (intent != null) {

                    done = false;

                    Bundle addAccountOptions = new Bundle();

                    addAccountOptions.putParcelable(KEY_CALLER_IDENTITY, mPendingIntent);

                    addAccountOptions.putBoolean(EXTRA_HAS_MULTIPLE_USERS,

                            Utils.hasMultipleUsers(AddAccountSettings.this));

                    intent.putExtras(addAccountOptions);

                    startActivityForResult(intent, ADD_ACCOUNT_REQUEST);

            ...

    }
  

這樣就會啟動Email創(chuàng)建帳號的activity，之后又會走到1)中的步驟了。

?

?

基于Andoird 4.2.2的Account Manager源代碼分析學習：創(chuàng)建選定類型的系統(tǒng)帳號