Generate apk files as part of standard build process

[kevinsullivan]

Jacob and Nick,

Let's think about having a smart and documented deployment process. What I've seen is manually running a build, trying to email myself the apk file (and failing at that), eventually getting it onto the phone, acknowledging a bunch of unknown origin app warnings, and finally having it running. Exhausting! It seems to me that the build process should generate and post up-to-date apk files. These Flutter packages, or things like them, can then detect when an update is needed, and do the right thing. So let's talk about our build/deploy process.

[nicholasphair]

Absolutely, I was about to create this same issue :)

Skimming quickly, this might be a starting point
subosito/flutter-action#4

Then after that we can move to https://github.com/marketplace/actions/upload-android-release-to-play-store

Also, for installing on the device, my process was flutter install -d '<device id' it was a bit easier than emailing but your phone needs to be connected.

[GeorgeMiroulis]

I just spoke with nick about this and am gonna try to get it done before our next tuesday meeting.

[kevinsullivan]

Also, for installing on the device, my process was flutter install -d '<device id' it was a bit easier than emailing but your phone needs to be connected.

Nick, I'm not quite seeing the details as to how to make this work. Fill me in at some point.

[kevinsullivan]

George,

I'm glad you're picking this up. Feel free to sketch what you're proposing to do, or what you're in the middle of doing, for validation and feedback. What we'd ultimately like to have is that pushing to the main branch on our production repo triggers replacement of the current build in the App Stores. An intermediate result would be to build the required apk and related files and post them to our repo, at which point running apps could see that there's a new version to download.

Kevin