ea693d5c66
- 实现了华为 HMS 推送服务集成 - 实现了小米推送服务集成 - 实现了 OPPO 推送服务集成 - 实现了 vivo 推送服务集成 - 实现了荣耀推送服务集成 - 实现了 FCM 推送服务集成 - 添加了统一的厂商推送接口和检测机制 - 添加了推送配置 API 和存储管理 - 添加了推送令牌管理和设备注册功能 - 添加了模拟器环境的推送测试用例
21 行
1.1 KiB
Markdown
21 行
1.1 KiB
Markdown
Vendor push SDK binaries can live here when a vendor only provides a console
|
|
download.
|
|
|
|
The Xuqm push SDK owns the vendor dependency graph. Huawei, Honor, Xiaomi,
|
|
OPPO, and vivo dependencies are declared by `sdk-push/build.gradle.kts`, so app
|
|
integrators do not need to add vendor SDKs themselves.
|
|
|
|
If a vendor SDK must be pinned to an official console-only binary for a tenant,
|
|
put the vendor `*.aar` or `*.jar` here before publishing the Xuqm push SDK.
|
|
Those binaries are picked up by `api(fileTree(...))`.
|
|
|
|
Xiaomi's official current AAR download page requires a Xiaomi Push console login
|
|
session. If an app must use that exact official package, download it from the
|
|
tenant's Xiaomi console and publish this SDK with the AAR in this directory.
|
|
|
|
`sdk-push` owns the Android manifest integration: permissions, push services,
|
|
notification click activity, vendor receivers and metadata placeholders are
|
|
declared in `src/main/AndroidManifest.xml`. Host apps should integrate the Xuqm
|
|
push SDK; vendor credentials are loaded from the tenant platform when the vendor
|
|
SDK supports runtime configuration.
|
