Background:

With phase 1 nearing completion, it was time to get the build process into a CI pipeline, this was something that was key for me working at Wyzetalk as we are unable to do that with some of the legacy products. Initially, I looked at codemagic, but from a costing aspect, it would not have been feasible especially when all our Web Apps where already being deployed through Azure Pipelines.

There was not too much info available online as to how to get it to work, specifically iOS, and that which I did find, did not work, so just in case anyone else has a tough time, here is what I ended up doing.

To work around some of the issues I was facing, I needed to add FastLaneinto the pipeline, which was how I had been doing the deployments up until now.

Using the available tooling for getting iOS built was not easy to figure out at all and in the end, I was never able to work out how to resolve the last (I presume) issue with signing the archive.

The android tool worked, the only issue I had was that it could only build for a single architecture, and I was not using aab for this project, and building a standalone 32b APK resulted in upload failures as it did not pass 64b requirements.

The android tools worked right off the bat, but for me, a big limitation was the inability to build multiple apk’s( — split-per-abi) and at this stage moving over to AAB is not an option. This meant I was only able to push up the 64-bit APK as the 32 bit naturally failed the 64-bit check.

More: https://medium.com/wyzetalk-tech/deploying-a-flutter-app-on-azure-pipeline-266aabdf5176