This topic describes the usage limits of the product.
Application number limit
Each Alibaba Cloud account has a cumulative quota of 45 applications that can be created in the EMAS console. This total includes deleted applications.
If you reach the application limit, see the FAQ: The number of created applications has reached the limit.
SDK compatibility and version requirements
Android: Supports Android 4.1 and later.
iOS: Supports iOS 10 and later.
HarmonyOS: Support starts with the HarmonyOS NEXT version.
Usage outside China
Android: The push server is located in the Chinese mainland. Pushes to devices outside China may experience a delay of 100 ms to 300 ms. We recommend that you integrate the Google channel for auxiliary support.
iOS:
Notifications: Notifications are sent through the Apple Push Notification service (APNs) channel. Users both inside and outside China should receive them without any issues.
Messages: Messages are sent through a proprietary in-app channel. Because the servers are deployed in the Chinese mainland, users outside China may experience network restrictions.
HarmonyOS: Currently supported only in the Chinese mainland.
Account, tag, and alias limits
Account: An account must be 64 bytes or less. A device can be attached to only one account. An account can be attached to a maximum of 10,000 devices.
Alias: An alias must be 128 bytes or less. A device can be attached to a maximum of 128 aliases. An alias can be attached to a maximum of 128 devices.
Tag:
A tag name can be up to 128 characters long. A Chinese character is counted as a single character. Each application can have up to 10,000 tags. A device can be attached to an unlimited number of tags. A tag can be attached to an unlimited number of devices.
Do not attach more than 100,000 devices to a single tag. Pushing to a tag with this many devices can increase the processing time and slow the response. To prevent this, you can push to all devices instead. Alternatively, you can split the device collection into more granular tags and call the push API multiple times to push to each tag.
Push content limits
Android:
Android message: Title + Body <= 1800 B
Android notification: Title + Body + AndroidMusic + AndroidOpenType + AndroidActivity + AndroidOpenUrl + AndroidExtParameter <= 1800 B
The Title and Body fields cannot be empty.
iOS:
iOS message: Title + Body <= 1800 B
iOS notification: Body + iOSMusic + iOSBadge + iOSExtParameter <= 1800 B
A Chinese character counts as 3 bytes. The Title and Body fields cannot be empty.
HarmonyOS:
HarmonyOS message: Title + Body <= 1800 B
HarmonyOS notification: Title + Body + HarmonyRemindTitle + HarmonyRemindBody + HarmonyNotifyId + HarmonyActionType + HarmonyAction + HarmonyUri + HarmonyRenderStyle + HarmonyImageUrl + HarmonyInboxContent + HarmonyNotificationSlotType + HarmonyExtParameters <= 1800 B
The Title and Body fields cannot be empty.Third-party channel push limits
For more information, see the FAQ: Push limits for auxiliary channels on Android.
Other limits
When you push by account, alias, or device, the targetValue parameter can contain a maximum of 1,000 values separated by commas (,).
OpenAPI pushes include pushes to all devices and batch pushes to specific devices. For batch pushes, you can target by device, account, or alias. You can specify a maximum of 1,000 devices, accounts, or aliases per push.
For OpenAPI call frequency limits, see Quota Center.
Frequency limit for pushing to all devices: For the same AppKey and operating system (Android, iOS, or HarmonyOS), the interval between two pushes to all devices must be at least 1 second. In any 10-minute period, you can push a maximum of 10 notifications and 30 messages to all devices. Messages converted to notifications count as notifications.