Get your JPush credentials
Obtain the JPush configuration for your application from NextAppMarket. Use the same assigned application for the mobile SDK and your notification sender.
| Value | Where to configure it |
|---|---|
| AppKey | The Android/iOS SDK and the authorized server sender. |
| MasterSecret | Your backend secret store, when direct server sending is provisioned. |
| Android package and channel configuration | The mobile build and the configuration handoff to NextAppMarket. |
| iOS bundle and APNs configuration | The iOS build and the application configuration managed with NextAppMarket. |
Keep MasterSecret on your server. If you only received the client configuration, complete the server-sending handoff with NextAppMarket before following the direct REST example.
Supply the right application details
Give NextAppMarket the Android package name and/or iOS bundle ID you will distribute. Confirm the push channels needed by those builds and, for iOS, the APNs environment and associated credential configuration.
Treat a package change, bundle change, or APNs configuration change as an integration change. Coordinate it before releasing the new build, then repeat the single-device notification test.
Keep environments explicit
For iOS, the SDK's APNs setting and the sender's apns_production option must match the signed build and registered device token. Derive the SDK setting from your build configuration; a debug/release label alone is not a reliable substitute for the APNs entitlement.
JPush/APNs environment settings are independent of NextAppMarket Payments, whose current documented environment is production.
Record the handoff
Keep the AppKey, application identifiers, SDK versions, APNs environment, and enabled channel settings together in your team's integration record. Store the secret separately with restricted access. Use that record when comparing a working build with a failing one.
Reference: JPush server authentication.