App publishing methods

There are several ways to publish apps on Google Play and on the Apple App Store. Here are the options available to you that can be executed in both stores in partnership with InEvent:

What are the options I have regarding publishing my app?

These are the viable possibilities by the Global standard of the app stores and InEvent.

1. Direct publishing via InEvent with admin access.
2. File generation with or without certificates: files exportation.

Direct publishing via InEvent with admin access

You can provide InEvent with full admin access, by adding the email store@inevent.com and password default to both the company details page and to the app account store granting us admin access. You should follow this guide: Giving InEvent access to your app stores.

In this case, our team will be responsible for carrying out the app development and publishing processes, such as downloading certificates, file creation, and upload.

For the Google Play Store, you must send us the API Key. Click here to read a guide on how to create the API Key.

File generation with or without certificates: files exportation

This section is divided per platform.

Apple App Store

Sending closed binary file (IPA) with certificates

1. If it is not possible for InEvent to receive access to the store, you are required to send InEvent these 3 certificates:

• Provisioning Profile Certificate.
• Distribution certificate:
• Push certificate (p12)

1. Then, you will receive the IPA file developed based on the information registered in your InEvent Platform account so you can continue with the publishing.
2. InEvent will take up to 10 business days to generate the IPA file for your initial request. Any subsequent requests will also take up to 10 business days. Once the file is ready, you will receive it via email. You can also reach out to us via chat to request the file.

InEvent will not perform the development of store default images. You must develop all of them based on the sizes and formats authorized by the Apple Store. Access the link for more information.

Sending closed binary file (IPA) without certificates

If it is not possible to receive access to the store for publication of the APP and the necessary certificates, InEvent will develop the IPA file (binary in the format accepted by the Apple Store) based on information entered in your InEvent Platform account and you must associate all required certificates for publishing + signature key.

InEvent will not perform the development of store default images; you must develop all of them based on the sizes and formats authorized by the Apple Store. Access the link for more information.

Creating a Provisioning Profile

A provisioning profile links your developer account, the devices on which you can install your app, and an App ID, ensuring that your app can be tested on physical devices and distributed via the App Store or Ad Hoc distribution.

Before creating a provisioning profile, you need:

• A development or distribution certificate.
• An App ID for your app.

Creating a development or distribution certificate.

follow the steps below to create a distribution certificate:

1. Go to the Apple Developer Center: developer.apple.com.
2. Log in with your developer account.
3. Navigate to Certificates, Identifiers & Profiles.
4. Follow the instructions to create a development certificate (for testing) or a distribution certificate (for the App Store).

Creating an App ID

To create an App ID follow the steps below:

1. Log in to the Apple Developer Center: developer.apple.com.
2. Go to Certificates, Identifiers & Profiles.
3. Select the Identifiers section and click the add button (+).
4. Choose App IDs and fill in the required information, such as the app name, Bundle ID, and select the app services you want to enable.
5. Click Continue and then Register to create the App ID.

Creating a development provisioning profile

Once you are done creating your distribution certificate and App ID, you can now create your provision profile. To do this follow the steps below:

1. In the Apple Developer Center, go to the Profiles section and click the add button (+).
2. Select iOS App Development and click Continue.
3. Choose the App ID corresponding to your app and click Continue.
4. Select the development certificate you created earlier and click Continue.
5. Select the devices you want to test the app on and click Continue.
6. Name your provisioning profile and click Generate.
7. Download the generated provisioning profile (.mobileprovision) and save it in a secure location.

Creating a distribution provisioning profile (App Store or Ad Hoc)

To create a distribution provisioning profile, follow the steps below:

1. In the Apple Developer Center, go to the Profiles section and click the add button (+).
2. Select App Store for App Store distribution or Ad Hoc for distribution outside the App Store and click Continue.
3. Choose the App ID corresponding to your app and click Continue.
4. Select the distribution certificate you created earlier and click Continue.
5. (For Ad Hoc) Select the devices you want to distribute the app to and click Continue.
6. Name your provisioning profile and click Generate.
7. Download the generated provisioning profile (.mobileprovision) and save it in a secure location.

Installing the provisioning profile in Xcode

1. Open Xcode.
2. Go to Xcode > Preferences in the menu and select the Accounts tab.
3. Select your Apple ID and the corresponding development team.
4. Drag the downloaded .mobileprovision file into the Xcode window to install it.

Configuring Xcode to use the certificate and provisioning profile

1. Open your project in Xcode.
2. Select your app's target from the left panel.
3. Go to the Signing & Capabilities tab.
4. Check the Automatically manage signing option, or if you prefer, uncheck it and manually select the provisioning profile and certificate you installed.

Creating a distribution certificate

To creat a distribution certificate, you first have to create a Private Key and a Certificate Signing Request (CSR). Follow the steps below to do this:

1. Open Keychain Access on your Mac (found in the Utilities folder inside the Applications folder).
2. In the Keychain Access menu, go to Certificate Assistant > Request a Certificate From a Certificate Authority.
3. Fill in the requested information:
   • Email Address: Your email address associated with your Apple Developer account.
   • Common Name: Your full name.
   • CA Email Address: Leave it blank.
   • Request is: Select Saved to disk.
