-
Notifications
You must be signed in to change notification settings - Fork 105
Updated App Store deployment info #174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from 3 commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
4f19e48
Updated app store deployment info
pinkeshmars 00a190f
Update app versioning info
pinkeshmars 08c942f
Merge branch 'main' into pinkesh/update-app-store-deployment
pinkeshmars f461358
Address review comments
pinkeshmars 6129e14
Merge branch 'pinkesh/update-app-store-deployment' of https://github.…
pinkeshmars File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Binary file not shown.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file not shown.
Binary file not shown.
267 changes: 54 additions & 213 deletions
267
docs/testing-deployment-publishing/publishing/apple-appstore-deployment.md
Large diffs are not rendered by default.
Oops, something went wrong.
74 changes: 74 additions & 0 deletions
74
docs/testing-deployment-publishing/publishing/deploy-from-github.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,74 @@ | ||
--- | ||
slug: /deployment/deploy-from-github | ||
title: Deploy from GitHub | ||
description: Learn how to deploy your apps directly from GitHub branch. | ||
tags: [Apple App Store, Google Play Store, Deployment, GitHub] | ||
sidebar_position: 5 | ||
keywords: [Apple App Store, Google Play Store, Deployment, GitHub] | ||
--- | ||
|
||
You can deploy your FlutterFlow app directly from a GitHub repository. This is especially useful when you are managing your app’s code on GitHub. Managing code on GitHub enables you to add custom features or advanced functionality that may not be fully supported by FlutterFlow's capabilities. | ||
|
||
Deploying from GitHub is particularly beneficial when: | ||
|
||
- You have written custom code that cannot be managed directly in FlutterFlow, such as features that require advanced Flutter functionality. | ||
- You want to manage the source code in an external GitHub repository for better version control. | ||
- You want to automate the process of deploying your app directly from GitHub to the Play Store or App Store after modifying the code. | ||
- You need full control over your project’s code and want to deploy a specific branch of your GitHub repository. | ||
|
||
## Steps to Deploy | ||
|
||
To deploy from a GitHub repository: | ||
|
||
1. If you haven't already added your project to the GitHub repository, follow the instructions provided [here](../exporting-code/push-to-github.md#connect-a-github-repo). | ||
2. In FlutterFlow, go to **Settings & Integrations > App Settings > Mobile Deployment.** | ||
3. Locate the **Deployment Source** section and click the arrow icon on the right to expand it. | ||
4. Turn on the toggle for **Use GitHub repo: [your repo URL]**. | ||
5. Enter the branch name of your repository that contains the code you want to deploy. Ensure the branch name is correct. | ||
6. Click the **Deploy to App Store** or **Deploy to Play Store** button, depending on your desired platform for deployment. | ||
|
||
 | ||
|
||
:::info[important] | ||
|
||
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`. | ||
|
||
 | ||
|
||
::: | ||
|
||
## FAQs | ||
|
||
<details> | ||
<summary>I am having an issue while Deploying from a GitHub branch. Error: *You uploaded an APK or Android App Bundle that was signed in debug mode. You need to sign your APK or Android App Bundle in release mode.*</summary> | ||
<p> | ||
|
||
If you are experiencing problems deploying or uploading to the Google Play Store from a Github branch, check to make sure your `build.gradle` file is correct. | ||
|
||
1. Open your `android/app/build.gradle` file. | ||
2. Ensure your file has these lines of code: | ||
|
||
``` | ||
def keystoreProperties = new Properties() | ||
def keystorePropertiesFile = rootProject.file('key.properties') | ||
if (keystorePropertiesFile.exists()) { | ||
keystoreProperties.load(new FileInputStream(keystorePropertiesFile)) | ||
} | ||
signingConfigs { | ||
release { | ||
keyAlias keystoreProperties['keyAlias'] | ||
keyPassword keystoreProperties['keyPassword'] | ||
storeFile keystoreProperties['storeFile'] ? file(keystoreProperties['storeFile']) : null | ||
storePassword keystoreProperties['storePassword'] | ||
} | ||
} | ||
``` | ||
|
||
3. Newer Flutterflow code will automatically have these lines added. If yours doesn't, you can push it to your `flutterflow` branch on GitHub and merge in the changes or add them like so: | ||
|
||
 | ||
|
||
|
||
4. Lastly, change `debug` (shown in the red box above) to `release` before deploying. | ||
</p> | ||
</details> |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we mention first that if their flutterflow project is connected to a github repository, then the generated code can be pushed to the github repository and devs can manage deployment from the same repo instead of FF.
I'm also not sure about this line: Managing code on GitHub enables you to add custom features or advanced functionality that may not be fully supported by FlutterFlow's capabilities.
like just mention about the added functionalities that can be added when the genrated code is managed in github and lets end there?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ya, updated it. and removed the 'Managing code on GitHub enables you to ...' as the benefits are very well explained just below it.