Android/frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update AbstractAccountAuthenticator to call out the caveat in addAccount that requires synchronous execution.

Browse Source 
Bug: 175382142
Change-Id: I5c2032e91c47d8cd78e9d2c110737d8ad9ba2749
This commit is contained in:
Matt Pape
2020-12-14 17:49:03 +00:00
parent f010d5dea2
commit 8ebfc33d17
1 changed files with 3 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
core/java/android/accounts/AbstractAccountAuthenticator.java
View File

@@ -93,7 +93,8 @@ import java.util.Arrays;
* {@link AccountAuthenticatorResponse#onError} when it is complete.
* <li> If the authenticator cannot synchronously process the request and return a result then it
* may choose to return null and then use the AccountManagerResponse to send the result
* when it has completed the request.
* when it has completed the request. This asynchronous option is not available for the
* {@link #addAccount} method, which must complete synchronously.
* </ul>
* <p>
* The following descriptions of each of the abstract authenticator methods will not describe the
@@ -101,7 +102,7 @@ import java.util.Arrays;
* parameters and the expected result.
* <p>
* When writing an activity to satisfy these requests one must pass in the AccountManagerResponse
* and return the result via that response when the activity finishes (or whenever else the
* and return the result via that response when the activity finishes (or whenever else the
* activity author deems it is the correct time to respond).
*/
public abstract class AbstractAccountAuthenticator {