Though the user signs out, the HUAWEI ID is actually still in signed-in state on your app, because the user has authorized your app. Therefore, it's normal that your app does not require input of account information from the user when he/she signs in again. The user has to enter necessary information for signing in, if he/she has done either of the following:

Logged the HUAWEI ID out of the device. (How to log out: Go to Settings > Account center and tap LOG OUT.)
Canceled authorization to your app. (How to cancel: Go to Settings > Account center > Privacy center > Control account access, then select your app, and tap CANCEL AUTHORIZATION.)

My app appears in full-screen mode and it calls the sign-in API to bring up the sign-in screen, but the status bar at the top of the device screen flashes by. Why does this happen?

Full-screen adaptation is not made for a page in the Account SDK. To resolve this issue, do as follows:

Update the Account SDK to 6.1.0.302 or later.
Make sure that the sample code used for integrating the sign-in API is similar to the following:

Java

Collapse
Word wrap
Dark theme
Copy code
public void accountAuthSignIn() {
    AccountAuthParams authParams = new AccountAuthParamsHelper(AccountAuthParams.DEFAULT_AUTH_REQUEST_PARAM).setAuthorizationCode().createParams();
    AccountAuthService service = AccountAuthManager.getService(MainActivity.this, authParams);
    Intent intent = service.getSignInIntent();
    intent.putExtra(CommonConstant.RequestParams.IS_FULL_SCREEN, true);
    startActivityForResult(intent, 8899);
}

Obtaining Account Information

What are the maximum lengths of access token and refresh token?

The lengths of access token and refresh token are related to the information encoded in the tokens. Currently, each of the two tokens contains a maximum of 1024 characters.

Is there a limit on the frequency for calling the API for obtaining the access token?

This API can be called by an app up to 10,000 times within one hour. If the app exceeds the limit, it will fail to obtain the access token.

The email address is contained in the account information, but is not found in the response to the /oauth2/v3/tokeninfo API call from the Huawei Account Kit server. Why?

Description

After integrating Account Kit, I call the /oauth2/v3/tokeninfo API of the Account Kit server to obtain the ID token, but can't find the email address in the response body.

The response in this case is as follows:

Collapse
Word wrap
Dark theme
Copy code
{
    "at_hash": "XXXXXX",
    "aud": "XXXXXX",
    "sub": "XXXXXX",
    "azp": "XXXXXX",
    "kid": "XXXXXX",
    "iss": "https://accounts.huawei.com",
    "typ": "JWT",
    "exp": 1579682457,
    "display_name": "136******53",
    "iat": XXXXXX,
    "alg": "RS256"
}

The response in the API reference is as follows:

Collapse
Word wrap
Dark theme
Copy code
{
    "iss":"String",
    "sub":"String",
    "aud":"String",
    "exp":"Long",
    "iat":"Long",
    "nonce":"String",
    "at_hash":"String",
    "azp":"String",
    "email_verified":"Boolean",
    "email":"String",
    "picture":"String",
    "name":"String",
    "locale":"String",
    "family_name":"String",
    "given_name":"String",
    "display_name":"String"
}

Possible Causes

Before obtaining the ID token, the app does not request the HUAWEI ID user to authorize the app to obtain the email address.

Procedure

In the client-side code of your app, call the related API to request the HUAWEI ID user to authorize the app to obtain the email address.

The authorization request API in Account SDK 3.0 is requestEmail(), and that in Account SDK 4.0 is setEmail().

Account SDK 3.0

Collapse
Word wrap
Dark theme
Copy code
HuaweiIdSignInOptions mSignInOptions = new HuaweiIdSignInOptions.Builder(HuaweiIdSignInOptions.DEFAULT_SIGN_IN).requestServerAuthCode().requestIdToken("").requestEmail().build();

Account SDK 4.0

Collapse
Word wrap
Dark theme
Copy code
HuaweiIdAuthParams authParams = new HuaweiIdAuthParamsHelper(HuaweiIdAuthParams.DEFAULT_AUTH_REQUEST_PARAM).setIdToken().setEmail().createParams();

NOTE

For details about how to request a HUAWEI ID user to authorize an app to obtain the email address, please refer to setEmail in HuaweiIdAuthParamsHelper.

Is a private key required when jwt.io is used to verify an ID token?

No private key is required for verifying or parsing an ID token.

After the on-device ID token verification code in the sample code is executed, an error message "id Token validate failed.NoSuchMethodError" is displayed. Why?

The minimum Android version for the ID token-based integration demo is Android 9. Check whether the Android version on the test phone is the required version.

The account information has been obtained after a successful callback on the device. Then I called getEmail() to obtain the email address from the account information, but didn't find the email address. Why?

The email address is not mandatory. Sign in to the account center to check whether the user's account information contains the email address.

What is the update policy of the public key used to verify the validity of the ID token? When will the public key be updated? Will the old public key cached by me be unavailable after the update?

The public key used to verify the ID token is updated once a day and can be cached on your app server. If the public key is invalid, obtain the latest public key from certs and update the public key cached on the app server.

Can I obtain the UID after integrating Account Kit?

No. For privacy protection, you can obtain only the OpenID and UnionID.

What are the lengths of OpenID and UnionID?

OpenID: Currently, the OpenID returned by the Account Kit server does not have a fixed length, but the maximum length allowed is 256 characters. For future expansion considerations, reserve at least 768 (256 x 3) characters for the OpenID. Actually, you are advised not to set any length limit for the OpenID.

UnionID: Currently, the UnionID returned by the Account Kit server consists of 46 characters, and the maximum length allowed is 64 characters. For future expansion considerations, reserve at least 192 (64 x 3) characters for the UnionID. Actually, you are advised not to set any length limit for the UnionID.

NOTE

The difference between UnionID and OpenID lies in that if multiple apps are managed under the same developer ID, the OpenID varies depending on the apps, but the UnionID is the same for all the apps. If you need to share the user information of the same HUAWEI ID across different apps, use UnionID as the user ID.

How long will the access token and refresh token be valid?

The validity period of the access token is 1 hour, and that of the refresh token is 180 days.

Others

A user has installed the latest HMS Core (APK) on their phone running Android 11, but they were still asked to update the APK. How should I resolve this issue?

In Android 11, the way for an app to query other apps on the user device and interact with them has been changed. If targetSdkVersion is 30 or later for your app and the Account SDK integrated into your app is earlier than 6.1.0.300, your app will be unable to access HMS Core (APK) and continuously ask users to update the APK.

You can solve the issue using either of the following methods:

Method 1:
Update the Account SDK to 6.7.0.300. See Version Change History for detailed version information.

Method 2:
If the SDK is not updated, add a <queries> element in the manifest element in AndroidManifest.xml.
Collapse
Word wrap
Dark theme
Copy code
```
<manifest ...>
    ...
    <queries>
        <intent>
            <action android:name="com.huawei.hms.core.aidlservice" />
        </intent>
    </queries>
    ...
</manifest>
```
NOTE
The <queries> element requires the following:
- Your Android Studio version is 3.3 or later.
- Your Android Gradle plugin version is 3.3.3, 3.4.3, 3.5.4, 3.6.4, 4.0.1, 4.1.0, or later.

Result Codes

Success Stories

Send feedback

Was this page helpful?

Send feedback

Reach out to us through the community for any other questions.

Community Q&A Intelligent Assistant