Automating can help you save some time. It’s also very convenient. It also often helps your environment stay consistent: e.g. you tag a commit in your GitHub repository and a new store release is published.

xkcd: Automation

Lastly, I spent some time on automating publishing my Flutter app to Google Play, which I usually did from my Windows desktop, but it was annoying to type this long fastlane supply command with my Google Service Account JSON key path, etc. It took me a good day to assemble everything together and I finally managed to succeed. In this post, I wanted to share this knowledge (and workflow source code) to the community so that you won’t have to waste that much time on it.

Intro

I’m going to do a walkthrough through my GitHub Actions workflow. It has the following features:

• flutter analyze‘ying,
• flutter testing,
• compiling Flutter app to Android App Bundle (with release key signing),
• publishing the AAB and metadata (store listing stuff) to Google Play and
• caching all dependencies.

#flutter #github