Skip to content

Commit 594ead1

Browse files
committed
Refine steps for downloading AAB file and uploading to internal testing track
1 parent cf3335e commit 594ead1

File tree

1 file changed

+43
-12
lines changed

1 file changed

+43
-12
lines changed

docs/test-and-publish/publish/google-playstore-deployment.md

Lines changed: 43 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -169,21 +169,18 @@ To upload your service account credentials in Dreamflow, go to **Publish > Andro
169169

170170
For first-time deployment, you need to create an initial release manually in Google Play Console. After that, Dreamflow can handle all subsequent deployments.
171171

172-
### 4.1 First-time setup
172+
### 4.1 Downloading AAB file
173173

174-
1. In Dreamflow, set the **Google Play Track** to **Internal**.
175-
2. Specify the **Bundle ID** and **Version Code** and then click **Submit Build to Google Play**.
176-
3. Once the build is complete, download the [**.aab**](https://chatgpt.com/share/6f5714c1-eb13-428b-b9ee-9772f2810284) file.
177-
4. In Google Play Console, create an **Internal Testing** track and upload the **.aab** file.
174+
In DreamFlow, set the **Google Play Track** to **Internal**, enter the **Bundle ID** and **Version Code**, then click **Submit Build to Google Play**. Wait a few minutes and click **Check Deployment Status**.
175+
176+
Once the build is complete, click **Download AAB File** button (in the **App Bundle** section). If the button is still disabled, wait a bit longer and try again.
178177

179178
:::info
180179

181-
- After the internal testing track is set up, Dreamflow can handle all future deployments directly.
182-
- Even if the build status appears as FAILURE, you can still download the AAB file.
180+
Even if the build status appears as FAILURE, you can still download the AAB file.
183181

184182
:::
185183

186-
187184
<div style={{
188185
position: 'relative',
189186
paddingBottom: 'calc(50.67989417989418% + 41px)', // Keeps the aspect ratio and additional padding
@@ -210,7 +207,41 @@ For first-time deployment, you need to create an initial release manually in Goo
210207
</div>
211208
<p></p>
212209

213-
### 4.2 Deploy from Dreamflow
210+
### 4.2 Upload AAB file to Internal testing track
211+
212+
In Google Play Console, create an **Internal Testing** track and upload the **.aab** file.
213+
214+
<div style={{
215+
position: 'relative',
216+
paddingBottom: 'calc(50.67989417989418% + 41px)', // Keeps the aspect ratio and additional padding
217+
height: 0,
218+
width: '100%'}}>
219+
<iframe
220+
src="https://demo.arcade.software/PJt1oXAVn7Wpvjb6zYCb?embed&show_copy_link=true"
221+
title=""
222+
style={{
223+
position: 'absolute',
224+
top: 0,
225+
left: 0,
226+
width: '100%',
227+
height: '100%',
228+
colorScheme: 'light'
229+
}}
230+
frameborder="0"
231+
loading="lazy"
232+
webkitAllowFullScreen
233+
mozAllowFullScreen
234+
allowFullScreen
235+
allow="clipboard-write">
236+
</iframe>
237+
</div>
238+
<p></p>
239+
240+
:::info
241+
After the internal testing track is set up, DreamFlow can handle all future deployments directly.
242+
:::
243+
244+
### 4.3 Deploy from Dreamflow
214245

215246
To deploy your app from Dreamflow, navigate to **Publish > Android**, set the **Track** to Internal, and update the **version code.** If your app is still in draft mode (not yet available on the Play Store), set **Submit as Draft** (under **Deployment Flags)** to **True**, and then click **Deploy to Play Store**.
216247

@@ -247,7 +278,7 @@ To deploy your app from Dreamflow, navigate to **Publish > Android**, set the **
247278

248279
:::
249280

250-
### 4.3 Verify deployment
281+
### 4.4 Verify deployment
251282

252283
To verify that the app is deployed to Play Console:
253284

@@ -257,7 +288,7 @@ To verify that the app is deployed to Play Console:
257288

258289
![verify-deployment.avif](imgs/verify-deployment.avif)
259290

260-
### 4.4 Deploy to production
291+
### 4.5 Deploy to production
261292

262293
To promote your app to production, open your **Internal testing** track in Google Play Console and complete the release. Once the internal release is finalized, click **Promote Release > Production**.
263294

@@ -338,7 +369,7 @@ Why does my first upload fail with a message like "You need to use a different p
338369

339370
</summary>
340371
<p>
341-
For the initial deployment, you must manually upload the **.aab** file to Google Play Console to create the first release track. Once the initial track is set up, Dreamflow will handle all subsequent deployments automatically.
372+
For the initial deployment, you must manually [**download the .aab file**](#41-downloading-aab-file) and [**upload it to internal testing track**](#42-upload-aab-file-to-internal-testing-track) in Google Play Console. Once the initial track is set up, Dreamflow will handle all subsequent deployments automatically.
342373
</p>
343374
</details>
344375

0 commit comments

Comments
 (0)