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 options do I have regarding having my app published?

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 the first time you request it. The second time, it will take up to 5 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 of them based on the sizes and formats authorized by the Apple Store. Access the link for more information: http://iosres.com/

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: http://iosres.com/

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 5 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.