When using Offline Push Settings, common questions usually focus on naming rules, supported platforms, environment selection, and vendor-specific configuration differences. This section covers 4 frequent questions.
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.
- Multiple segments must be separated by periods.
- Each segment must start with a letter.
- The same identifier cannot be created twice.
Which platforms are supported for offline push?
- iOS push certificate configuration is supported.
- Android multi-vendor push configuration is supported, including the vendors listed on the page and FCM.
- HarmonyOS push configuration is supported.
How should I choose the iOS push environment?
- Select the development environment during testing.
- Before release, confirm whether you need to switch to the production environment.
- Before saving, verify that the certificate and environment match.
Do I need to configure Android push separately for each vendor?
- Yes. Select the specific vendor first.
- Enter the required parameters for that vendor.
- Different vendors may require additional information shown on the page.
Glossary
| Term | Definition |
|---|---|
| App Identifier | The identifier used to distinguish a specific app and the base object for push configuration. |
| Bundle ID | The identifier of an iOS app, used to match the app with its push certificate. |
| App Secret | A common authentication parameter in Android vendor push configuration, used to verify app identity. |
| channel ID | The Android notification channel identifier used for important message delivery channels. |