If you prefer not to grant Amego access to your Apple Developer account, you can still provide the necessary files so we can build and publish your app successfully.
Below are the files and steps required to ensure your iOS app can be signed, distributed, and send push notifications through OneSignal.
🧩 Files to Provide to Amego
Please provide the following files to [email protected] along with the password details so our team can build and publish your app:
1. App Provisioning Profile
Used to sign your main iOS app.
.mobileprovision
2. OneSignal (Push) Provisioning Profile
Used for the OneSignal Notification Service Extension.
.mobileprovision
3. Distribution Certificate
Used to sign and distribute your app.
.p12 file + password
4. Apple Push Notification Auth Key
Used by OneSignal to send push notifications.
.p8 file + Key ID + Team ID
⚠️ Important: Keep Your Current Bundle ID
When replacing an existing app:
- The Bundle ID (App ID) must remain identical to the current one in App Store Connect.
- Apple uses the Bundle ID to link your new build to the existing listing, ensuring:
- Users receive the update automatically.
- Ratings, reviews, and analytics remain intact.
Do not create a new Bundle ID for the main app.
🪜 Step-by-Step Instructions
1. Confirm Existing App ID
Identify your existing App ID (Bundle ID).
Example:
com.companyname.appnameThis will be used for the main app provisioning profile.
2. Create (or Confirm) App Group
If you don’t already have an App Group for push notifications, create one following this convention:
group.com.companyname.appname.onesignalAssociate this group with both:
- The existing main App ID (
com.companyname.appname) - The new OneSignal extension ID (
com.companyname.appname.OneSignalNotificationServiceExtension)
3. Verify or Create App Identifiers
(A) Main App
- Confirm your existing App ID (e.g.,
com.companyname.appname) already exists under Identifiers. - Ensure the following capabilities are enabled:
- App Groups → select
group.com.companyname.appname.onesignal - Associated Domains
- Push Notifications
- App Groups → select
(B) OneSignal Extension
If you don’t already have one, create a new App Identifier:
com.companyname.appname.OneSignalNotificationServiceExtensionThen enable:
- App Groups → select
group.com.companyname.appname.onesignal - Push Notifications
4. Create or Confirm App in App Store Connect
Your existing app listing should remain the same — do not create a new app record.
If needed, confirm:
- Platform: iOS
- Bundle ID: matches your existing one (
com.companyname.appname) - SKU: same as before (or unchanged if already set)
5. Create or Recreate Apple Distribution Certificate
If your certificate has expired or you need a fresh one:
- Go to https://developer.apple.com/account/resources/certificates/list
- Click +
- Select Apple Distribution
- Upload a Certificate Signing Request (CSR)
- Download the
.cerfile and export it as a.p12file in Keychain Access - Share the
.p12and password with Amego securely
6. Create or Recreate Provisioning Profiles
(A) App Provisioning Profile
- Go to https://developer.apple.com/account/resources/profiles
- Click + → App Store → select your existing App ID
- Select your Apple Distribution certificate
- Name the profile clearly, e.g.:
YourAppName_AppStore - Download the
.mobileprovisionfile
(B) OneSignal Provisioning Profile
- Repeat the steps above but select the OneSignal App ID:
com.companyname.appname.OneSignalNotificationServiceExtension - Select your Apple Distribution certificate
- Name the profile clearly, e.g.:
YourAppName_OneSignal_AppStore - Download the
.mobileprovisionfile
7. Generate or Confirm the Push Auth Key (.p8)
- Go to Certificates, Identifiers & Profiles → Keys → +
- Name it “Amego Push Key”
- Enable Apple Push Notifications service (APNs)
- Download the
.p8file (only available once) - Provide Amego:
.p8file- Key ID
- Team ID
📦 Send Files to Amego
Please provide all files securely to your Amego Customer Success contact:
YourAppName_AppStore.mobileprovisionYourAppName_OneSignal_AppStore.mobileprovisionAppleDistributionCertificate.p12+ passwordAuthKey.p8+ Key ID + Team ID
🔐 For security, please do not email these directly — use a secure file-sharing link (such as Box, Dropbox, or Google Drive).
