From 273f7a5b9e1e917b4120e4d5f0b4283172b35098 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Sarp=20Bak=C4=B1=C5=9F?= Date: Thu, 30 Oct 2025 20:58:21 +0300 Subject: [PATCH 1/2] publish rename --- .../artifacts/retention-period.md | 2 +- docs/account/my-organization/billing/index.md | 2 +- .../profile-and-team/role-management.md | 6 +- .../adding-an-app-store-connect-api-key.md | 2 +- .../configurations.md | 2 +- .../enterprise-app-store-profile.md | 4 +- docs/enterprise-app-store/index.md | 2 +- .../android-publish-integrations/index.md | 2 +- .../publish-to-google-play.md | 4 +- .../publish-to-huawei-appgallery.md | 2 +- .../get-approval-via-email.md | 2 +- .../common-publish-integrations/index.md | 2 +- .../metadata-approval.md | 2 +- .../common-publish-integrations/send-email.md | 2 +- .../send-to-enterprise-app-store.md | 4 +- .../send-to-testing-distribution.md | 4 +- .../add-for-review-on-app-store.md | 2 +- .../app-information-app-store.md | 2 +- docs/publish-module/_category_.json | 2 +- .../publish-module/binary-management/index.md | 10 +-- .../creating-publish-profiles/index.md | 10 +-- docs/publish-module/index.md | 28 +++--- .../publish-activity-log/index.md | 4 +- docs/publish-module/publish-flow/index.md | 4 +- .../publish-information/app-information.md | 2 +- .../auto-resign-configuration.md | 6 +- .../publish-information/binary-information.md | 8 +- .../check-release-status.md | 2 +- .../publish-information/delete.md | 14 +-- .../publish-information/download.md | 10 +-- .../google-play-information.md | 2 +- .../publish-information/history.md | 8 +- .../publish-information/index.md | 14 +-- .../meta-data-information.md | 2 +- .../publish-information/publish-details.md | 4 +- .../publish-information/resign-binary.md | 8 +- docs/publish-module/publish-report/index.md | 4 +- .../publish-resign-report/index.md | 6 +- docs/publish-module/publish-settings/index.md | 4 +- .../publish-module/publish-variables/index.md | 6 +- .../index.md | 86 +++++++++---------- .../index.md | 44 +++++----- docs/release-notes.md | 2 +- ...create-or-select-a-distribution-profile.md | 2 +- 44 files changed, 170 insertions(+), 170 deletions(-) diff --git a/docs/account/my-organization/artifacts/retention-period.md b/docs/account/my-organization/artifacts/retention-period.md index bf32ec70b..657c1faaf 100644 --- a/docs/account/my-organization/artifacts/retention-period.md +++ b/docs/account/my-organization/artifacts/retention-period.md @@ -72,7 +72,7 @@ Automatically deletes **undistributed artifacts** that exceed the defined retent **Publish to Stores** module includes specific rules for published artifacts: -#### Delete Publish Module Artifacts +#### Delete Publish to Stores Artifacts Automatically deletes artifacts that have been **published** and are older than the retention period. #### Keep if Marked as RC diff --git a/docs/account/my-organization/billing/index.md b/docs/account/my-organization/billing/index.md index 0f9308092..d841661ad 100644 --- a/docs/account/my-organization/billing/index.md +++ b/docs/account/my-organization/billing/index.md @@ -24,7 +24,7 @@ The Billing section allows you to monitor your usage summary, including builds, - **[Builds](/build/build-process-management/manual-builds)** : Number of builds initiated from the build module in a single billing cycle. - **[Code Push Updates](/code-push)** : The number of devices receiving CodePush updates within a single billing cycle. - **[Testing Distribution](/testing-distribution/testing-portal)** : Number of app downloads from the Testing Portal in a single billing cycle. -- **[Publishes](/publish-module)** : Number of publishes initiated from the Publish module in a single billing cycle. +- **[Publishes](/publish-module)** : Number of publishes initiated from the Publish to Stores in a single billing cycle. - **[Enterprise App Store](/enterprise-app-store/enterprise-portal)** : Number of app downloads from the Enterprise App Store in a single billing cycle. - **[Team Members](/account/my-organization/profile-and-team/team-management)** : Number of team members allowed in a single organization. - **[Artifact Storage](/account/my-organization/artifacts)** : Total storage size for all the build and distribution artifacts across the platform. diff --git a/docs/account/my-organization/profile-and-team/role-management.md b/docs/account/my-organization/profile-and-team/role-management.md index 5ae58f1bf..00b913d1b 100644 --- a/docs/account/my-organization/profile-and-team/role-management.md +++ b/docs/account/my-organization/profile-and-team/role-management.md @@ -40,7 +40,7 @@ Some role types are not used in certain modules because they are redundant or un When assigning roles on Appcircle, you can assign more than one role for a user at the same time. For example, a user can be both **Manager** and **Operator** in the Build module. -For this reason, Appcircle behavior will change when multiple roles are assigned. For example, you have assigned **Ext Operator** and **Viewer** role in **Publish Module** for a user. This means that the Ext Operator role now has the privileges of the Viewer role. So while Ext Operator cannot see Activity logs, it now has access to those logs because it also has the viewer role. +For this reason, Appcircle behavior will change when multiple roles are assigned. For example, you have assigned **Ext Operator** and **Viewer** role in **Publish to Stores** for a user. This means that the Ext Operator role now has the privileges of the Viewer role. So while Ext Operator cannot see Activity logs, it now has access to those logs because it also has the viewer role. ::: @@ -221,7 +221,7 @@ The following table details the roles and restrictions for the [**Testing Groups | Testing Groups | List LDAP Groups and Members | ✅ | ✅ | ✅ | -### Publish Module iOS Permissions +### Publish to Stores iOS Permissions The following table details the roles and restrictions for the [**Publish**](/publish-module) module for iOS. Please refer to the related module information and caution notes. @@ -265,7 +265,7 @@ User can resign the binary if this user has **Manager** or **Viewer** Signing Id ::: -### Publish Module Android Permissions +### Publish to Stores Android Permissions The following table details the roles and restrictions for the [**Publish**](/publish-module) module for Android. Please refer to the related modules information and caution notes. diff --git a/docs/account/my-organization/security/credentials/adding-an-app-store-connect-api-key.md b/docs/account/my-organization/security/credentials/adding-an-app-store-connect-api-key.md index 4aaa34114..6e3f112a0 100644 --- a/docs/account/my-organization/security/credentials/adding-an-app-store-connect-api-key.md +++ b/docs/account/my-organization/security/credentials/adding-an-app-store-connect-api-key.md @@ -122,7 +122,7 @@ Once the API key is generated, it must be added to Appcircle: 6. Click Save to complete the setup. :::info -Please note that the registered Enterprise API Key cannot be used within the Publish module because the Apple Enterprise Program does not provide TestFlight or App Store Connect services. +Please note that the registered Enterprise API Key cannot be used within the Publish to Stores because the Apple Enterprise Program does not provide TestFlight or App Store Connect services. ::: ## Sharing App Store Connect Credentials diff --git a/docs/build/build-process-management/configurations.md b/docs/build/build-process-management/configurations.md index c4485be65..2e0d57de2 100644 --- a/docs/build/build-process-management/configurations.md +++ b/docs/build/build-process-management/configurations.md @@ -185,7 +185,7 @@ Enabling "Automatically Distribute to Publish" will display the available [Publi Simply select your relevant publish profiles, and Appcircle will automatically send your builds to the selected publish profiles. -Please note that the publish profiles should be created within the publish module prior to configuring the distribution settings in the build profile. +Please note that the publish profiles should be created within the Publish to Stores prior to configuring the distribution settings in the build profile. #### Send to Enterprise App Store diff --git a/docs/enterprise-app-store/enterprise-app-store-profile.md b/docs/enterprise-app-store/enterprise-app-store-profile.md index 26f8f4e60..7beeaf2a7 100644 --- a/docs/enterprise-app-store/enterprise-app-store-profile.md +++ b/docs/enterprise-app-store/enterprise-app-store-profile.md @@ -15,7 +15,7 @@ The Enterprise App Store provides a centralized platform for managing an organiz ## Creating a Profile -An Enterprise build profile can be created in several ways. IPA or APK files can either be manually uploaded or sent from Appcircle’s Distribution, Build, or Publish modules. +An Enterprise build profile can be created in several ways. IPA or APK files can either be manually uploaded or sent from Appcircle’s Distribution, Build, or Publish to Storess. ## Uploading Binary @@ -49,7 +49,7 @@ Binaries can also be uploaded via the Build module. For more information, please Binaries can also be uploaded via the Testing Distribution module. For more information, please visit the [Testing Distribution](/testing-distribution/create-or-select-a-distribution-profile#send-your-application-to-enterprise-app-store) documentation. -### Upload via Publish Module +### Upload via Publish to Stores module The Publish Flow steps can be customized to send the binary to the Enterprise App Store. For more information, please visit the [Publish Integrations](/publish-integrations/common-publish-integrations/send-to-enterprise-app-store) documentation. diff --git a/docs/enterprise-app-store/index.md b/docs/enterprise-app-store/index.md index f3c9f71cd..e2b4530a2 100644 --- a/docs/enterprise-app-store/index.md +++ b/docs/enterprise-app-store/index.md @@ -29,7 +29,7 @@ For a complete overview of the Appcircle Enterprise App Store module capabilitie ## [Enterprise App Store Profile](/enterprise-app-store/enterprise-app-store-profile) -There are several ways to create an Enterprise App Store Profile. You can either manually upload your IPA or APK files or send them through Appcircle's Distribution, Build, or Publish modules. +There are several ways to create an Enterprise App Store Profile. You can either manually upload your IPA or APK files or send them through Appcircle's Distribution, Build, or Publish to Stores modules. Enterprise App Store Profile] diff --git a/docs/publish-integrations/android-publish-integrations/index.md b/docs/publish-integrations/android-publish-integrations/index.md index 6558db7c9..543f9ea24 100644 --- a/docs/publish-integrations/android-publish-integrations/index.md +++ b/docs/publish-integrations/android-publish-integrations/index.md @@ -8,7 +8,7 @@ tags: [android, android integrations, android publish integrations] Appcircle's Android Integrations facilitate the distribution of your Android applications to major app stores with minimal effort. -To use the Android Integration, click on the **Android Publish** button on the left in the Publish module. +To use the Android Integration, click on the **Android Publish** button on the left in the Publish to Stores module. diff --git a/docs/publish-integrations/android-publish-integrations/publish-to-google-play.md b/docs/publish-integrations/android-publish-integrations/publish-to-google-play.md index c2189ef33..2e5f6e121 100644 --- a/docs/publish-integrations/android-publish-integrations/publish-to-google-play.md +++ b/docs/publish-integrations/android-publish-integrations/publish-to-google-play.md @@ -1,6 +1,6 @@ --- title: Publish to Google Play -description: Publish your Android applications to the Google Play Store with Appcircle's Publish module. +description: Publish your Android applications to the Google Play Store with Appcircle's Publish to Stores module. tags: [android, publish google play, android publish integrations] sidebar_position: 2 --- @@ -11,7 +11,7 @@ import RunnerUsage from '@site/docs/\_publish-steps-runner-usage-caution.mdx'; # Publish to Google Play -Appcircle supports sending APK and AAB binaries to [Google Play](https://play.google.com) through the Publish module. +Appcircle supports sending APK and AAB binaries to [Google Play](https://play.google.com) through the Publish to Stores module. Google Play no longer supports APK submission; however, Appcircle retains the APK submission feature for exceptional cases. For more details about APK submission, please refer to this document: > [Google Play requires new apps to be published with the Android App Bundle starting August 2021.](https://android-developers.googleblog.com/2021/06/the-future-of-android-app-bundles-is.html) diff --git a/docs/publish-integrations/android-publish-integrations/publish-to-huawei-appgallery.md b/docs/publish-integrations/android-publish-integrations/publish-to-huawei-appgallery.md index 8b201a98a..9daaa2840 100644 --- a/docs/publish-integrations/android-publish-integrations/publish-to-huawei-appgallery.md +++ b/docs/publish-integrations/android-publish-integrations/publish-to-huawei-appgallery.md @@ -11,7 +11,7 @@ import RunnerUsage from '@site/docs/\_publish-steps-runner-usage-caution.mdx'; # Publish to Huawei AppGallery -Appcircle supports sending [APK](https://developer.huawei.com/consumer/en/doc/app/agc-help-releaseapkrpk-0000001106463276) and [AAB](https://developer.huawei.com/consumer/en/doc/app/agc-help-releasebundle-0000001100316672) binaries to [Huawei AppGallery](https://appgallery.huawei.com/) through the Publish module. +Appcircle supports sending [APK](https://developer.huawei.com/consumer/en/doc/app/agc-help-releaseapkrpk-0000001106463276) and [AAB](https://developer.huawei.com/consumer/en/doc/app/agc-help-releasebundle-0000001100316672) binaries to [Huawei AppGallery](https://appgallery.huawei.com/) through the Publish to Stores module. diff --git a/docs/publish-integrations/common-publish-integrations/get-approval-via-email.md b/docs/publish-integrations/common-publish-integrations/get-approval-via-email.md index 0beef9727..e7d3af554 100644 --- a/docs/publish-integrations/common-publish-integrations/get-approval-via-email.md +++ b/docs/publish-integrations/common-publish-integrations/get-approval-via-email.md @@ -40,7 +40,7 @@ For example, imagine you need approval from at least two people to keep the flow ### Email Template -With the Email Approval step provided by the Appcircle Publish module, release processes are managed in a structured and controlled way. The email includes all key information, such as binary details, release notes, and other relevant data, so users can review the release context without needing to search within the Appcircle interface. +With the Email Approval step provided by the Appcircle Publish to Stores module, release processes are managed in a structured and controlled way. The email includes all key information, such as binary details, release notes, and other relevant data, so users can review the release context without needing to search within the Appcircle interface. To proceed with the approval, users can click the link in the email, which opens the binary details window in Appcircle. From this view, they can examine version information, build details, and commit history before making a decision by selecting **Approve** or **Reject**. diff --git a/docs/publish-integrations/common-publish-integrations/index.md b/docs/publish-integrations/common-publish-integrations/index.md index 5e633277f..5c0fd139b 100644 --- a/docs/publish-integrations/common-publish-integrations/index.md +++ b/docs/publish-integrations/common-publish-integrations/index.md @@ -39,7 +39,7 @@ Appcircle's integration tools are designed to simplify and automate the publishi ## [Send to Testing Distribution](/publish-integrations/common-publish-integrations/send-to-testing-distribution) -With Appcircle's Publish module, you can submit your application to external stores such as App Store, Google Play, Huawei AppGallery or Microsoft Intune, as well as to Appcircle's Testing Distribution module. +With Appcircle's Publish to Stores module, you can submit your application to external stores such as App Store, Google Play, Huawei AppGallery or Microsoft Intune, as well as to Appcircle's Testing Distribution module. Testing Distribution module allows you to distribute your application without the need for any external tools. diff --git a/docs/publish-integrations/common-publish-integrations/metadata-approval.md b/docs/publish-integrations/common-publish-integrations/metadata-approval.md index 714fa4b1c..33c090781 100644 --- a/docs/publish-integrations/common-publish-integrations/metadata-approval.md +++ b/docs/publish-integrations/common-publish-integrations/metadata-approval.md @@ -23,7 +23,7 @@ When this step runs in your workflow, Appcircle sends a unique approval email to :::caution Metadata Approval Panel -Access to the Metadata Approval Panel is **exclusively** available via the link sent in the approval email; it is **not** accessible through the standard Publish module UI. +Access to the Metadata Approval Panel is **exclusively** available via the link sent in the approval email; it is **not** accessible through the standard Publish to Stores module UI. ::: diff --git a/docs/publish-integrations/common-publish-integrations/send-email.md b/docs/publish-integrations/common-publish-integrations/send-email.md index d29c952e3..e43448048 100644 --- a/docs/publish-integrations/common-publish-integrations/send-email.md +++ b/docs/publish-integrations/common-publish-integrations/send-email.md @@ -66,7 +66,7 @@ You can dynamically populate subject and content using environment variables. Th ### Creating Environment Variables -First, you need to define the environment variables. To do this, go to the Publish module and select Publish Variables. From there, you can start creating the variables for your email settings. +First, you need to define the environment variables. To do this, go to the Publish to Stores module and select Publish Variables. From there, you can start creating the variables for your email settings. diff --git a/docs/publish-integrations/common-publish-integrations/send-to-enterprise-app-store.md b/docs/publish-integrations/common-publish-integrations/send-to-enterprise-app-store.md index d0edb9e6d..361459a9a 100644 --- a/docs/publish-integrations/common-publish-integrations/send-to-enterprise-app-store.md +++ b/docs/publish-integrations/common-publish-integrations/send-to-enterprise-app-store.md @@ -1,6 +1,6 @@ --- title: Send to Enterprise App Store -description: Learn how to send Binary to Enterprise App Store in the Publish module of Appcircle +description: Learn how to send Binary to Enterprise App Store in the Publish to Stores module of Appcircle tags: [publish, publish module, enterprise, app store, enterprise app store, review] sidebar_position: 4 --- @@ -10,7 +10,7 @@ import NoRunnerUsage from '@site/docs/\_publish-steps-runner-no-usage-info.mdx'; # Send to Enterprise App Store -With Appcircle's Publish module, you can submit your application to external stores such as App Store, Google Play, Huawei AppGallery or Microsoft Intune, as well as to Appcircle's Enterprise App Store module. +With Appcircle's Publish to Stores module, you can submit your application to external stores such as App Store, Google Play, Huawei AppGallery or Microsoft Intune, as well as to Appcircle's Enterprise App Store module. Enterprise App Store offers a store structure that you can use and customise for internal application distribution. For detailed information, please see the [**Enterprise App Store document**](/enterprise-app-store). diff --git a/docs/publish-integrations/common-publish-integrations/send-to-testing-distribution.md b/docs/publish-integrations/common-publish-integrations/send-to-testing-distribution.md index 4fbb13249..287ae131b 100644 --- a/docs/publish-integrations/common-publish-integrations/send-to-testing-distribution.md +++ b/docs/publish-integrations/common-publish-integrations/send-to-testing-distribution.md @@ -1,6 +1,6 @@ --- title: Send to Testing Distribution -description: Learn how to send Binary to Testing Distribution in the Publish module of Appcircle +description: Learn how to send Binary to Testing Distribution in the Publish to Stores module of Appcircle tags: [publish, publish module, distribution, testing distribution] sidebar_position: 4 --- @@ -10,7 +10,7 @@ import NoRunnerUsage from '@site/docs/\_publish-steps-runner-no-usage-info.mdx'; # Send to Testing Distribution -With Appcircle's Publish module, you can submit your application to external stores such as App Store, Google Play, Huawei AppGallery or Microsoft Intune, as well as to Appcircle's Testing Distribution module. +With Appcircle's Publish to Stores module, you can submit your application to external stores such as App Store, Google Play, Huawei AppGallery or Microsoft Intune, as well as to Appcircle's Testing Distribution module. Testing Distribution module allows you to distribute your application without the need for any external tools. For detailed information, please see the [**Testing Distribution Documentation**](/testing-distribution). diff --git a/docs/publish-integrations/ios-publish-integrations/add-for-review-on-app-store.md b/docs/publish-integrations/ios-publish-integrations/add-for-review-on-app-store.md index 69214cc05..2d3f2960f 100644 --- a/docs/publish-integrations/ios-publish-integrations/add-for-review-on-app-store.md +++ b/docs/publish-integrations/ios-publish-integrations/add-for-review-on-app-store.md @@ -10,7 +10,7 @@ import RunnerUsage from '@site/docs/\_publish-steps-runner-usage-caution.mdx'; # Add for Review on App Store -Appcircle Publish Module isolates the user to a great extent in the App Store Connect interface with its steps. This allows you to manage the publishing process from a single location.. With the Add for Review on App Store step, you can send your application version in TestFlight directly for review. +Appcircle Publish to Stores module isolates the user to a great extent in the App Store Connect interface with its steps. This allows you to manage the publishing process from a single location.. With the Add for Review on App Store step, you can send your application version in TestFlight directly for review. diff --git a/docs/publish-integrations/ios-publish-integrations/app-information-app-store.md b/docs/publish-integrations/ios-publish-integrations/app-information-app-store.md index 9644a43e2..343433f29 100644 --- a/docs/publish-integrations/ios-publish-integrations/app-information-app-store.md +++ b/docs/publish-integrations/ios-publish-integrations/app-information-app-store.md @@ -25,7 +25,7 @@ Below are brief descriptions of the information provided on the App Information | **App Name** | The display name of the application on the selected platform. | | | **Version** | The current available app versions. For example, `1.0.5`. | | | **Build Number** | Version code information of your application. For example, `1.0.5(1)`. | | -| **Uploaded Date** | Date the application was first uploaded. The **Release Candidate** version is based on the date it was uploaded to the **Publish module**. | | +| **Uploaded Date** | Date the application was first uploaded. The **Release Candidate** version is based on the date it was uploaded to the **Publish to Stores module**. | | | **Expire Date** | The expiration date of the application version in TestFlight and the App Store. The **Release Candidate** version does not have an expiration date. | | | **Release Type** | Indicates the release type of your application. For example, if you have an application released to the market, you will see the type as **After Approval**. | | | **Processing State** | This indicates the status of your application; it will appear as **`Valid`** when there are no issues. For instance, if your application has expired in the TestFlight environment, the state will be **`Expire`**. If the application is rejected, the state will be **`Reject`**. | | diff --git a/docs/publish-module/_category_.json b/docs/publish-module/_category_.json index 6217caa94..c192d2699 100644 --- a/docs/publish-module/_category_.json +++ b/docs/publish-module/_category_.json @@ -1,5 +1,5 @@ { - "label": "Publish", + "label": "Publish to Stores", "position": 12, "collapsed": true, "collapsible": true, diff --git a/docs/publish-module/binary-management/index.md b/docs/publish-module/binary-management/index.md index 9d9b1fe0f..f8da27431 100644 --- a/docs/publish-module/binary-management/index.md +++ b/docs/publish-module/binary-management/index.md @@ -54,7 +54,7 @@ For this, click on the **Actions** button for the relevant version and go to **D ## Store Status -Appcircle now allows you to track the App Store status of your applications directly within the Publish module. This powerful feature is tailored for **Enterprise License** holders, ensuring continuous monitoring of your application's deployment status. +Appcircle now allows you to track the App Store status of your applications directly within the Publish to Stores module. This powerful feature is tailored for **Enterprise License** holders, ensuring continuous monitoring of your application's deployment status. @@ -74,7 +74,7 @@ This streamlined approach ensures that you are always informed of your applicati ### Filter By Status -In the Publish module, where your Publish profiles are listed, you can use the filter option to display specific Publish profiles based on their latest store status. +In the Publish to Stores module, where your Publish profiles are listed, you can use the filter option to display specific Publish profiles based on their latest store status. @@ -92,7 +92,7 @@ The iOS Publish filter options will only display the available statuses from the ## FAQ -### How can I get a binary from another organization to use in the Publish Module ? +### How can I get a binary from another organization to use in the Publish to Stores module ? Let’s assume there are two organizations: Organization A and Organization B. In Organization A, we have a build profile that generates an IPA, APK, or AAB. @@ -139,8 +139,8 @@ To generate Personal Access Key, follow this documentation [API authentication]( To obtain the Publish profile ID, follow the steps below: 1. Log in to organization B. -2. Go to Publish module. -3. Select the desired Publish profile +2. Go to Publish to Stores module. +3. Select the desired Publish profile. 4. Copy it from the URL. `https://my.appcircle.io/publish/android/123456f-7d89-4545-5454-123456789abc` 5. Then the Publish profile ID is => `123456f-7d89-4545-5454-123456789abc` diff --git a/docs/publish-module/creating-publish-profiles/index.md b/docs/publish-module/creating-publish-profiles/index.md index 19b3149f1..b3b1c5e95 100644 --- a/docs/publish-module/creating-publish-profiles/index.md +++ b/docs/publish-module/creating-publish-profiles/index.md @@ -9,11 +9,11 @@ sidebar_position: 1 import Screenshot from '@site/src/components/Screenshot'; -After building the application, we can start the publishing process by sending it to the Publish module. +After building the application, we can start the publishing process by sending it to the Publish to Stores module. -For this, it is necessary to first create a publish profile within the Publish module. Afterwards, the relevant publish profile must be selected from the **Distribution** tab in the configuration of the relevant profile in the Build module. +For this, it is necessary to first create a publish profile within the Publish to Stores module. Afterwards, the relevant publish profile must be selected from the **Distribution** tab in the configuration of the relevant profile in the Build module. -In order to create a publish profile, click on the "Add New" button in the Publish module. +In order to create a publish profile, click on the "Add New" button in the Publish to Stores module. :::info If it's your first time, set up connections to the app stores under [API Integrations](/account/my-organization). @@ -80,9 +80,9 @@ Another option to create a profile is to import it. With this feature, a Publish :::caution Apple Enterprise API Key -The **Create from App Store Connect** feature requires an **Apple API** key to create a profile. However, since the **Apple Enterprise Program** does not include **TestFlight** or **App Store Connect** features, **Apple Enterprise API Keys** are **not** listed anywhere in the **Publish module**. +The **Create from App Store Connect** feature requires an **Apple API** key to create a profile. However, since the **Apple Enterprise Program** does not include **TestFlight** or **App Store Connect** features, **Apple Enterprise API Keys** are **not** listed anywhere in the **Publish to Stores module**. -If an **Apple Enterprise API** key has been added in your organization, it **cannot** be used in the Publish Module. For more information, please visit the [**Enterprise API Key Credential**](/account/my-organization/security/credentials/adding-an-app-store-connect-api-key#enterprise-api-key-option-for-app-store-connect) documentation. +If an **Apple Enterprise API** key has been added in your organization, it **cannot** be used in the Publish to Stores Module. For more information, please visit the [**Enterprise API Key Credential**](/account/my-organization/security/credentials/adding-an-app-store-connect-api-key#enterprise-api-key-option-for-app-store-connect) documentation. ::: diff --git a/docs/publish-module/index.md b/docs/publish-module/index.md index 9dc1a8738..1c44fb16d 100644 --- a/docs/publish-module/index.md +++ b/docs/publish-module/index.md @@ -1,19 +1,19 @@ --- -title: Publish +title: Publish to Stores sidebar_position: 1 tags: [publish, distribution, app store, google play, huawei appgallery, testflight, microsoft intune] -description: The Publish module in Appcircle allows you to distribute your mobile applications to the App Store, Google Play, Huawei AppGallery and Microsoft Intune. +description: The Publish to Stores module in Appcircle allows you to distribute your mobile applications to the App Store, Google Play, Huawei AppGallery and Microsoft Intune. --- import Screenshot from '@site/src/components/Screenshot'; import ContentRef from '@site/src/components/ContentRef'; -# Publish +# Publish to Stores -The Publish module is a powerful feature in Appcircle that allows you to distribute your mobile applications to the App Store, Google Play, Huawei AppGallery and Microsoft Intune. It provides a streamlined process for sending your apps directly to the stores or to TestFlight for beta testing. +The Publish to Stores module is a powerful feature in Appcircle that allows you to distribute your mobile applications to the App Store, Google Play, Huawei AppGallery and Microsoft Intune. It provides a streamlined process for sending your apps directly to the stores or to TestFlight for beta testing. :::tip Learn More -For a complete overview of the Appcircle Publish module capabilities, check out the [Appcircle's Profile Section](https://appcircle.io/publish-to-stores). +For a complete overview of the Appcircle Publish to Stores module capabilities, check out the [Appcircle's Profile Section](https://appcircle.io/publish-to-stores). ::: ## [Creating Publish Profiles](/publish-module/creating-publish-profiles) @@ -24,19 +24,19 @@ After building the application, in order to start the publishing process, you wi ## [Binary Management](/publish-module/binary-management) -Manage your binaries within the Publish module. +Manage your binaries within the Publish to Stores module. Binary Management ## [Publish Flow](/publish-module/publish-flow) -Appcircle includes a predefined flow in the Publish module for publishing the application to stores (App Store, Google Play, Huawei AppGallery, Microsoft Intune). This flow can be customized according to your specific publishing requirements. +Appcircle includes a predefined flow in the Publish to Stores module for publishing the application to stores (App Store, Google Play, Huawei AppGallery, Microsoft Intune). This flow can be customized according to your specific publishing requirements. Publish Flow ## [Publish Information](/publish-module/publish-information) -The Publish module provides users with several key actions to manage their application versions effectively. +The Publish to Stores module provides users with several key actions to manage their application versions effectively. Publish Information @@ -48,36 +48,36 @@ Manage your profile and publish settings via the Publish Settings. ## [Publish Variables](/publish-module/publish-variables) -The Publish Variables section within the Publish module is a feature that allows you to set up and manage key-value pairs that are essential for the app publishing process. +The Publish Variables section within the Publish to Stores module is a feature that allows you to set up and manage key-value pairs that are essential for the app publishing process. Publish Variables ## [Publish Walkthrough for App Store](/publish-module/publish-walkthrough-for-app-store) -The Publish module in Appcircle is a powerful tool designed for managing the release process of mobile applications to various app stores, including the Apple App Store, Google Play, and Huawei AppGallery. This module streamlines the complex process of app release via App Store Connect. +The Publish to Stores module in Appcircle is a powerful tool designed for managing the release process of mobile applications to various app stores, including the Apple App Store, Google Play, and Huawei AppGallery. This module streamlines the complex process of app release via App Store Connect. Publish Walkthrough for App Store ## [Publish Walkthrough for Google Play](/publish-module/publish-walkthrough-for-google-play) -The Publish module in Appcircle is a powerful tool designed for managing the release process of mobile applications to various app stores, including the Apple App Store, Google Play, and Huawei AppGallery. This module streamlines the complex process of app release via Google Play. +The Publish to Stores module in Appcircle is a powerful tool designed for managing the release process of mobile applications to various app stores, including the Apple App Store, Google Play, and Huawei AppGallery. This module streamlines the complex process of app release via Google Play. Publish Walkthrough for Google Play ## [Publish Report](/publish-module/publish-report) -The Publish Report provides a detailed overview of all actions performed within the Publish Module. It allows users to monitor, filter, and export publish-related activities across different platforms, trigger types, and stores. +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. Publish Report ## [Publish Re-sign Report](/publish-module/publish-resign-report) -The Publish Re-sign Report provides detailed visibility into the manual and automatic re-sign operations performed within the publish module. This report helps you monitor and analyze re-sign activities across your organization over a selected time period. +The Publish Re-sign Report provides detailed visibility into the manual and automatic re-sign operations performed within the Publish to Stores module. This report helps you monitor and analyze re-sign activities across your organization over a selected time period. Publish Re-sign Report ## [Publish Activity Log](/publish-module/publish-activity-log) -You can view Publish 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. +You can 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. Publish Activity Log \ No newline at end of file diff --git a/docs/publish-module/publish-activity-log/index.md b/docs/publish-module/publish-activity-log/index.md index 8ff377ec6..455006a1a 100644 --- a/docs/publish-module/publish-activity-log/index.md +++ b/docs/publish-module/publish-activity-log/index.md @@ -2,7 +2,7 @@ title: Publish Activity Log sidebar_position: 1 tags: [publish, activity log, search] -description: Understand the Activity Log for Publish in Appcircle, providing visibility on the usage of publish module over a given time period. +description: Understand the Activity Log for Publish in Appcircle, providing visibility on the usage of Publish to Stores module over a given time period. --- @@ -11,7 +11,7 @@ import CSVExport from '@site/docs/\_csv-export.mdx'; # Activity Log -You can view Publish 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. +You can 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. diff --git a/docs/publish-module/publish-flow/index.md b/docs/publish-module/publish-flow/index.md index 2f78c9aef..a8058c88c 100644 --- a/docs/publish-module/publish-flow/index.md +++ b/docs/publish-module/publish-flow/index.md @@ -10,11 +10,11 @@ import ContentRef from '@site/src/components/ContentRef'; # Publish Flow -Appcircle includes a predefined flow in the Publish module for publishing the application to stores (App Store, Google Play, Huawei AppGallery, Microsoft Intune). This flow can be customized according to your specific publishing requirements. +Appcircle includes a predefined flow in the Publish to Stores module for publishing the application to stores (App Store, Google Play, Huawei AppGallery, Microsoft Intune). This flow can be customized according to your specific publishing requirements. :::caution Runner Usage -Appcircle's Publish module requires a **runner** to operate. The runner dependency of each step in the **Publish Flows** is specified in the relevant step's documentation. For detailed information on runner dependencies, please refer to the documentation of the relevant steps. +Appcircle's Publish to Stores module requires a **runner** to operate. The runner dependency of each step in the **Publish Flows** is specified in the relevant step's documentation. For detailed information on runner dependencies, please refer to the documentation of the relevant steps. ::: diff --git a/docs/publish-module/publish-information/app-information.md b/docs/publish-module/publish-information/app-information.md index ee753ddd4..74fee3d4e 100644 --- a/docs/publish-module/publish-information/app-information.md +++ b/docs/publish-module/publish-information/app-information.md @@ -1,6 +1,6 @@ --- title: App Store Connect Information -description: Learn how to update App Information in the Publish module of Appcircle +description: Learn how to update App Information in the Publish to Stores module of Appcircle tags: [publish, publish module, app information, app store connect, review] sidebar_position: 1 --- diff --git a/docs/publish-module/publish-information/auto-resign-configuration.md b/docs/publish-module/publish-information/auto-resign-configuration.md index fb791e076..6b06f3058 100644 --- a/docs/publish-module/publish-information/auto-resign-configuration.md +++ b/docs/publish-module/publish-information/auto-resign-configuration.md @@ -1,17 +1,17 @@ --- title: Auto Re-sign -description: Learn how to automatically re-sign your binary in the Publish module of Appcircle +description: Learn how to automatically re-sign your binary in the Publish to Stores module of Appcircle tags: [publish, publish module, auto, re-sign, configuration] sidebar_position: 3 --- # Auto Re-sign -The **Auto Re-sign** feature in Appcircle’s Publish module allows users to automatically re-sign their iOS (`.ipa`) and Android (`.apk`/`.aab`) applications with a different keystore, provisioning profile, or certificate before distribution. +The **Auto Re-sign** feature in Appcircle’s Publish to Stores module allows users to automatically re-sign their iOS (`.ipa`) and Android (`.apk`/`.aab`) applications with a different keystore, provisioning profile, or certificate before distribution. ## Enabling Auto Re-sign -To use the **Auto Re-sign** feature in the Appcircle Publish module, you need to enable the **Auto Re-sign** toggle within the Publish Settings section. +To use the **Auto Re-sign** feature in the Appcircle Publish to Stores module, you need to enable the **Auto Re-sign** toggle within the Publish Settings section. :::caution Business Rule for Auto Publish and Auto Re-sign diff --git a/docs/publish-module/publish-information/binary-information.md b/docs/publish-module/publish-information/binary-information.md index b16047ae3..df98a1b4f 100644 --- a/docs/publish-module/publish-information/binary-information.md +++ b/docs/publish-module/publish-information/binary-information.md @@ -7,7 +7,7 @@ sidebar_position: 4 # Binary Information -The "Binary Information" feature in the Publish module provides essential details about the app's binary file. This information is critical for understanding the specifics of each build. +The "Binary Information" feature in the Publish to Stores module provides essential details about the app's binary file. This information is critical for understanding the specifics of each build. ## Viewing Binary Information @@ -15,7 +15,7 @@ To access the binary details for a specific version of your app: 1. **Navigate to the Appropriate Version:** - - Within the Publish module, locate and select the version you want to examine. + - Within the Publish to Stores module, locate and select the version you want to examine. 2. **Open Binary Information:** - Click on the "Binary Information" option to display the binary details. @@ -61,11 +61,11 @@ Release Notes are an important part of the binary information, providing context ### Adding Release Notes -Before publishing your binary to the app stores, you can add Release Notes in the Publish module: +Before publishing your binary to the app stores, you can add Release Notes in the Publish to Stores module: 1. **Access Binary Information:** - - Navigate to the 'Binary Information' section for the selected app version in the Publish module. + - Navigate to the 'Binary Information' section for the selected app version in the Publish to Stores module. 2. **Input Release Notes:** diff --git a/docs/publish-module/publish-information/check-release-status.md b/docs/publish-module/publish-information/check-release-status.md index a18cd9673..595156a52 100644 --- a/docs/publish-module/publish-information/check-release-status.md +++ b/docs/publish-module/publish-information/check-release-status.md @@ -1,6 +1,6 @@ --- title: Check Release Status -description: Learn how to check and update statuses in the Publish module of Appcircle +description: Learn how to check and update statuses in the Publish to Stores module of Appcircle tags: [publish, publish module, app information, app store connect, review] sidebar_position: 2 --- diff --git a/docs/publish-module/publish-information/delete.md b/docs/publish-module/publish-information/delete.md index 859174adc..2b761f3ca 100644 --- a/docs/publish-module/publish-information/delete.md +++ b/docs/publish-module/publish-information/delete.md @@ -1,6 +1,6 @@ --- title: Delete -description: Learn how to delete a build version in the Publish module of Appcircle +description: Learn how to delete a build version in the Publish to Stores module of Appcircle tags: [publish, publish module, delete] sidebar_position: 11 --- @@ -9,7 +9,7 @@ import Screenshot from '@site/src/components/Screenshot'; # Deleting a Build Version -The "Delete" function in the Publish module allows users to remove specific versions of an app from the module. This action does not affect any versions of the app that have been submitted to app stores; it only removes the version from Appcircle's Publish module. +The "Delete" function in the Publish to Stores module allows users to remove specific versions of an app from the module. This action does not affect any versions of the app that have been submitted to app stores; it only removes the version from Appcircle's Publish to Stores module. @@ -17,7 +17,7 @@ The "Delete" function in the Publish module allows users to remove specific vers 1. **Locate the Version:** - - Find the app version you wish to delete in the Publish module. + - Find the app version you wish to delete in the Publish to Stores module. 2. **Access Delete Option:** @@ -36,15 +36,15 @@ The "Delete" function in the Publish module allows users to remove specific vers - **Check Before Deleting:** Always double-check which version you are deleting to prevent removing the wrong one. - **Irreversible Action:** Deletion is permanent. Once a version is deleted, it cannot be recovered through Appcircle. -- **Does Not Affect Store Submissions:** Deleting a version from Appcircle's Publish module does not remove it from any app stores where it has been published. +- **Does Not Affect Store Submissions:** Deleting a version from Appcircle's Publish to Stores module does not remove it from any app stores where it has been published. ## Use Cases for Deleting a Build Version -- **Cleaning Up:** Remove outdated or unnecessary builds to keep your Publish module organized. -- **Storage Management:** Free up space in your Publish module by deleting old or superseded versions. +- **Cleaning Up:** Remove outdated or unnecessary builds to keep your Publish to Stores module organized. +- **Storage Management:** Free up space in your Publish to Stores module by deleting old or superseded versions. Remember to use this feature judiciously to maintain the integrity of your build history and avoid accidental loss of important build versions. :::caution -Appcircle does not delete the application that has been submitted to the stores. This deletion will only delete the version of the application in the Publish module. +Appcircle does not delete the application that has been submitted to the stores. This deletion will only delete the version of the application in the Publish to Stores module. ::: diff --git a/docs/publish-module/publish-information/download.md b/docs/publish-module/publish-information/download.md index 89857e76f..36ec3073f 100644 --- a/docs/publish-module/publish-information/download.md +++ b/docs/publish-module/publish-information/download.md @@ -1,6 +1,6 @@ --- title: Downloading Binaries -description: Learn how to download the built application files from the Publish module in Appcircle +description: Learn how to download the built application files from the Publish to Stores in Appcircle tags: [publish, download, binaries, distribution] sidebar_position: 8 --- @@ -9,7 +9,7 @@ import Screenshot from '@site/src/components/Screenshot'; # Downloading Binaries -The "Download" function in the Publish module allows you to easily download the built application files, such as IPA for iOS or APK/AAB for Android, directly to your local system. +The "Download" function in the Publish to Stores module allows you to easily download the built application files, such as IPA for iOS or APK/AAB for Android, directly to your local system. @@ -17,7 +17,7 @@ The "Download" function in the Publish module allows you to easily download the 1. **Navigate to the Desired Version:** - - In the Publish module, locate the version of the app that you want to download. + - In the Publish to Stores module, locate the version of the app that you want to download. 2. **Open the Options Menu:** @@ -36,8 +36,8 @@ The "Download" function in the Publish module allows you to easily download the ## Use Cases for Downloading Binaries -- **Local Testing:** Quickly grab a build for local testing or sharing with testers who may not have access to the Publish module. +- **Local Testing:** Quickly grab a build for local testing or sharing with testers who may not have access to the Publish to Stores module. - **Backup:** Keep a local backup of certain builds for record-keeping or rollback purposes. - **Distribution:** Manually distribute the build to other services or stakeholders as needed. -Please note that the availability of binaries for download might depend on the retention policy set within the Publish module or the build's life cycle management rules. Make sure to download the binaries you need before they are auto-purged if such a policy is in place. +Please note that the availability of binaries for download might depend on the retention policy set within the Publish to Stores module or the build's life cycle management rules. Make sure to download the binaries you need before they are auto-purged if such a policy is in place. diff --git a/docs/publish-module/publish-information/google-play-information.md b/docs/publish-module/publish-information/google-play-information.md index d9d892b9f..bb1f3b6e8 100644 --- a/docs/publish-module/publish-information/google-play-information.md +++ b/docs/publish-module/publish-information/google-play-information.md @@ -1,6 +1,6 @@ --- title: Google Play Console Information -description: Learn how to update App Information in the Publish module of Appcircle for Google Play Console +description: Learn how to update App Information in the Publish to Stores module of Appcircle for Google Play Console tags: [publish, publish module, app information, google play console, review] sidebar_position: 1 --- diff --git a/docs/publish-module/publish-information/history.md b/docs/publish-module/publish-information/history.md index 130582746..1afbba9fe 100644 --- a/docs/publish-module/publish-information/history.md +++ b/docs/publish-module/publish-information/history.md @@ -14,7 +14,7 @@ The History section has two parts: The Publish History and The Resign History. The Publish History section is a record of all the publishing actions that have been performed for different versions of an application. It serves as a log for tracking the deployment lifecycle of each release. -The Resign History section is a record of all the resign actions that have been performed within the Publish module for a specific app version. +The Resign History section is a record of all the resign actions that have been performed within the Publish to Stores module for a specific app version. ## Overview @@ -28,7 +28,7 @@ You can also access the Resign History for an app version by navigating to it's ### Accessing Publish History -To view the Publish History, navigate to the History section in the Publish module. Once History is selected, The Publish History tab will be displayed by default. This section lists all versions of the app along with the dates and times their publishing actions started along with their publish status. +To view the Publish History, navigate to the History section in the Publish to Stores module. Once History is selected, The Publish History tab will be displayed by default. This section lists all versions of the app along with the dates and times their publishing actions started along with their publish status. @@ -67,7 +67,7 @@ The Publish History is a key feature that provides transparency and traceability ### Accessing Build History -To view the Build History, go to the History section for an app version in the Publish module, and then navigate to the Build History tab. +To view the Build History, go to the History section for an app version in the Publish to Stores module, and then navigate to the Build History tab. @@ -79,7 +79,7 @@ Please note that to access the build logs from this tab, the selected binary mus ### Accessing Resign History -To view the Resign History, navigate to the History section in the Publish module, then simply select the Resign History tab. +To view the Resign History, navigate to the History section in the Publish to Stores module, then simply select the Resign History tab. ### Viewing Logs diff --git a/docs/publish-module/publish-information/index.md b/docs/publish-module/publish-information/index.md index 862a04efe..25b989d86 100644 --- a/docs/publish-module/publish-information/index.md +++ b/docs/publish-module/publish-information/index.md @@ -1,6 +1,6 @@ --- title: Publish Information Overview -description: Overview of the Publish module in Appcircle +description: Overview of the Publish to Stores module in Appcircle tags: [publish, publish module, publish information] sidebar_position: 1 --- @@ -10,7 +10,7 @@ import Screenshot from '@site/src/components/Screenshot'; # Publish Information Overview -The Publish module provides users with several key actions to manage their application versions effectively. Below is an overview of each menu item and its function within the system: +The Publish to Stores module provides users with several key actions to manage their application versions effectively. Below is an overview of each menu item and its function within the system: @@ -28,7 +28,7 @@ This option provides an in-depth view of the selected version's publish process. ## [Auto Re-sign](/publish-module/publish-information/auto-resign-configuration) -The **Auto Re-sign** feature in Appcircle’s Publish module allows users to automatically re-sign their iOS (`.ipa`) and Android (`.apk`/`.aab`) applications with a different keystore, provisioning profile, or certificate before distribution. +The **Auto Re-sign** feature in Appcircle’s Publish to Stores module allows users to automatically re-sign their iOS (`.ipa`) and Android (`.apk`/`.aab`) applications with a different keystore, provisioning profile, or certificate before distribution. ## [Google Play Console Information](/publish-module/publish-information/google-play-information) @@ -56,11 +56,11 @@ The History has two sections: The Publish History and The Resign History. The Publish History gives users a chronological log of all publish actions taken for a specific version. It allows users to track and audit the deployment process over time, which can be crucial for compliance, troubleshooting, and historical analysis. -The Resign History gives users a chronological log of all resign actions that was done within the Publish Module for a specific app version. +The Resign History gives users a chronological log of all resign actions that was done within the Publish to Stores Module for a specific app version. ## [Downloading Binaries](/publish-module/publish-information/download) -This functionality enables users to download the binary directly from the Publish module. This is useful for offline review, storage, or distribution purposes. The download feature ensures that users can access and disseminate the application's build even outside the publish platform. +This functionality enables users to download the binary directly from the Publish to Stores module. This is useful for offline review, storage, or distribution purposes. The download feature ensures that users can access and disseminate the application's build even outside the publish platform. ## [Cancel Submission](/publish-module/publish-information/cancel-submission) @@ -72,10 +72,10 @@ Binary rejection on Appcircle can delay your app's launch. Discover the top reas ## [Delete](/publish-module/publish-information/delete) -The Delete option provides a way to remove a version from the system. It should be used with caution as it will permanently eliminate the selected version and all associated data from the Publish module. This feature helps in maintaining a clean and organized workspace by removing obsolete or unnecessary versions. +The Delete option provides a way to remove a version from the system. It should be used with caution as it will permanently eliminate the selected version and all associated data from the Publish to Stores module. This feature helps in maintaining a clean and organized workspace by removing obsolete or unnecessary versions. --- -Each menu item is an integral part of the Publish module, providing comprehensive tools for managing application versions from creation to deployment. Users should familiarize themselves with these options to fully leverage the capabilities of the Publish system. +Each menu item is an integral part of the Publish to Stores module, providing comprehensive tools for managing application versions from creation to deployment. Users should familiarize themselves with these options to fully leverage the capabilities of the Publish system. For further details on each menu item, refer to the corresponding section in this documentation. \ No newline at end of file diff --git a/docs/publish-module/publish-information/meta-data-information.md b/docs/publish-module/publish-information/meta-data-information.md index 7a09fa6c8..c19a1afe6 100644 --- a/docs/publish-module/publish-information/meta-data-information.md +++ b/docs/publish-module/publish-information/meta-data-information.md @@ -113,7 +113,7 @@ If there is existing metadata associated with your app on the Google Play Consol **Updating Android Metadata:** You can easily update your Google Play Console metadata for your app via Appcircle by following these steps: -- Update your app's metadata on Appcircle within the Publish module. +- Update your app's metadata on Appcircle within the Publish to Stores module. - Add the **Update Metadata on Google Play Console** Publish flow step to your workflow. - Run your Publish Flow of your app by selecting the Publish Details under actions menu. diff --git a/docs/publish-module/publish-information/publish-details.md b/docs/publish-module/publish-information/publish-details.md index ca84b2ed6..2cec0f148 100644 --- a/docs/publish-module/publish-information/publish-details.md +++ b/docs/publish-module/publish-information/publish-details.md @@ -10,7 +10,7 @@ sidebar_position: 2 This option provides an in-depth view of the selected version's publish process. Users can review the steps taken, configurations used, and outcomes of the publish sequence. It's an essential resource for understanding the specific details of a version's journey through the publish workflow. +The "Publish Details" feature in the Publish to Stores module provides a comprehensive view of the publish flow for both Android and iOS builds. It is where you can see the progress and logs of your publishing process to different platforms like Google Play Store and TestFlight. --> @@ -20,7 +20,7 @@ To view the details of your publish flow: 1. **Select the Version:** - - Locate and select the build version you want to review in the Publish module. + - Locate and select the build version you want to review in the Publish to Stores module. 2. **Open Publish Details:** diff --git a/docs/publish-module/publish-information/resign-binary.md b/docs/publish-module/publish-information/resign-binary.md index fd3afc625..2baf765be 100644 --- a/docs/publish-module/publish-information/resign-binary.md +++ b/docs/publish-module/publish-information/resign-binary.md @@ -64,7 +64,7 @@ Please note that if the project `info.plist` file does **not** have a `CFBundleD - **Description**: Original Bundle ID. :::caution BundleID -Please note that changing the **BundleID** is allowed while the related version is being re-signed in the **Publish module**. However, you **cannot start** a publish operation unless it matches the Bundle ID defined for the [Publish Profile](/publish-module/creating-publish-profiles#create-profile-manually). +Please note that changing the **BundleID** is allowed while the related version is being re-signed in the **Publish to Stores module**. However, you **cannot start** a publish operation unless it matches the Bundle ID defined for the [Publish Profile](/publish-module/creating-publish-profiles#create-profile-manually). ::: #### Provisioning Profiles @@ -73,7 +73,7 @@ Please note that changing the **BundleID** is allowed while the related version ### Edit Entitlements -With the entitlement editing feature of the Re-sign Binary feature in the Publish module of Appcircle. If you want, you can change your existing entitlements or add or remove them. +With the entitlement editing feature of the Re-sign Binary feature in the Publish to Stores module of Appcircle. If you want, you can change your existing entitlements or add or remove them. @@ -93,7 +93,7 @@ If you want to change, add or remove Entitlement. The **Provision Profile** and To re-sign a binary, follow these steps: -1. **Select the Version**: Choose the version of your app you wish to resign from the **Version List** in the Publish module. +1. **Select the Version**: Choose the version of your app you wish to resign from the **Version List** in the Publish to Stores module. 2. **Configure Re-signing Options**: Navigate to the **Re-sign Binary** action and configure the necessary fields such as the provisioning profile, entitlements, and other settings. 3. **Sign the Binary**: After configuring, click the **Sign** button to re-sign the binary. This process will create a new package with the updated provisioning profile and entitlements. @@ -118,7 +118,7 @@ Re-signing an Android binary allows you to apply a new keystore to your applicat - **Package ID**: This is the unique identifier for your Android application, also known as the application ID. It usually follows the format `com.example.myapp` and should not be changed during the re-signing process. :::caution Package ID -Please note that changing the **Package ID** is not allowed while the related version is being re-signed in the **Publish module**. If you need to change the **Package ID value** of your package, please use the **Re-sign Binary** feature in [Testing Distribution](/testing-distribution/resigning-binaries). +Please note that changing the **Package ID** is not allowed while the related version is being re-signed in the **Publish to Stores module**. If you need to change the **Package ID value** of your package, please use the **Re-sign Binary** feature in [Testing Distribution](/testing-distribution/resigning-binaries). ::: - **Version Name**: This field represents the human-readable version of your app, such as `1.2.3`. It is used for display purposes and can be adjusted if necessary during the re-signing process. diff --git a/docs/publish-module/publish-report/index.md b/docs/publish-module/publish-report/index.md index ac11c300b..4f4defff4 100644 --- a/docs/publish-module/publish-report/index.md +++ b/docs/publish-module/publish-report/index.md @@ -2,7 +2,7 @@ title: Publish Report sidebar_position: 1 tags: [publish, report] -description: Understand the Report for Publish in Appcircle, providing visibility on the usage of publish module over a given time period. +description: Understand the Report for Publish in Appcircle, providing visibility on the usage of Publish to Stores module over a given time period. --- @@ -11,7 +11,7 @@ import CSVExport from '@site/docs/\_csv-export.mdx'; # Publish Report -The Publish Report provides a detailed overview of all actions performed within the Publish Module. It allows users to monitor, filter, and export publish-related activities across different platforms, trigger types, and stores. +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. diff --git a/docs/publish-module/publish-resign-report/index.md b/docs/publish-module/publish-resign-report/index.md index 76275ac25..8c26a47d4 100644 --- a/docs/publish-module/publish-resign-report/index.md +++ b/docs/publish-module/publish-resign-report/index.md @@ -2,7 +2,7 @@ title: Publish Re-sign Report sidebar_position: 1 tags: [publish, report, re-sign] -description: Understand the Report for Publish Re-sign in Appcircle, providing visibility on the usage of re-sign operations within the publish module over a given time period. +description: Understand the Report for Publish Re-sign in Appcircle, providing visibility on the usage of re-sign operations within the Publish to Stores module over a given time period. --- @@ -11,7 +11,7 @@ import CSVExport from '@site/docs/\_csv-export.mdx'; # Publish Re-sign Report -The Publish Re-sign Report provides detailed visibility into the manual and automatic re-sign operations performed within the publish module. This report helps you monitor and analyze re-sign activities across your organization over a selected time period. +The Publish Re-sign Report provides detailed visibility into the manual and automatic re-sign operations performed within the Publish to Stores module. This report helps you monitor and analyze re-sign activities across your organization over a selected time period. @@ -47,7 +47,7 @@ In the filter options, you can only view and select the organization and sub-org ::: :::warning -Please note that the Publish Re-sign Report displays only the re-sign operations that were triggered in the Publish module. +Please note that the Publish Re-sign Report displays only the re-sign operations that were triggered in the Publish to Stores module. ::: \ No newline at end of file diff --git a/docs/publish-module/publish-settings/index.md b/docs/publish-module/publish-settings/index.md index c72a12c7d..2cbea4095 100644 --- a/docs/publish-module/publish-settings/index.md +++ b/docs/publish-module/publish-settings/index.md @@ -9,7 +9,7 @@ tags: [publish settings, publish, settings] import Screenshot from '@site/src/components/Screenshot'; import ContentRef from '@site/src/components/ContentRef'; -When a build is completed on the Build module and its artifacts are distributed to the Publish module, we can start the publish process to the stores using the **Auto Publish** toggle in **Settings**. +When a build is completed on the Build module and its artifacts are distributed to the Publish to Stores module, we can start the publish process to the stores using the **Auto Publish** toggle in **Settings**. Your configured publish flow will be executed automatically when you enable **Auto Publish**. @@ -84,7 +84,7 @@ For detailed information on store connections, follow the links below. :::caution Apple Enterprise API Key -The Apple Enterprise Program is intended solely for in‑house distribution within an organization. Consequently, an Apple Enterprise API Key cannot be used in the Publish module because the Enterprise Program **does not** provide any **App Store Connect** or **TestFlight** infrastructure. +The Apple Enterprise Program is intended solely for in‑house distribution within an organization. Consequently, an Apple Enterprise API Key cannot be used in the Publish to Stores module because the Enterprise Program **does not** provide any **App Store Connect** or **TestFlight** infrastructure. ::: diff --git a/docs/publish-module/publish-variables/index.md b/docs/publish-module/publish-variables/index.md index 48bbcbff7..a8637d968 100644 --- a/docs/publish-module/publish-variables/index.md +++ b/docs/publish-module/publish-variables/index.md @@ -7,7 +7,7 @@ tags: [publish variables, publish, variables] import Screenshot from '@site/src/components/Screenshot'; import ContentRef from '@site/src/components/ContentRef'; -The **Publish Variables** section within the Publish module is a feature that allows you to set up and manage key-value pairs that are essential for the app publishing process. +The **Publish Variables** section within the Publish to Stores module is a feature that allows you to set up and manage key-value pairs that are essential for the app publishing process. @@ -49,7 +49,7 @@ Remember to handle these variables with care, especially if they contain sensiti :::info -Please note that Publish Variables can only be used within the Publish module. +Please note that Publish Variables can only be used within the Publish to Stores module. ::: @@ -259,7 +259,7 @@ User can use `AC_RELEASE_NOTES` environment variable, if the `apk`, `aab` or `ip ### How to change environment variable and exchange it between steps? -In the Appcircle Publish module, the steps within a Publish flow operate independently. This means that each step is executed in a separate, clean runner environment. This feature allows steps to run independently and individually. Therefore, to exchange environment variables between steps, the modified ENV value needs to be saved as an output variable. +In the Appcircle Publish to Stores module, the steps within a Publish flow operate independently. This means that each step is executed in a separate, clean runner environment. This feature allows steps to run independently and individually. Therefore, to exchange environment variables between steps, the modified ENV value needs to be saved as an output variable. Below is an example of how this can be done. Once an ENV variable is modified in a step and saved to the output direction, it will become accessible in another step. diff --git a/docs/publish-module/publish-walkthrough-for-app-store/index.md b/docs/publish-module/publish-walkthrough-for-app-store/index.md index 048bdf59c..084ef9833 100644 --- a/docs/publish-module/publish-walkthrough-for-app-store/index.md +++ b/docs/publish-module/publish-walkthrough-for-app-store/index.md @@ -1,6 +1,6 @@ --- title: Publish Walkthrough for App Store -description: Learn how to use Publish module in Appcircle +description: Learn how to use Publish to Stores module in Appcircle tags: [publish module, benefits, key features, walkthrough, app store connect, app store, release, metadata] --- @@ -10,28 +10,28 @@ import Screenshot from '@site/src/components/Screenshot'; import ContentRef from '@site/src/components/ContentRef'; import NeedHelp from '@site/docs/\_need-help.mdx'; -## Why Use the Publish Module: Features and Benefits +## Why Use the Publish to Stores module: Features and Benefits -The Publish module in Appcircle is a powerful tool designed for managing the release process of mobile applications to various app stores, including the Apple App Store, Google Play, and Huawei AppGallery. This module streamlines the complex process of app release, enabling users to: +The Publish to Stores module in Appcircle is a powerful tool designed for managing the release process of mobile applications to various app stores, including the Apple App Store, Google Play, and Huawei AppGallery. This module streamlines the complex process of app release, enabling users to: - **Centralized Release Management**: Monitor, manage, and audit releases from a single platform, making the release process more efficient and organized. - **Automate Releases**: Automate the submission of applications to multiple stores, reducing the manual workload and minimizing the risk of errors. - **Flexibility in Publishing**: Appcircle provides the flexibility to publish your applications to various platforms, including app stores and internal app distribution systems. This ensures that your application reaches the right audience through the most suitable channels. - **Isolation from Complex Interactions**: Eliminate the need for direct interaction with individual app stores like the App Store, Google Play Console, and Huawei AppGallery. Appcircle acts as a central hub, isolating you from the complexities and variances of each store’s submission processes. -By using the Publish module, you can ensure a smooth, reliable, and scalable release process for your mobile applications, enhancing the overall efficiency and effectiveness of your app release strategy. +By using the Publish to Stores module, you can ensure a smooth, reliable, and scalable release process for your mobile applications, enhancing the overall efficiency and effectiveness of your app release strategy. https://appcircle.io/publish-to-stores ## Getting Started -The Publish module in Appcircle is a versatile tool that simplifies the app release process. To make the most of this module, it's important to ensure that you meet all prerequisites and properly configure the necessary settings. The following sections outline the initial steps to start a release process using the Publish module. +The Publish to Stores module in Appcircle is a versatile tool that simplifies the app release process. To make the most of this module, it's important to ensure that you meet all prerequisites and properly configure the necessary settings. The following sections outline the initial steps to start a release process using the Publish to Stores module. -## Prerequisites for Using the Publish Module +## Prerequisites for Using the Publish to Stores module -Before you can start using the Publish module, there are several key prerequisites to address: +Before you can start using the Publish to Stores module, there are several key prerequisites to address: ### Creating an App Store Connect API Key @@ -75,7 +75,7 @@ Before starting the release process, it's essential to prepare all necessary app :::info Binary -The binary file can be uploaded to the Publish module either manually, through the Build module, or through the Testing Distribution module. For more detailed instructions, please refer to the [**Upload Binary**](/publish-module/publish-walkthrough-for-app-store#uploading-a-binary) section. +The binary file can be uploaded to the Publish to Stores module either manually, through the Build module, or through the Testing Distribution module. For more detailed instructions, please refer to the [**Upload Binary**](/publish-module/publish-walkthrough-for-app-store#uploading-a-binary) section. ::: @@ -117,7 +117,7 @@ To use this profile creation method, you must have an API key integration in pla ### Selecting an App Store API Key -Once the required integrations are set up, you can access these platforms from your profile within the Publish module. To initiate a release process, you need to select the credentials for the related store from the `Settings` screen under the Publish profile. +Once the required integrations are set up, you can access these platforms from your profile within the Publish to Stores module. To initiate a release process, you need to select the credentials for the related store from the `Settings` screen under the Publish profile. @@ -127,7 +127,7 @@ Once the required integrations are set up, you can access these platforms from y ### Updating App Store Connect Information -- Within the Publish module, you can update and review your app's information directly. This includes updating app name, subtitle, categories, and other store-related information such as privacy URLs, primary languages, etc. Please visit the [**App Store Connect Information**](/publish-module/publish-information/app-information) documentation for detailed information. +- Within the Publish to Stores module, you can update and review your app's information directly. This includes updating app name, subtitle, categories, and other store-related information such as privacy URLs, primary languages, etc. Please visit the [**App Store Connect Information**](/publish-module/publish-information/app-information) documentation for detailed information. @@ -135,7 +135,7 @@ Once the required integrations are set up, you can access these platforms from y ### Updating TestFlight Beta Information -- Within the Publish module, you can update and review your **TestFlight Beta Information** directly. This includes editing the description, feedback email, beta app review details, and other store-related information such as privacy URLs, etc. +- Within the Publish to Stores module, you can update and review your **TestFlight Beta Information** directly. This includes editing the description, feedback email, beta app review details, and other store-related information such as privacy URLs, etc. @@ -143,7 +143,7 @@ Once the required integrations are set up, you can access these platforms from y ### Customizing the Publish Flow -Publish flow is used to automate multiple tasks and introduce automation checkpoints for application publishing to stores. You can create and manage flows within the Publish module as outlined below: +Publish flow is used to automate multiple tasks and introduce automation checkpoints for application publishing to stores. You can create and manage flows within the Publish to Stores module as outlined below: @@ -172,11 +172,11 @@ You can back up your current Publish flow by clicking the `Download YAML` button ### Publish Flow Sample -The Publish module is designed to cater to a wide range of needs, making it suitable for both enterprise-level companies and individual developers. Here is an example of a custom flow you might create: +The Publish to Stores module is designed to cater to a wide range of needs, making it suitable for both enterprise-level companies and individual developers. Here is an example of a custom flow you might create: #### Beta Testing and Release Flow -With the Appcircle Publish module, you can manage your entire release process from scratch without needing to access the developer interfaces of the app stores. Below is an example flow that demonstrates how to manage a release process including testing from start to finish. The steps are utilized in the following order: +With the Appcircle Publish to Stores module, you can manage your entire release process from scratch without needing to access the developer interfaces of the app stores. Below is an example flow that demonstrates how to manage a release process including testing from start to finish. The steps are utilized in the following order: - [**App Information from App Store**](/publish-integrations/ios-publish-integrations/app-information-app-store): This step compares the Release Candidate version with the latest versions in both the TestFlight and Production environments, giving you an idea of how the release process will begin. - [**Get Approval via Email**](/publish-integrations/common-publish-integrations/get-approval-via-email): After the version comparison is completed, an approval email is sent to the Release Manager to decide whether or not to proceed with the release process. This email informs the Release Manager about the release that is set to go to Beta Test. If the Release Manager sees no issues, they can click the Approve link within the email to move the process forward. @@ -192,7 +192,7 @@ With the Appcircle Publish module, you can manage your entire release process fr ### Setting Up Notifications -- Keeping your team informed about the release progress is essential for a coordinated effort. The Publish module can be integrated with collaboration tools like [**Slack**](/account/my-organization/notifications/slack-notifications) or [**Microsoft Teams**](/account/my-organization/notifications/teams-notifications) for notifications. By setting up these integrations, you can automatically send notifications about key events in the release process—such as successful publishing or issues that need attention—ensuring that everyone stays in the loop and can act swiftly when needed. Please visit the related [**Notifications Integration**](/account/my-organization/notifications) documentation for more detailed information. +- Keeping your team informed about the release progress is essential for a coordinated effort. The Publish to Stores module can be integrated with collaboration tools like [**Slack**](/account/my-organization/notifications/slack-notifications) or [**Microsoft Teams**](/account/my-organization/notifications/teams-notifications) for notifications. By setting up these integrations, you can automatically send notifications about key events in the release process—such as successful publishing or issues that need attention—ensuring that everyone stays in the loop and can act swiftly when needed. Please visit the related [**Notifications Integration**](/account/my-organization/notifications) documentation for more detailed information. @@ -200,23 +200,23 @@ With the Appcircle Publish module, you can manage your entire release process fr ## Managing Releases -Effective release management is crucial for ensuring the success of your app updates. The Publish module provides you with the tools to monitor, control, and optimize the release process. You can track the status of your releases in real-time, manage approvals, and address any issues that arise during the process. Also, the Publish module offers customizable flows to provide more detailed management of the release process. +Effective release management is crucial for ensuring the success of your app updates. The Publish to Stores module provides you with the tools to monitor, control, and optimize the release process. You can track the status of your releases in real-time, manage approvals, and address any issues that arise during the process. Also, the Publish to Stores module offers customizable flows to provide more detailed management of the release process. Additionally, the module allows you to roll back to previous versions if needed, ensuring that you have full control over your app's distribution. By leveraging these features, you can maintain a smooth and efficient release cycle, minimizing disruptions and maximizing the impact of your updates. ### Uploading a Binary -Easily upload your binary file to the Publish module **manually**, via the **Build** or **Testing Distribution** modules, or through **Appcircle CLI and API** to begin the release process. +Easily upload your binary file to the Publish to Stores module **manually**, via the **Build** or **Testing Distribution** modules, or through **Appcircle CLI and API** to begin the release process. #### Manual Binary Upload -You can upload your binary file directly to the Publish module using the manual upload option. +You can upload your binary file directly to the Publish to Stores module using the manual upload option. #### Uploading via Build Module -You can deploy your binary file to the Publish module from the Build module automatically. This method automates the binary publish process, ensuring that your binary is transferred directly from the Build pipeline to the Publish module, ready for release. It simplifies the flows and reduces the risk of manual errors. +You can deploy your binary file to the Publish to Stores module from the Build module automatically. This method automates the binary publish process, ensuring that your binary is transferred directly from the Build pipeline to the Publish to Stores module, ready for release. It simplifies the flows and reduces the risk of manual errors. :::info Uploading via Build Module @@ -226,7 +226,7 @@ To upload a binary from the Build module, please refer to the [**Distribution Co #### Uploading via Testing Distribution Module -You can send your binary file to the Publish module from the Testing Distribution module. +You can send your binary file to the Publish to Stores module from the Testing Distribution module. @@ -240,7 +240,7 @@ To upload a binary from the Testing Distribution module, please refer to the [** If you have your own CI environment, you can use the Appcircle API & CLI to upload binaries to the related publish Profile. -- **Other CI/CD Tools**: You can integrate the Publish module with continuous integration/continuous deployment (CI/CD) tools like Jenkins and GitHub Actions to automate your build and release pipeline. With the Appcircle [**API & CLI**](/appcircle-api-and-cli), you can seamlessly connect these tools, allowing for automated triggers that initiate a release as soon as a new build is ready. This integration ensures a consistent and efficient publish process, reducing manual intervention and the risk of errors. You can check out [**Appcircle Marketplace**](/marketplace) for more integrations. +- **Other CI/CD Tools**: You can integrate the Publish to Stores module with continuous integration/continuous deployment (CI/CD) tools like Jenkins and GitHub Actions to automate your build and release pipeline. With the Appcircle [**API & CLI**](/appcircle-api-and-cli), you can seamlessly connect these tools, allowing for automated triggers that initiate a release as soon as a new build is ready. This integration ensures a consistent and efficient publish process, reducing manual intervention and the risk of errors. You can check out [**Appcircle Marketplace**](/marketplace) for more integrations. To get more information, please refer to our [**API & CLI**](/appcircle-api-and-cli) documentation. @@ -254,7 +254,7 @@ To get more information, please refer to our [**API & CLI**](/appcircle-api-and- ### Updating Metadata -- Within the Publish module, you can manage your app's metadata directly. This includes updating app descriptions, keywords, and other store-related information. Please visit the [**Metadata Details**](/publish-module/publish-information/meta-data-information) documentation for more information. +- Within the Publish to Stores module, you can manage your app's metadata directly. This includes updating app descriptions, keywords, and other store-related information. Please visit the [**Metadata Details**](/publish-module/publish-information/meta-data-information) documentation for more information. @@ -275,7 +275,7 @@ step to get approval before submitting the metadata to App Store Connect. ### Managing Release Status -After initiating a release, the Publish module provides tools to monitor and manage the process: +After initiating a release, the Publish to Stores module provides tools to monitor and manage the process: #### Release Dashboard @@ -304,20 +304,20 @@ If needed, you can rollback to a previous version of your app or pause a release ### Auditing Releases -The Publish module provides comprehensive auditing and reporting features that give you full visibility into your release process. +The Publish to Stores module provides comprehensive auditing and reporting features that give you full visibility into your release process. - **Activity Log**: The Activity Log keeps a detailed record of every action taken during the release process, including who performed each action and when it occurred. This log is invaluable for tracking changes, identifying issues, and ensuring accountability within your team. -## Publish Module Troubleshooting +## Publish to Stores module Troubleshooting -When using the Publish module, it's essential to know how to troubleshoot potential issues that may arise during the release process. Whether you're dealing with failed submissions, integration errors, or flow execution problems, having a clear understanding of common issues and their solutions can save you time and ensure a smooth release. +When using the Publish to Stores module, it's essential to know how to troubleshoot potential issues that may arise during the release process. Whether you're dealing with failed submissions, integration errors, or flow execution problems, having a clear understanding of common issues and their solutions can save you time and ensure a smooth release. ### Common Issues and Solutions -While the Publish module is designed for reliability, you may occasionally encounter issues due to various reasons. Here are some common problems and their solutions: +While the Publish to Stores module is designed for reliability, you may occasionally encounter issues due to various reasons. Here are some common problems and their solutions: - **Failed Submissions**: Submissions can fail for various reasons. One common issue is a conflicting version number—if the version you're trying to submit already exists on the store, you'll need to increment the version number. Another issue could be an invalid binary, which might occur if the app doesn’t meet store requirements, have technical issues or if there are missing assets. Always check the error logs for specific details, correct any issues, and attempt the submission again. @@ -325,11 +325,11 @@ While the Publish module is designed for reliability, you may occasionally encou - **Flow Execution Problems**: If a flow doesn't execute as expected, it might be due to incorrect configuration settings. Review each step of the flow to ensure everything is set up correctly, such as conditions, triggers, and action sequences. If the problem persists, try testing the flow in a staging environment to isolate the issue before rerunning it in production. -### Frequently Asked Questions About the Publish Module +### Frequently Asked Questions About the Publish to Stores module #### How do I update my app's metadata? -To update your app's metadata, navigate to the Publish module, select the relevant profile, click the Actions button for the binary, and go to Metadata details. You can now update the metadata fields such as the app name, description, and screenshots. After saving your changes, submit the updated metadata for review if required. +To update your app's metadata, navigate to the Publish to Stores module, select the relevant profile, click the Actions button for the binary, and go to Metadata details. You can now update the metadata fields such as the app name, description, and screenshots. After saving your changes, submit the updated metadata for review if required. @@ -342,13 +342,13 @@ feedback in case of rejection. #### Is it possible to automate notifications for team members during the release process? -Yes, it is possible. The Publish module allows you to set up automated notifications for your team members at various stages of the release process. You can configure notifications to be sent via email or integrate with collaboration tools like Slack or Microsoft Teams, ensuring that everyone involved is kept up to date on the release status. +Yes, it is possible. The Publish to Stores module allows you to set up automated notifications for your team members at various stages of the release process. You can configure notifications to be sent via email or integrate with collaboration tools like Slack or Microsoft Teams, ensuring that everyone involved is kept up to date on the release status. For more information, please refer to the [**Notification Integrations**](/account/my-organization/notifications) document. #### Can I track the progress of the app release in real-time? -Yes, the Publish module provides real-time tracking of the app release process. You can monitor each step of the flow, view the status of your submission, and receive notifications about any changes or issues. This feature allows you to stay informed and take action immediately if necessary. +Yes, the Publish to Stores module provides real-time tracking of the app release process. You can monitor each step of the flow, view the status of your submission, and receive notifications about any changes or issues. This feature allows you to stay informed and take action immediately if necessary. @@ -358,43 +358,43 @@ If your binary is rejected by Apple in App Store Connect, the status on Appcircl -#### Can I use the Publish Module with other CI tools? +#### Can I use the Publish to Stores Module with other CI tools? -Yes, you can use other CI tools to upload a binary to the Publish module. By utilizing Appcircle [**API & CLI**](/appcircle-api-and-cli) within your chosen CI tool, you can directly send the binary to the relevant profile and manage the Publish process. +Yes, you can use other CI tools to upload a binary to the Publish to Stores module. By utilizing Appcircle [**API & CLI**](/appcircle-api-and-cli) within your chosen CI tool, you can directly send the binary to the relevant profile and manage the Publish process. Additionally, you can check our existing integrations in the [**Appcircle Marketplace**](/marketplace) documentation for integration alternatives for the **Appcircle API and CLI**. -#### Can I manage the team members roles for Publish Module? +#### Can I manage the team members roles for Publish to Stores Module? Appcircle provides users with a comprehensive role management system. This system allows you to assign specific permissions to all organization members on an organization-wide basis. For more information, please refer to the [**Role Management**](/account/my-organization/profile-and-team/role-management) document. -#### Can I manage multiple app store accounts within the Publish module? +#### Can I manage multiple app store accounts within the Publish to Stores module? -Yes, the Publish module allows you to manage multiple app store accounts within a single interface. You can set up and integrate different accounts, such as Apple App Store, Google Play, and Huawei AppGallery, and then select the appropriate account during the release process. This flexibility ensures that you can handle releases across multiple platforms efficiently. +Yes, the Publish to Stores module allows you to manage multiple app store accounts within a single interface. You can set up and integrate different accounts, such as Apple App Store, Google Play, and Huawei AppGallery, and then select the appropriate account during the release process. This flexibility ensures that you can handle releases across multiple platforms efficiently. -#### How do I create a custom flow in the Publish Module? +#### How do I create a custom flow in the Publish to Stores Module? -To create a custom flow, navigate to the Publish module and select the "Publish Flow" option. From there, you can choose and arrange the steps needed for your release process, configure each step according to your requirements, and save the flow for future use. Custom flow allows you to tailor the release process to fit your specific needs. +To create a custom flow, navigate to the Publish to Stores module and select the "Publish Flow" option. From there, you can choose and arrange the steps needed for your release process, configure each step according to your requirements, and save the flow for future use. Custom flow allows you to tailor the release process to fit your specific needs. #### Why can't I edit the Publish Flow? -The Publish module is an **enterprise-level** solution, so only users with an **Appcircle Enterprise Licence** have access to all of its features. Users with other licences have limited access to the module. To get more information for Enterprise Licence please [**contact us**](https://appcircle.io/contact) directly. +The Publish to Stores module is an **enterprise-level** solution, so only users with an **Appcircle Enterprise Licence** have access to all of its features. Users with other licences have limited access to the module. To get more information for Enterprise Licence please [**contact us**](https://appcircle.io/contact) directly. #### How can I roll back to a previous version if needed? -If you need to roll back to a previous version, you can do so by selecting the desired version from your release history within the Publish module. This process involves re-uploading the previous binary and metadata, then executing a flow to re-release that version. Rolling back ensures that you can quickly address any issues with the current release without significant downtime. +If you need to roll back to a previous version, you can do so by selecting the desired version from your release history within the Publish to Stores module. This process involves re-uploading the previous binary and metadata, then executing a flow to re-release that version. Rolling back ensures that you can quickly address any issues with the current release without significant downtime. ### Further Support and Resources -If you need additional help with the Publish module, the following resources are available: +If you need additional help with the Publish to Stores module, the following resources are available: -- **Technical Documentation**: Refer to the Appcircle user documentation for detailed guides and troubleshooting tips for the Publish module. +- **Technical Documentation**: Refer to the Appcircle user documentation for detailed guides and troubleshooting tips for the Publish to Stores module. -- **Commercial Details**: The Publish module is an **enterprise-level** solution; therefore, for commercial details, please [**contact us**](https://appcircle.io/contact) directly. +- **Commercial Details**: The Publish to Stores module is an **enterprise-level** solution; therefore, for commercial details, please [**contact us**](https://appcircle.io/contact) directly. diff --git a/docs/publish-module/publish-walkthrough-for-google-play/index.md b/docs/publish-module/publish-walkthrough-for-google-play/index.md index 893b73358..7d118c9f8 100644 --- a/docs/publish-module/publish-walkthrough-for-google-play/index.md +++ b/docs/publish-module/publish-walkthrough-for-google-play/index.md @@ -1,6 +1,6 @@ --- title: Publish Walkthrough for Google Play Console -description: Learn how to automate app publishing to Google Play Console using the Publish module. +description: Learn how to automate app publishing to Google Play Console using the Publish to Stores module. tags: [publish, google play console, android, metadata, walkthrough, android app release] --- @@ -8,28 +8,28 @@ import Screenshot from '@site/src/components/Screenshot'; import ContentRef from '@site/src/components/ContentRef'; import NeedHelp from '@site/docs/\_need-help.mdx'; -## Why Use the Publish Module: Features and Benefits +## Why Use the Publish to Stores module: Features and Benefits -The Publish module in Appcircle is a powerful tool designed for managing the release process of mobile applications to various app stores, including the Apple App Store, Google Play Console, and Huawei AppGallery. This module streamlines the complex process of app release, enabling users to: +The Publish to Stores module in Appcircle is a powerful tool designed for managing the release process of mobile applications to various app stores, including the Apple App Store, Google Play Console, and Huawei AppGallery. This module streamlines the complex process of app release, enabling users to: - **Centralized Release Management**: Monitor, manage, and audit releases from a single platform, making the release process more efficient and organized. - **Automate Releases**: Automate the submission of applications to multiple stores, reducing the manual workload and minimizing the risk of errors. - **Flexibility in Publishing**: Appcircle provides the flexibility to publish your applications to various platforms, including app stores and internal app distribution systems. This ensures that your applications reaches the right audience through the most suitable channels. - **Isolation from Complex Interactions**: Eliminate the need for direct interaction with individual app stores like the Apple App Store, Google Play Console, and Huawei AppGallery. Appcircle acts as a central hub, isolating you from the complexities and variances of each store’s submission processes. -By using the Publish module, you can ensure a smooth, reliable, and scalable release process for your mobile applications, enhancing the overall efficiency and effectiveness of your app release strategy. +By using the Publish to Stores module, you can ensure a smooth, reliable, and scalable release process for your mobile applications, enhancing the overall efficiency and effectiveness of your app release strategy. https://appcircle.io/publish-to-stores ## Getting Started -The Publish module in Appcircle is a versatile tool that simplifies the app release process. To make the most of this module, it's important to ensure that you meet all prerequisites and properly configure the necessary settings. The following sections outline the initial steps to start a release process using the Publish module. +The Publish to Stores module in Appcircle is a versatile tool that simplifies the app release process. To make the most of this module, it's important to ensure that you meet all prerequisites and properly configure the necessary settings. The following sections outline the initial steps to start a release process using the Publish to Stores module. -## Prerequisites for Using the Publish Module +## Prerequisites for Using the Publish to Stores module -Before you can start using the Publish module, there are several key prerequisites to address: +Before you can start using the Publish to Stores module, there are several key prerequisites to address: ### Creating and Adding a Google Play Developer API Key @@ -52,7 +52,7 @@ Before starting the release process, make sure your AAB or APK binary is properl :::info Binary Upload Methods -The binary file can be uploaded to the Publish module either manually or through the Build or Testing Distribution modules. For more detailed instructions, please refer to the [**Upload Binary**](/publish-module/publish-walkthrough-for-google-play#uploading-a-binary) section. +The binary file can be uploaded to the Publish to Stores module either manually or through the Build or Testing Distribution modules. For more detailed instructions, please refer to the [**Upload Binary**](/publish-module/publish-walkthrough-for-google-play#uploading-a-binary) section. ::: @@ -82,7 +82,7 @@ To use this profile creation method, you must have a Google Play API key integra ### Selecting a Google Play Developer API Key -If you choose to create the profile manually, you must select the required Google Play Developer API key integration from your profile in the Publish module after the profile is created. To initiate the release process, select the credentials for the relevant store from the `Settings` screen under the selected Publish profile. +If you choose to create the profile manually, you must select the required Google Play Developer API key integration from your profile in the Publish to Stores module after the profile is created. To initiate the release process, select the credentials for the relevant store from the `Settings` screen under the selected Publish profile. @@ -92,7 +92,7 @@ If you choose to create the profile manually, you must select the required Googl ### Updating Google Play Console App Information -- Within the Publish module, you can update and review your app's information directly. This includes updating email address, phone number, website URL, primary languages, and auto-send for review options. Please visit the [**Google Play Console Information**](/publish-module/publish-information/google-play-information) documentation for detailed information. +- Within the Publish to Stores module, you can update and review your app's information directly. This includes updating email address, phone number, website URL, primary languages, and auto-send for review options. Please visit the [**Google Play Console Information**](/publish-module/publish-information/google-play-information) documentation for detailed information. @@ -100,7 +100,7 @@ If you choose to create the profile manually, you must select the required Googl ### Customizing the Publish Flow -Publish flow is used to automate multiple tasks and introduce automation checkpoints for application deployments to stores. You can manage flow within the Publish module as outlined below: +Publish flow is used to automate multiple tasks and introduce automation checkpoints for application deployments to stores. You can manage flow within the Publish to Stores module as outlined below: @@ -148,7 +148,7 @@ You can select one of the following options: ### Setting Up Notifications -- Keeping your team informed about the release progress is essential for a coordinated effort. The Publish module can be integrated with collaboration tools like [**Slack**](/account/my-organization/notifications/slack-notifications) or [**Microsoft Teams**](/account/my-organization/notifications/teams-notifications) for notifications. By setting up these integrations, you can automatically send notifications about key events in the release process—such as successful deployments or issues that need attention—ensuring that everyone stays in the loop and can act swiftly when needed. Please visit the related [**Notifications Integration**](/account/my-organization/notifications) documentation for more detailed information. +- Keeping your team informed about the release progress is essential for a coordinated effort. The Publish to Stores module can be integrated with collaboration tools like [**Slack**](/account/my-organization/notifications/slack-notifications) or [**Microsoft Teams**](/account/my-organization/notifications/teams-notifications) for notifications. By setting up these integrations, you can automatically send notifications about key events in the release process—such as successful deployments or issues that need attention—ensuring that everyone stays in the loop and can act swiftly when needed. Please visit the related [**Notifications Integration**](/account/my-organization/notifications) documentation for more detailed information. @@ -156,21 +156,21 @@ You can select one of the following options: ## Managing Releases -Effective release management is crucial for ensuring the success of your app updates. The Publish module provides you with the tools to monitor, control, and optimize the release process. You can track the status of your releases in real time, manage approvals, and address any issues that arise during the process. Also, the Publish module offers customizable flow to provide more detailed management of the release process. +Effective release management is crucial for ensuring the success of your app updates. The Publish to Stores module provides you with the tools to monitor, control, and optimize the release process. You can track the status of your releases in real time, manage approvals, and address any issues that arise during the process. Also, the Publish to Stores module offers customizable flow to provide more detailed management of the release process. ### Uploading a Binary -Easily upload your binary file to the Publish module **manually**, via the **Build** or **Testing Distribution** modules, or through **Appcircle CLI and API** to begin the release process. +Easily upload your binary file to the Publish to Stores module **manually**, via the **Build** or **Testing Distribution** modules, or through **Appcircle CLI and API** to begin the release process. #### Manual Binary Upload -You can upload your binary file directly to the Publish module using the manual upload option. +You can upload your binary file directly to the Publish to Stores module using the manual upload option. #### Upload via Build Module -You can automatically deploy your binary file to the Publish module directly from the Build module. This method streamlines the binary deployment process by transferring your binary immediately after the build pipeline completes, making it ready for release. It simplifies the flow and reduces the risk of manual errors. +You can automatically deploy your binary file to the Publish to Stores module directly from the Build module. This method streamlines the binary deployment process by transferring your binary immediately after the build pipeline completes, making it ready for release. It simplifies the flow and reduces the risk of manual errors. :::info Upload via Build Module @@ -188,7 +188,7 @@ You can send your application from a testing distribution profile to a designate If you have your own CI environment or need to integrate Appcircle into a specific process or job, you can use the Appcircle API & CLI to upload binaries to the related Publish profile. -- **Other CI/CD Tools**: You can integrate the Publish module with CI/CD tools like Jenkins and GitHub Actions to automate your build and release pipeline. With the Appcircle [**API & CLI**](/appcircle-api-and-cli), you can seamlessly connect these tools, allowing for automated triggers that initiate a release as soon as a new build is ready. This integration ensures a consistent and efficient deployment process, reducing manual intervention and the risk of errors. You can check out [**Appcircle Marketplace**](/marketplace) for more integrations. +- **Other CI/CD Tools**: You can integrate the Publish to Stores module with CI/CD tools like Jenkins and GitHub Actions to automate your build and release pipeline. With the Appcircle [**API & CLI**](/appcircle-api-and-cli), you can seamlessly connect these tools, allowing for automated triggers that initiate a release as soon as a new build is ready. This integration ensures a consistent and efficient deployment process, reducing manual intervention and the risk of errors. You can check out [**Appcircle Marketplace**](/marketplace) for more integrations. To get more information, please refer to our [**API & CLI**](/appcircle-api-and-cli) documentation. @@ -202,7 +202,7 @@ To get more information, please refer to our [**API & CLI**](/appcircle-api-and- ### Updating Metadata -- Within the Publish module, you can directly manage your app’s metadata. This includes editing the screenshots, video, app name, and descriptions. Please visit the [**Metadata Details**](/publish-module/publish-information/meta-data-information#android-metadata-information) documentation for more information. +- Within the Publish to Stores module, you can directly manage your app’s metadata. This includes editing the screenshots, video, app name, and descriptions. Please visit the [**Metadata Details**](/publish-module/publish-information/meta-data-information#android-metadata-information) documentation for more information. @@ -220,7 +220,7 @@ To get more information, please refer to our [**API & CLI**](/appcircle-api-and- ### Managing Release Status -After initiating a release, the Publish module provides tools to monitor and manage the process. +After initiating a release, the Publish to Stores module provides tools to monitor and manage the process. #### Release Dashboard @@ -240,15 +240,15 @@ View the real time status of your release. ### Auditing Releases -The Publish module provides comprehensive auditing and reporting features that give you full visibility into your release process. +The Publish to Stores module provides comprehensive auditing and reporting features that give you full visibility into your release process. - **Activity Log**: The activity log keeps a detailed record of every action taken during the release process, including who performed each action and when it occurred. This log is invaluable for tracking changes, identifying issues, and ensuring accountability within your team. -## Publish Module Troubleshooting +## Publish to Stores module Troubleshooting -When using the Publish module, it's essential to know how to troubleshoot potential issues that may arise during the release process. Whether you're dealing with failed submissions, integration errors, or flow execution problems, having a clear understanding of common issues and their solutions can save you time and ensure a smooth release. +When using the Publish to Stores module, it's essential to know how to troubleshoot potential issues that may arise during the release process. Whether you're dealing with failed submissions, integration errors, or flow execution problems, having a clear understanding of common issues and their solutions can save you time and ensure a smooth release. ### Frequently Asked Questions About the Publish Module diff --git a/docs/release-notes.md b/docs/release-notes.md index 684d84b6c..9839c8780 100644 --- a/docs/release-notes.md +++ b/docs/release-notes.md @@ -29,7 +29,7 @@ import RedisDomainCaution from '@site/docs/self-hosted-appcircle/install-server/ - CodePush activities are now displayed in the Build Activity Log. - Overall UI and stability improvements have been made to the Account page. - Re-sign notifications are now displayed under the corresponding module’s notifications. -- The Publish module has been renamed to Publish to Stores. +- The Publish to Stores module has been renamed to Publish to Stores. ### 🐞 Fixes diff --git a/docs/testing-distribution/create-or-select-a-distribution-profile.md b/docs/testing-distribution/create-or-select-a-distribution-profile.md index 57d904f5d..f69231c81 100644 --- a/docs/testing-distribution/create-or-select-a-distribution-profile.md +++ b/docs/testing-distribution/create-or-select-a-distribution-profile.md @@ -471,7 +471,7 @@ You can send your application from your Testing Distribution profile to a design :::caution -You must have already created the designated Publish profile within the Publish Module, and it should correspond to the operating system of your application (Android or iOS) listed in your Testing Distribution Profile. +You must have already created the designated Publish profile within the Publish to Stores module, and it should correspond to the operating system of your application (Android or iOS) listed in your Testing Distribution Profile. ::: From a82915747ab179bb67936d920c74e71ad21cc9e8 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Sarp=20Bak=C4=B1=C5=9F?= Date: Mon, 10 Nov 2025 11:42:03 +0300 Subject: [PATCH 2/2] patch release notes --- docs/release-notes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/release-notes.md b/docs/release-notes.md index 2a2a13f2f..3e2f97d99 100644 --- a/docs/release-notes.md +++ b/docs/release-notes.md @@ -186,7 +186,7 @@ You cannot upgrade directly from `3.28.3` or an older version to `3.29.3` or lat ### :muscle: Improvements -- An update was made for [Publish iOS](/account/my-organization/profile-and-team/role-management#publish-module-ios-permissions) and [Publish Android](/account/my-organization/profile-and-team/role-management#publish-module-android-permissions) operator roles, and access to Publish Flow settings was removed for them. +- An update was made for [Publish iOS](/account/my-organization/profile-and-team/role-management#publish-to-stores-ios-permissions) and [Publish Android](/account/my-organization/profile-and-team/role-management#publish-to-stores-android-permissions) operator roles, and access to Publish Flow settings was removed for them. - The “Create from existing SSO settings” option was disabled for SAML-type SSO configurations. - The exact renewal time is now shown next to the expiry date on the billing page. - Auto Re-sign operations will now be specifically mentioned as Auto Re-sign within notifications sent via Email, Teams, and Slack.