# Custom IOS Certificates (App)

## I won't grant Let's Get Digital access to the Apple ID, how can I publish the app in the app store under my own account? <a href="#option-a-you-will-sign-the-application-yourself" id="option-a-you-will-sign-the-application-yourself"></a>

If we cannot be granted access to your Apple ID, there are two ways to publish the app in the App Store. Below you will find both options, including what we expect.

### **Additional costs of 500 euro**

Our pricing is low compared to custom app development because we have automated most parts of the app-creation and publishing process.\
\
When you choose one of the manual publishing options below, the automated workflow no longer applies. This requires additional work from our development team, which is why an extra service fee of **€500** is charged.

### Important Note

If you choose one of these options, we expect that you (or someone on your side) has the necessary technical knowledge to complete the required steps.\
\
We do **not** provide support for these parts of the process, as they fall outside our standard automated workflow.

## Option A: You will sign the application yourself <a href="#option-a-you-will-sign-the-application-yourself" id="option-a-you-will-sign-the-application-yourself"></a>

1. Generate a new application (In the correct language) in Itunes Connect and save the App & Bundle IDs (You can choose one yourself).
2. Generate a pem certificate for the specific Apple ID.
3. Sent the pem certificate and the BundleID to Let's Get Digital.
4. Provide us a safe way to send you the .xcarchive back to. (If not provided we use WeTransfer.com)
5. Let's Get Digital will send you a .xcarchive back + a zip file with screenshots of the app.
6. You will sign and publish the app yourself.
7. **Remember to re-enable Push Notifications while signing, otherwise sending out push messages will not work**

## Option B: Follow these steps where Let's Get Digital will sign the application <a href="#option-b-follow-these-steps-where-eventinsight-will-sign-the-application" id="option-b-follow-these-steps-where-eventinsight-will-sign-the-application"></a>

1. Generate a new application (In the correct language) in Itunes Connect and save the App & Bundle IDs (You can choose one yourself).
2. Generate a pem certificate for the specific Apple ID.
3. Generate a provisioning profile for the specific Apple ID.
4. Send the following details to the Let's Get Digital developers (Your Delivery Consultant will supply you with the e-mail address):
5. Give <distribution@letsgetdigital.com> developer **AND** app manager rights to publish and edit apps for the specific Apple ID.

| Type (File / String) | Name                            | Description                                                                                                                                                      |
| -------------------- | ------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| String               | App ID                          | The created application's App ID.                                                                                                                                |
| String               | Developer Team ID               | The Apple account's developer team ID which will be used to publish the application.                                                                             |
| String               | App Store Connect Team ID       | The App Store Connect Team ID which will be used to publish the application. (Please note that this is a numeric string).                                        |
| String               | Bundle ID                       | The Bundle ID of the application.                                                                                                                                |
| .p12                 | Distribution Certificate Export | A P12 export containing the certificate and private key to sign applications. If it's password protected, then the password should be sent in a separate e-mail. |
| .pem                 | Push certificate                | A Pem file to sent push messages. If it's password protected, then the password should be sent in a separate e-mail.                                             |
| .mobileprovision     | Provisioning profile            | A provisioning profile which matched the distribution certificate.                                                                                               |