When using Offline Push Settings, the most common questions focus on naming rules, supported platforms, environment selection, and parameter preparation, covering 4 frequent issue types.
FAQ
What are the naming rules for an app identifier?
- An app identifier supports only letters, numbers, underscores, and periods.
- It must contain at least one segment, and multiple segments must be separated by periods.
- Each segment must start with a letter.
- The identifier cannot be duplicated.
Which platforms are supported by Offline Push Settings?
- It supports iOS push certificate configuration.
- It supports Android vendor push configuration, including Xiaomi, Huawei, Honor, VIVO, OPPO, Meizu, third-party push services, and FCM.
- It supports HarmonyOS push certificate configuration.
How should I choose the iOS push environment?
- Select the development environment for testing scenarios.
- Select the production environment when the app is in a formal release stage.
- Before saving, confirm that the selected environment matches the certificate and app stage.
Do Android push settings need to be configured separately for each vendor?
- Yes, start by selecting a specific vendor.
- Then enter the App ID, App Secret, package name, and other required parameters for that vendor.
- Parameter requirements may vary by vendor, so complete the fields shown on the page.
Glossary
| Term | Definition |
|---|---|
| App Identifier | The identifier used to distinguish a specific app, usually in a segmented naming format. |
| Bundle ID | The iOS app identifier field used to match the app with its push certificate settings. |
| channel ID | The Android notification channel identifier used to distinguish different notification channels. |
| VOIP Certificate | An optional iOS push certificate item used for voice-related notification scenarios. |