Add flavors and code signing for macos and ios build workflow

[jesscmoore]

Description

• Edit ios/macos project.yml files to add flavor build configurations with code signing so that capabilities such as local secure storage are enabled in builds

• Setup provisioning profile and certs in repo and update installer workflow for macos/ios builds

Why

So that as a developer can have separate build configurations for the build for each signing type and setup CI/CD builds of macos/ios apps.

Closing Criteria

Checklist for closing the issue:

• All tests pass
• Creates build configurations for unsigned and signed macos apps.
• Creates build configurations for unsigned and signed ios apps.
• Macos unsigned dmg workflow working
• Macos dev dmg workflow working
• Macos staging dmg workflow working
• ios unsigned dmg workflow working
• ios dev dmg workflow working
• ios staging dmg workflow working

[jesscmoore]

Build configurations for each build mode and flavor-build mode combo are stored in the macos/Runner.xcodeproj/project.pbxproj file which comprising nested build configurations and other information as key value pairs formatted in OpenStep ASCII.

I tried converting it to json with plutil, editing with jq to add signing settings. xcodebuild (used by flutter) can read it in json format. However it needs pod install to install pods for the flavors, which required project.pbxproj in openstep format. However there is no easy way to convert it back to openstep format. Additionally there are more settings that each flavor build config needs, which seem to be created when one edits in xcode, but which need to be added if scripting.

There are ruby, python and nodejs modules to edit project.pbxproj files which could be used. However, as the project file becomes very nested and complex, and gets easily changed when people open xcode, I will try one of the new project.pbxproj generation tool xcodegen which allows one to configure a project in .yaml file and generate the project.pbxproj, such that only the yaml file needs to be in version control.

• https://github.com/yonaskolb/XcodeGen

Additionally, these files must also be added when flavors are added, to enable pod install to work after flavors are added to the project.pbxproj file.

1. Edit macos/Podfile to append/insert:

# Match flavor build configs to build phases
project 'Runner', {
  'Debug' => :debug,
  'Debug-dev' => :debug,
  'Debug-staging' => :debug,
  'Debug-unsigned' => :debug,
  'Profile' => :release,
  'Profile-dev' => :release,
  'Profile-staging' => :release,
  'Profile-unsigned' => :release,
  'Release' => :release,
  'Release-dev' => :release,
  'Release-staging' => :release,
  'Release-unsigned' => :release,
}

2. Edit macos/Runner/Configs/AppInfo.xcconfig to append:

# Add includes for each flavor build config
#include "Pods/Target Support Files/Pods-Runner/Pods-Runner.debug-dev.xcconfig"
#include "Pods/Target Support Files/Pods-Runner/Pods-Runner.debug-staging.xcconfig"
#include "Pods/Target Support Files/Pods-Runner/Pods-Runner.debug-unsigned.xcconfig"
#include "Pods/Target Support Files/Pods-Runner/Pods-Runner.profile-dev.xcconfig"
#include "Pods/Target Support Files/Pods-Runner/Pods-Runner.profile-staging.xcconfig"
#include "Pods/Target Support Files/Pods-Runner/Pods-Runner.profile-unsigned.xcconfig"
#include "Pods/Target Support Files/Pods-Runner/Pods-Runner.release-dev.xcconfig"
#include "Pods/Target Support Files/Pods-Runner/Pods-Runner.release-staging.xcconfig"
#include "Pods/Target Support Files/Pods-Runner/Pods-Runner.release-unsigned.xcconfig"

[jesscmoore]

@gjwgit Adding a precursor issue of script and yml file to automate generation of macos/ios xcode project configuration files. Configuring flavors and codesigning is an add on to that.

[jesscmoore]

This will be easier after PR 14 merged, which migrates to xcodegen with human readable project.yml build configuration.