Live Streaming SDK/Short Video SDK/Player SDK/Beauty Effects SDK license FAQ-Apsara Video SDK(Apsara Video SDK)-阿里云帮助中心

This topic answers frequently asked questions about applying for, renewing, using, and modifying the application information bound to your license.

Web Player SDK license errors

Problem: A license error occurs when you use the web Player SDK.

Solution: You must integrate the license service if you use web Player SDK v2.28.0 or later. Newly purchased licenses are not compatible with earlier versions of the web Player SDK. For optimal performance, use version 2.29.1 or later. If you have not purchased a web Player SDK license, purchase a new license on the ApsaraVideo MediaBox SDK buy page. After purchase, you must re-bind the license.

Mobile Player SDK license errors

Problem: An error message like "License verify premium func:abr" may appear when using Player SDK for mobile v7.0.0 or later.

[7.0.0_43566760] [licenseManager] :license verify premium func: abr
[7.0.0_43566760] [licenseManager] :Premium LICENSE INFO NOT VALID!
[7.0.0_43566760] [ResolverManager] :httpdns get ip info timed out
[7.0.0_43566760] [analytics] :eventCode:5004, name: string:li_di * Can not found the business data *||* li_fri * success *|
[7.0.0_43566760] [licenseManager] :license verify premium sdk result is 6, errMsg: Can not found the business data
[7.0.0_43566760] [licenseManager] :
                                    +---------------------------------------------------------------------------------------------------+
                                    |--------------------------------- Premium license is invalid!!! ----------------------------------|
                                    |--------------------- Please provide correct license key before play, --------------------------|
                                    | you can visit 'https://help.aliyun.com/zh/apsara-video-sdk/user-guide/license/' for more info.|
                                    +---------------------------------------------------------------------------------------------------+
[7.0.0_43566760] [] :check premium failed
[7.0.0_43566760] [] :check premium function: ABR
[7.0.0_43566760] [licenseManager] :license verify premium func: abr
[7.0.0_43566760] [licenseManager] :Premium LICENSE INFO NOT VALID!
[7.0.0_43566760] [analytics] :eventCode:5004, name: string:li_di * Can not found the business data *||* li_fri * success *|

Solution: In Player SDK for mobile v7.0.0 and later, features are divided into different editions. To use Professional Edition features such as advanced ABR policies, you must purchase and bind a Professional Edition license. For more information, see Obtain a Player SDK license.

License expiration and renewal

View the license expiration date

Log on to the ApsaraVideo VOD console or ApsaraVideo Live console.
In the left-side navigation pane, choose SDK Management > My Licenses.
Click the License Management tab, find the license order bound to your application, and check its expiration date in the Expiration Date column. To renew the license, click Renew in the Actions column.

Renew a license

For more information about renewing a license, see Renew a license.

Important

If the expiration date in the SMS notification you received differs from the date shown in the console, it is because the validity period was manually extended. The expiration date in the console prevails. You can ignore the expiration alerts on the Renewal page in Billing Management. We recommend that you disable the auto-renewal feature.
If you have a legacy license order that includes a bundle of multiple SDK features, you must renew the entire order. You cannot renew individual features separately. There are two ways to renew:
1. If the license order has an instance ID, click Renew in the Actions column.
2. If the license order does not have an instance ID, you cannot use the Renew button. You must purchase a new license on the ApsaraVideo MediaBox SDK buy page. After purchase, you must re-bind the license.

Troubleshoot license errors

If you encounter integration failures or other license errors, follow these steps to troubleshoot:

Verify that the license authorization is configured correctly in the ApsaraVideo VOD or ApsaraVideo Live console.
1. Log on to the ApsaraVideo VOD console or ApsaraVideo Live console.
2. In the left-side navigation pane, choose SDK Management > My Licenses.
3. Click the Application Management tab, find the target application, and click Details. The page displays basic information about the application and its bound license.
4. Check whether the following information is correct:
  - Basic application information: application identifier (such as the Package Name) and package signature. We recommend against binding a package signature.
  - Bound license information: SDK version, authorization type, expiration date, status, and value-added services.
Verify that the license configuration in your project is correct and matches the license information in the console.
- Web: Check the license field configuration used during player initialization.
  - domain: Ensure the domain of your player's page matches or is a subdomain of the domain specified when you applied for the license.
  - key: Ensure the License Key value matches the value displayed in the console.
