Skip to content

Commit 00a190f

Browse files
committed
Update app versioning info
1 parent 4f19e48 commit 00a190f

File tree

3 files changed

+7
-44
lines changed

3 files changed

+7
-44
lines changed

docs/testing-deployment-publishing/publishing/apple-appstore-deployment.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -222,6 +222,7 @@ To deploy your app from FlutterFlow, go to **Settings & Integrations > App Setti
222222
![deploy-to-appstore.avif](../imgs/deploy-to-appstore.avif)
223223

224224
:::info
225+
- Every time you deploy, we'll auto increment the **Build Number** (i.e., version code in Android) to ensure that each release is identifiable. If needed, you can update the *App Version* and *Build Number* yourself.
225226
- If another deployment is already in progress, deploying a new build will cancel the previous one.
226227
- It may take a few minutes for the request to process. Once completed, the status will be updated to **Submitted**.
227228
:::

docs/testing-deployment-publishing/publishing/deploy-from-github.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ To deploy from a GitHub repository:
3131

3232
:::info[important]
3333

34-
When deploying from your GitHub branch, you will need to manage the app versioning manually. This is done through the `pubspec.yaml` file. For example, to set the version to **1.1.0** and the build number to **2**, you can use the format: `version: 1.1.0+2`. Learn more about app versioning [**here**](#).
34+
When deploying from your GitHub branch, you will need to manage the app versioning manually. This is done through the `pubspec.yaml` file. For example, to set the version to **1.1.0** and the build number to **2**, you can use the format: `version: 1.1.0+2`.
3535

3636
![update-version.avif](../imgs/update-version.avif)
3737

docs/testing-deployment-publishing/publishing/google-playstore-deployment.md

Lines changed: 5 additions & 43 deletions
Original file line numberDiff line numberDiff line change
@@ -314,57 +314,19 @@ You can now deploy directly from FlutterFlow or from your GitHub repository.
314314

315315
:::info
316316

317-
- Every time you deploy, we'll auto increment the 'Build Number' (i.e., version code in Android). If needed, you can update the **App Version** and **Build Number** yourself.
317+
- Every time you deploy, we'll auto increment the **Build Number** (i.e., version code in Android) to ensure that each release is identifiable. If needed, you can update the *App Version* and *Build Number* yourself.
318318
- We'll [**auto-generate**](https://developer.android.com/studio/publish/app-signing#generate-key) and [**sign**](https://developer.android.com/studio/publish/app-signing#sign_release) your app for the release with the Keystore (i.e., upload key). If you wish to download the keystore, click the orange key button.
319319

320320
:::
321321

322-
<Tabs>
323-
<TabItem value="FF" label="Deploy From FlutterFlow" default>
324-
Ensure the **Google Play Track** is set to **Internal** and hit the **Deloy to Play Store** again. On successful deployment, you will see the status as 'finished'.
322+
Ensure the **Google Play Track** is set to **Internal** and hit the **Deloy to Play Store** again. On successful deployment, you will see the status as 'finished'.
325323

326324
![deploy-flutterflow](../imgs/deploy-flutterflow.avif)
327325

328-
</TabItem>
329-
<TabItem value="GitHub" label="Deploy From Github">
330-
331-
[Connecting the Github](../exporting-code/push-to-github.md) repo allows you to introduce the custom code into your FlutterFlow project. You may want to deploy the modified code directly from your Github repo to Play Store.
332-
333-
To deploy from Github repo:
334-
335-
1. If you haven't added the Github repo yet, you can do so using the instructions [here](../exporting-code/push-to-github.md).
336-
2. Navigate to **Settings & Integrations > App Settings >** **Mobile** **Deployment**.
337-
3. Find the **Deployment Settings** section and click on the arrow icon on the right to open it.
338-
4. Under the **Deployment Source**, enable the **Use Github repo**.
339-
5. Enter the **Branch Name** of your repo, from which you want to deploy the code. Make sure to enter the correct branch name.
340-
341-
<div style={{
342-
position: 'relative',
343-
paddingBottom: 'calc(56.67989417989418% + 41px)', // Keeps the aspect ratio and additional padding
344-
height: 0,
345-
width: '100%'}}>
346-
<iframe
347-
src="https://www.loom.com/embed/402bba6f50a24f388930b192cce7f554?sid=3d572cc0-0296-45fd-b981-f580cee591ff"
348-
title="Sharing a Project with a User"
349-
style={{
350-
position: 'absolute',
351-
top: 0,
352-
left: 0,
353-
width: '100%',
354-
height: '100%',
355-
colorScheme: 'light'
356-
}}
357-
frameborder="0"
358-
loading="lazy"
359-
webkitAllowFullScreen
360-
mozAllowFullScreen
361-
allowFullScreen
362-
allow="clipboard-write">
363-
</iframe>
364-
</div>
365326

366-
</TabItem>
367-
</Tabs>
327+
:::tip
328+
You also have the option to [**Deploy apps from your GitHub repository**](deploy-from-github.md).
329+
:::
368330

369331

370332
#### 4.4 Verify deployment

0 commit comments

Comments
 (0)