@@ -45,6 +45,17 @@ These features make the Appcircle Enterprise Mobile App Store a powerful tool
4545for securely and efficiently distributing in-house applications, offering
4646flexibility, enhanced security, and a streamlined workflow.
4747
48+ ### System Requirements
49+
50+ ** Compatible Agents:**
51+
52+ - macOS
53+ - Ubuntu
54+ - Ventura
55+
56+ Note: We currently support ** Appcircle Cloud** , with ** self-hosted** support
57+ planned in our roadmap.
58+
4859![ Enterprise App Store Dashboard] ( images/ent_app_store.png )
4960
5061### Generating/Managing the Personal API Tokens
@@ -60,18 +71,34 @@ To generate a Personal API Token:
6071## How to use Appcircle Enterprise Store Action
6172
6273``` yml
63- - name : Publish App to Appcircle
64- id : store-publish-appcircle
65- uses : ./
74+ - name : Publish App to Appcircle Enterprise App Store
75+ id : store-publish-to- appcircle
76+ uses : appcircleio/appcircle-enterprise-app-store-githubaction
6677 with :
67- accessToken : ${{ secrets.AC_ACCESS_TOKEN }}
68- entProfileId : ${{ secrets.AC_PROFILE_ID }}
69- appPath : ./Appcircle.ipa
70- summary : Github Action Summary
71- releaseNotes : Github Action Release Notes
72- publishType : ' 1' # None: 0, 1: Beta, 2: Live
78+ personalAPIToken : ${{ secrets.AC_PERSONAL_API_TOKEN }}
79+ appPath : APP_PATH
80+ summary : SUMMARY
81+ releaseNotes : RELEASE_NOTES
82+ publishType : PUBLISH_TYPE # "0": None, "1": Beta, "2": Live
7383` ` `
7484
85+ - ` personalAPIToken`: The Appcircle Personal API token is utilized to
86+ authenticate and secure access to Appcircle services, ensuring that only
87+ authorized users can perform actions within the platform.
88+ - `appPath` : Indicates the file path to the application that will be uploaded to
89+ Appcircle Testing Distribution Profile.
90+ - `releaseNote` : Contains the details of changes, updates, and improvements made
91+ in the current version of the app being published.
92+ - `Summary` : Used to provide a brief overview of the version of the app that is
93+ about to be published.
94+ - `publishType` : Specifies the publishing status as either none, beta, or live,
95+ and must be assigned the values "0", "1", or "2" accordingly.
96+
97+ **If two builds start simultaneously, such as v1.0.5(5) and v1.0.5(5), for the
98+ same publishType, the build that finishes last will result in failure because
99+ the same version cannot be added, while the first build to complete will be
100+ successfully uploaded and published.**
101+
75102# ## Leveraging Environment Variables
76103
77104Utilize environment variables seamlessly by substituting the parameters with
0 commit comments