Publish a Mendix Native App with Appcircle
Introduction
Once you have built your Mendix native app with Appcircle, you can publish it directly to the App Store or Google Play using Appcircle's built-in Publish to Stores module. This lets you manage the entire release pipeline—from build to store submission—within a single platform.
Prerequisites
Before starting this guide, make sure you have completed the following prerequisites:
- Set up a build profile and built your app by following Build a Mendix Native App with Appcircle
- iOS: have an App Store Connect API key
- Android: have a Google Play service account key
Set Up Store Connections
Before creating a publish profile, set up your store credentials under Credentials in the Appcircle organization settings. To access this, do the following:
- Click on your organization icon in the bottom-left corner.
- Select Security on the left panel.
- Go to the Credentials section.
- Choose the appropriate integration:
For iOS (App Store Connect):
- Click Add under App Store Connect Integrations.
- Provide a name for the integration (for example,
My App Store Connect). - Upload your App Store Connect API Key (.p8 file).
- Enter the Issuer ID and Key ID from your App Store Connect API key details.
- Save the integration.
For Android (Google Play Console):
- Click Add under Google Play Integrations.
- Provide a name for the integration (for example,
My Google Play Account). - Upload your Google Play service account JSON key file.
- Save the integration.
Once these integrations are configured, you can use them when creating publish profiles.
Create a Publish Profile
To create a publish profile, do the following:
- Go to the Publish to Stores module from the left navigation menu.
- Choose your platform (iOS or Android).
- Click Add New.
For iOS
For iOS, you have two options:
-
Create a profile manually:
- Select Create Profile Manually.
- Enter a Profile Name (for example,
My App - iOS). - Enter the Bundle ID (must exactly match the Bundle ID in your Xcode project and provisioning profile).
- Create the profile.
-
Create from App Store Connect:
- Select Create from App Store Connect.
- Choose the App Store Connect credential you configured in credential integrations.
- Select the app from the list of apps in your App Store Connect account.
- Appcircle automatically fills in the Bundle ID, app name, and other metadata.
For Android
For Android, you have two options:
-
Create Profile Manually:
- Select Create Profile Manually.
- Enter a Profile Name (for example,
My App - Android). - Enter the Package Name (must exactly match the Package Name in your Android project).
- Create the profile.
-
Create from Google Play Console:
- Select Create from Google Play Console.
- Choose the Google Play Console credential you configured in credential integrations.
- Select the app from the list of apps in your Google Play Console account.
- Appcircle automatically fills in the Package Name and other metadata.
Link the Publish Profile to Your Build Profile
To automatically send finished builds to the publish to stores module, do the following:
- Open the build profile in the Build module and go to the Build Configuration settings.
- Navigate to the Distribution tab.
- Enable the Automatically Distribute to Publish toggle.
- Select the publish profile you created.
- Save the configuration.
After this, completed builds will be sent to the publish profile where you can start the store submission flow.
Publish to the App Store or Google Play
Once a build appears in your publish profile, you can start the store submission process directly from Appcircle. For platform-specific walkthroughs, see the following Appcircle documentation:
Publish Report and Activity Log
The Publish Report provides a detailed overview of all actions performed within the Publish to Stores module. It allows users to monitor, filter, and export publish-related activities across different platforms, trigger types, and stores.
You can also view Publish to Stores module actions such as Publish Flow and Publish Step statutes, along with resign binary operations within the Organizations or Sub-Organizations in the Activity Log section.