Overview
An iOS/Apple Push Notification Certificate is necessary to send push notifications to attendees via your app. This article outlines this push notes certificate rebuilding procedure without accessing the Apple Developer Account.
Diagnosis
You will have faced an error message while trying to send a push note via your app (eg "There was a problem sending out your push notification.") or you will have been notified that your certificate is due to expire (or has already expired) and therefore you will need to rebuild it.
Often this certificate may be faulty or it may have expired and thus it is useful to rebuild it.
Prerequisites
- A published iOS application.
- Reseller Account
Solution
- Log in to the BiznessApps portal and go to My Apps.
- Go to the app that has the issue. At the bottom right, click the three dots icon to reveal an action menu.
- Click More > Push Publish.
- You will now see the Push Publish window appear at the right. Fill in the following information for your request to go through:
- Input your email in the Email Address field as this field is required.
- A confirmation of the cert rebuild was delivered on the legacy system, but it will be removed on future releases.
- Provide the Apple Username and Apple Password for the account the app is hosted in, or in case you have been added as an Admin for Company/Organization accounts, you can use those credentials instead.
- Provide the Apple Developer Name associated with the Developer account where the app is published.
- Verify that the Bundle ID is correct (see the next step for instructions).
- Input your email in the Email Address field as this field is required.
- To verify the Bundle ID, log in to the App Store Connect and click My Apps from the main menu.
- Select the app that has push notification issues and select the tab that says App Information.
- Copy this Bundle ID and paste it into the Bundle ID field back in the BiznessApps dashboard.
- Once you have confirmed your Bundle ID and all other info, click Log In.
- This adds a field to the screen asking for the verification code if your account has two-factor authentication enabled.
- If it does not, go to Step 10.
- Once you have received the code on your device, write it down on that field and click on Submit code.
TIP: A workaround to avoid having your customers on the phone while renewing push services certificates, is adding your phone number as a trusted resource to the account. Have a look at the Add a Trusted Phone Number 2FA for an Apple ID KB article for more information. - If your account has been added to multiple teams, you will have to select the team name where the app was published. Otherwise, you will only see one team there:
<supportagent>
Customers who are Single App Users do not have access to the dashboard, and hence you will have to perform these actions for them. Moreover, you will have to arrange a phone call/remote session with the customer and perform the steps so that they can share details of the Apple developer account and share the 2FA code in order to renew the certificate.
- Inform the customer that since they have an individual app account, you will need to arrange a session with them and perform these steps.
- Login to the Super Admin Dashboard, and find the customer's app using the App Code that they have shared with you. If they have not shared one, you will have to request it.
- Once you have found the App using the App Code, click on the three dots to the right of the App, then click on More and then Push Publish
- You can then follow steps 4-10 from the public-facing section of this article. For reference, the following Push Publish Window will appear on the right:
- Ask the customer to test whether push notifications are working after all the steps have been completed.
</supportagent>
Testing
The push notification certificates are re-generated instantly, and a success message appears in the Dashboard. The following message displays on the top of the interface:
Push certificate generated!
You or your client can log in to the app and send iOS push notifications without receiving the error message.
Comments
0 comments
Please sign in to leave a comment.