4. Click Continue and save the CSR file to a secure location on your Mac.

Once this is done, you will have to request a certificate on the Apple Developer Portal.

Requesting a certificate on the Apple Developer Portal

To request a certificate on the Apple Developer Portal follow the steps below;

1. Go to the Apple Developer Center: developer.apple.com.
2. Log in with your developer account.
3. In the menu, select Certificates, Identifiers & Profiles.
4. Go to the Certificates section and click the add button (+).
5. Select App Store and Ad Hoc (or Apple Distribution for unified certificates) and click Continue.
6. Upload the CSR file you created earlier and click Continue.
7. Download the generated certificate (.cer) and save it in a secure location.

You can now install the certificate in Keychain Access. To install the certificate in Keychain Access, Double-click the downloaded .cer file to open it in Keychain Access. The certificate will then be automatically installed in your keychain.

Creating a Push Certificate (p12)

To create a Push certificate, you will have to create a Private Key and Certificate Signing Request (CSR)

Follow the steps below to create a push certificate.

1. Open Keychain Access: You can find it in the Utilities folder inside the Applications folder on your Mac.
2. Request a Certificate: In the Keychain Access menu, go to Certificate Assistant > Request a Certificate From a Certificate Authority.

Fill in the requested information:

• Email Address: Your email address associated with your Apple Developer account.
• Common Name: Your full name.
• CA Email Address: Leave it blank.
• Request is: Select "Saved to disk".

Click Continue and save the CSR file to a secure location on your Mac.

Once you have completed the above steps, you can now generate the Push Certificate on the Apple Developer Portal. To do this, Follow the steps below:

1. Log in to the Apple Developer Center: developer.apple.com.
2. Navigate to Certificates, Identifiers & Profiles:

• Go to the Identifiers section, select App IDs, and find your app from the list.
• Click on your app ID and then click the Edit button.

1. Create the Push Certificate:

• Scroll down to the Push Notifications section and click Create Certificate under either the Development SSL Certificate or Production SSL Certificate, depending on your needs.
• Upload the CSR file you created earlier and click Generate.
• Download the generated certificate (.cer) and save it in a secure location.

You can now install the Push Certificate in Keychain Access. Follow the steps below to do this.

1. Install the Certificate:

• Double-click the downloaded .cer file to open it in Keychain Access.
• The certificate will be automatically installed in your keychain.

1. Export the Certificate as a .p12 File

In Keychain Access, find the installed certificate. It should be listed under the My Certificates category.

To export the certificate, follow the steps below:

1. Right-click on the certificate and select Export.
2. Choose a location to save the exported file and set the file format to Personal Information Exchange (.p12).
3. Click Save and set a strong password for the .p12 file when prompted. Remember this password as you will need it to import the certificate later.
4. Click OK to finish the export process.

You now have a .p12 file that you can use for setting up push notifications in your app. This file will be required when configuring your push notification service, such as Firebase Cloud Messaging (FCM) or another service provider.

Changing the app store name on apple

To change the App Store name for your app on Apple, follow these steps:

1. Log into App Store Connect
   Go to App Store Connect and sign in with your Apple Developer account.
2. Select Your App
   Click on My Apps and choose the app whose name you want to change.
3. Go to App Information
   In the left-hand menu, navigate to App Information under the General section.
4. Edit the Name
   Find the App Store Name field and enter the new name you want.
5. Save and Submit for Review
   Click Save and then submit an update for review. The new name will go live once Apple approves the update.

Important Notes:

• The App Store Name must be unique and follow Apple’s guidelines.
• Changing the name does not require a new app version, but submitting an update (even a minor one) is required.
• The name change will reflect in the App Store after Apple approves the update.

How long does it take for Apple to review and approve updates?

Apple typically takes 1 to 3 business days to review and approve an app update, including a name change. However, approval times can vary depending on factors such as:

• App complexity – More complex apps may take longer to review.
• Compliance with guidelines – If the app violates Apple's guidelines, it may be rejected or require resubmission.
• Review backlog – During peak times (e.g., before holidays or major updates), reviews may take longer.
  Once the app is submitted and awaiting review and approval from Apple, InEvent has no control over the processing time.

Google Play Store

InEvent signature binary file (APK) delivery

1. If it is not possible to receive access to the store for publication of the app; you will receive the APK file developed, based on the information registered in your InEvent Platform account and our signature to continue the publishing.
2. InEvent will take up to 10 business days to generate the APK file the first time you request it. The second time, it will take up to 10 business days. You will receive an email from InEvent with the file. You can also contact us via chat and request the files.

InEvent will not perform the development of store default images; you must develop all images based on the sizes and formats authorized by the Google Play Store.

InEvent Unclosed binary file transfer (APK)

If it is not possible to receive access to the store for publication of the app; you will receive the APK file (binary in the format accepted by Google Play) developed based on the information registered in your InEvent Platform account and not associated with any subscription to follow the publication.

InEvent will not perform the development of store default images; you must develop all based on the sizes and formats authorized by Google Play and associate your developer signature.

Deadlines: when will the app be available?

Click here for further information about important deadlines regarding the app publishing process.

Certificates renewal

InEvent automatically renews all certificates for its clients, eliminating the need for manual renewal and ensuring continuous compliance without any action required.