IOS:
Once the certification is generated, you have to provision your app for push notifications either with a .p8 Auth key file OR .p12 certificate
Follow these steps to create new MobilePush apps (Repeat steps to create both a development and production app):
Log in to Marketing Cloud MobilePush.
Highlight the Mobile Studio menu and choose MobilePush from the dropdown.
On the top, select the Administration tab and click Create New App in the upper right corner.
Enter the name and description for the app.
Development app name suggestion: [App]_DEV-APNS.
Production app name suggestion: [App]_PROD-APNS.
Click Choose File and upload the icon for the MobilePush app.
Upload the previously created .p8 Auth Key File by clicking Choose File and choose the Auth Key on your computer to upload. This key will work for both Production and Development apps. To distinguish the difference for your app use the radio buttons described below as follows:
Development app: Select the Development APNs Environment radio button.
Production app: Select the Production APNs Environment radio button.
Validate the correct Auth Key File is uploaded. This should be a text file with a .p8 file extension. Not the signing certificate used to provision your application for AdHoc or App Store deployment.
Enter in the 10-character Key ID, this is usually the name of the .p8 text file after it is created or it can be viewed in your Apple Developer Account.
Enter in the 10-character Team ID associated with this Key. The team ID can be found in the Membership tab in your Apple Developer Account.
Enter in the Bundle Identifier of the app you are building.
Make any applicable changes to the optional settings.
Note and copy the Access Token, App ID and App Endpoint. These values will be used to configure the SDK for development testing.
Select your account name in the upper-right corner of the MobilePush Administration site and note and copy the “MID” value (numbers only).
Andriod
In the app switcher, hover over your name and click Setup.
Search for MobilePush.
To select the app to update, click the arrow by the app and select Settings.
You can update existing fields such as name, description, or the icon that represents your app.
For Google:
In the Android Client field, enter the server key from your Firebase console in the API Key field.
Enter or update optional settings.
After you populate the required fields for all applicable application platforms, click Save.
Review the information you provided and check for any potential errors.
Click Finish.
App Endpoint (Tenant-Specific Endpoint)
New implementations: Your app must use your app’s Marketing Cloud app endpoint value as part of the SDK configuration. Pass this value to setMarketingCloudServerUrl() in the MarketingCloudConfig.builder.
Upgrades: If you upgrade to the SDK version released with the April 2019 release or later, update your configuration to include the app endpoint value. App endpoint is required beginning with the April 2019 release. If your app isn’t configured with an app endpoint, the SDK returns an error from the configuration method, and the SDK does not function.
Access Token
Pass this value to setAccessToken() in the MarketingCloudConfig.builder.
App ID
Pass this value to setApplicationId() in the MarketingCloudConfig.builder.