Better to use "flutter build ipa"

Content

It is better to use "flutter build ipa" in the Makefile to save the time of archiving. However, since you need to specify "TEAM_ID" and "provisioning profile name" in the ExportOptions file, you need to consider whether to add it as a template.

Makefileで「flutter build ipa」を使ったほうがテストフライトの手間が省けます。しかし、ExportOptionsファイルには「TEAM_ID」や「プロビジョニングプロファイル名」などを指定する必要があるので、テンプレートとして追加するかは検討が必要です。

Link

Sample

Makefile

.PHONY: build-ios-dev
build-ios-dev:
    fvm flutter build ipa --flavor Development --dart-define=FLAVOR=development --target lib/main.dart --export-options-plist=ios/Config/DevelopmentExportOptions.plist

DevelopmentExportOptions.plist

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>compileBitcode</key>
    <true/>
    <key>destination</key>
    <string>export</string>
    <key>method</key>
    <string>ad-hoc</string>
    <key>provisioningProfiles</key>
    <dict>
        <key>jp.co.xxxxxx.dev</key>
        <string>XXX Development（Ad Hoc）</string>
    </dict>
    <key>signingCertificate</key>
    <string>Apple Distribution</string>
    <key>signingStyle</key>
    <string>manual</string>
    <key>stripSwiftSymbols</key>
    <true/>
    <key>teamID</key>
    <string>XXXXXXXXXX</string>
    <key>thinning</key>
    <string>&lt;none&gt;</string>
</dict>
</plist>

wasabeef / flutter-architecture-blueprints

Better to use "flutter build ipa" #78

Content

Link

Sample