Get your WeChat credentials
Obtain the WeChat configuration assigned to your application from NextAppMarket. Keep one record of the values and build identities agreed during onboarding, so your mobile and backend teams use the same application.
Understand the handoff
| Value | Where it belongs | Purpose |
|---|---|---|
| WeChat AppID | Mobile SDK configuration and backend | Identifies the WeChat application used for login. |
| WeChat AppSecret | Your authorized backend secret store | Authenticates the server-side code exchange. |
| Android application identity | Release configuration supplied to NextAppMarket | Connects the package and signing identity to the assigned WeChat app. |
| iOS application identity | Release configuration supplied to NextAppMarket | Connects the bundle and callback configuration to the assigned WeChat app. |
| iOS Universal Link configuration | iOS app and the associated domain setup | Provides the callback routing agreed for the application. |
NextAppMarket supplies the credentials. Your team supplies accurate application details and uses the assigned values in the build. The WeChat AppID is separate from your NextAppMarket application ID.
Confirm the build you will test
Send NextAppMarket the package or bundle identifier for the actual target. For Android, include the signing identity of the installed build; a locally signed debug APK and a distributed APK can differ. For iOS, confirm the associated domain and Universal Link used by the release.
A package rename, signing-key change, or callback-domain change can require a configuration update. Arrange the update before testing the new build and record which configuration belongs to each release.
Configure your backend
Use explicit configuration names such as WECHAT_APP_ID and WECHAT_APP_SECRET. Keep the AppSecret out of the mobile app, frontend bundle, and diagnostic screenshots. Restrict access to the component that performs the exchange.
The handoff method can vary by account. Use your NextAppMarket onboarding contact or the delivery channel provided for your application when a value is missing. Avoid creating a second provider application to work around an incomplete handoff.
Next: Android, iOS, or server-side authentication.