- Android: Check the AndroidManifest.xml configuration.
  - License key: Ensure the value of com.aliyun.alivc_license.licensekey matches the key displayed in the console.
  - license file: Ensure the value of com.aliyun.alivc_license.licensefile matches the storage path of your license file.
  - Package ID: Ensure the applicationId in build.gradle matches the Package Name in the console.
  - package signature: If you bound a signature when you created the license in the console, ensure the signature configured in your project matches the one in the console. You can run the following command to query your package signature: keytool -v -list -keystore your.keystore.
- iOS: Check the Info.plist configuration.
  - BundleId: Ensure the value of CFBundleIdentifier matches the Bundle ID configured in the console.
  - License key: Ensure the value of AlivcLicenseKey matches the key displayed in the console.
  - license file: Ensure the value of AlivcLicenseFile matches the path of the license file within your ipa package.
- HarmonyOS: Check the module.json5 configuration.
  - BundleId: Ensure the bundleName in app.json5 matches the HarmonyOS BundleID configured in the console.
  - License key: Ensure the value of com.aliyun.alivc_license.licensekey matches the key displayed in the console.
  - license file: Ensure the value of com.aliyun.alivc_license.licensefile matches the path of the license file within your hap package.

Apply for a complimentary SDK license

If your cumulative spending or purchases of specified subscription packages within the last 31 days (from T-30 to T) meet certain thresholds, you may be eligible for a complimentary license. You must bind the license before your existing license expires. To apply for a complimentary Player SDK, visit Player SDK Complimentary Purchase Application. For other features, you can submit the Yida form to apply.

Important

T: The current date (inclusive).
T-30: 30 days before the current date (inclusive).
The statistical period is a rolling 31-day window.

Module	Edition	Applicable products	Complimentary criteria
Player SDK	Standard Edition/Professional Edition Does not include any value-added features	ApsaraVideo Live ApsaraVideo VOD Intelligent Media Management	For more information, see Obtain a Player SDK license
Live Streaming SDK	Standard Edition/Interactive Edition	ApsaraVideo Live	Complimentary. Place an order on the ApsaraVideo MediaBox SDK buy page
Short Video SDK	Basic Edition	ApsaraVideo VOD Intelligent Media Management	Any resource plan order ≥ CNY 1,800
Short Video SDK	Standard Edition	ApsaraVideo VOD Intelligent Media Management	Any resource plan order ≥ CNY 30,000
Beauty Effects SDK	Basic Edition	ApsaraVideo Live ApsaraVideo VOD	Any resource plan order ≥ CNY 99

Updating the license file and key

License file: We recommend updating the license file. After renewal, the expiration date in the license file is updated. Using the updated file improves the authentication success rate. For published apps, using a historical license file typically does not affect functionality.
License key: This key remains unchanged, as it is uniquely tied to your UID.

Modifying the application ID

If your application information changes, you can modify it in the console.

Important

Modifying an application's identifier, such as its package name, will invalidate the original identifier. You must download the license file again and replace the existing one. Proceed with caution.

Log in to the ApsaraVideo VOD console or the ApsaraVideo Live console.
In the left-side navigation pane, choose SDK Management > My Licenses.
Click the Application Management tab, find the target application, and click Edit
.
You can modify the application name, platform, the MD5 value of the Android application signature, and application identifiers, such as the package name.
After you confirm the changes, click Modify to complete the license modification.

Modifying the Android MD5 signature

Modifying the MD5 signature can cause production issues, so proceed with caution. Apps that use the ApsaraVideo MediaBox SDK require a license file and key for configuration. If you change authorization settings, such as the MD5 signature, the SDK in a released app version might fail authentication, causing features to become unavailable. Common scenarios include:

If you change the MD5 signature of an Android app from A to B, the app version configured with signature A will fail. In this case, we recommend creating a new application that uses the same package name but is configured with signature B for new app versions.
If you unbind the signature, older SDK versions will fail authentication. We do not recommend unbinding the signature if your app has ever used the following SDK versions:
- ApsaraVideo MediaBox SDK: v1.6.0 and earlier
- Player SDK: v5.5.1.0 and earlier
- Live Streaming SDK: v4.4.8 and earlier
- Short Video SDK: v3.35.0 and earlier

Modifying authorized modules, editions, or features

To add SDK modules or modify the edition or features of an existing module, submit a ticket.