Recently, for our internal project called Kolizja, we decided to abandon building applications on the internal Jenkins server and move the process to Bitrise. Previously we described how this process looks like for iOS development. Now’s the time to check out how it looks like for a Flutter. In this scenario, additionally, we want to integrate Bitrise with App Center and Firebase. 

Bitrise gives users the ability to configure the entire building process by creating a workflow consisting of ready-made elements. The whole thing resembles the arrangement of a puzzle. Let see how the whole process looks like: 

In this blog post, we’ll concentrate on Flutter related things. The first three steps are universal. We want to import the branch you want to build and import certificates for our application. 

Building with Flutter

For the next steps concerning Flutter, we need to add some environmental variables. 

In most cases, these variables will be the same for each Flutter project, assuming that our repository has a default directory scheme. 

The next steps are responsible for the primary process of building our application. Install is responsible for downloading the latest version of the framework. Analyze performs static code analysis, and finally Build phase is building our project.  

Before building the application, we added a short command that forces the XCode to use the Legacy Build System, which, in our case, is needed to create an iOS version of this particular application. Still, it is not required; otherwise, you can execute any script in the terminal or skip this step.

Sign applications 

Now it’s time to sign our application with certificates, which we have to send in the Code Signing tab. Default settings inside these steps should be enough to execute them correctly.

Integrate with AppCenter

After the previous steps have been correctly performed, we can take care of sending the application files to the AppCenter.

To do this, we need to create a new access token with the Full Access privileges granted. The screen below shows where we can do it: 

Now all you have to do is use the ready-made token in the appropriate API Token field. In this case, we keep it in the Secrets tab.

Values for Owner Name and App Name fields we can obtain from the link to our application in App Center:

Now it is enough to repeat this for the other platform, and that’s it for App Center. 

Firebase App Distribution at the end

At the very end, we want to send our application files to the Firebase App Distribution. We have to do this stage twice for both Android and IOS applications:

To execute this stage correctly, we need three values:

You can get Firebase Token value with the Firebase CLI. Just use the script below. 

curl -sL firebase.tools | bash
firebase login:ci

App Path has already been used in previous stages. That is the path to where our signed application file is located. Firebase App ID can be obtained using the Firebase console by merely entering the Settings -> General -> Your Applications.

The whole workflow should get completed. If our application is built correctly, a new version of the app with version number sets in pubspec.yaml file. As you can see, the setup process itself is straightforward and requires little input from us.

Get started with us

Avatar Hi, I’m Marcin, COO of Applandeo

Looking for a partner that will work with you to create a great product? Fill in the form below and we’ll walk you through the process. Our developers will do more than just write code, but will also work with you to find the best business solutions to your specific needs. Let’s build something great together.

Drop a message
Contact image