Ekhlass/Flutter_Documentation · Datasets at Hugging Face

text stringlengths 1 474
while build-number uses CFBundleVersion.
Read more about iOS versioning at Core Foundation Keys
on the Apple Developer’s site.<topic_end>
<topic_start>
Add an app icon
When a new Flutter app is created, a placeholder icon set is created.
This step covers replacing these placeholder icons with your
app’s icons:<topic_end>
<topic_start>
Create a build archive with Xcode
This step covers creating a build archive and uploading
your build to App Store Connect using Xcode.During development, you’ve been building, debugging, and testing
with debug builds. When you’re ready to ship your app to users
on the App Store or TestFlight, you need to prepare a release build.
At this point, you might consider obfuscating your Dart code
to make it more difficult to reverse engineer. Obfuscating
your code involves adding a couple flags to your build command.In Xcode, configure the app version and build:Finally, create a build archive and upload it to App Store Connect:You should receive an email within 30 minutes notifying you that
your build has been validated and is available to release to testers
on TestFlight. At this point you can choose whether to release
on TestFlight, or go ahead and release your app to the App Store.For more details, see
Upload an app to App Store Connect.<topic_end>
<topic_start>
Create a build archive with Codemagic CLI tools
This step covers creating a build archive and uploading
your build to App Store Connect using Flutter build commands
and Codemagic CLI Tools executed in a terminal
in the Flutter project directory.Install the Codemagic CLI tools:You’ll need to generate an App Store Connect API Key
with App Manager access to automate operations with App Store Connect. To make
subsequent commands more concise, set the following environment variables from
the new key: issuer id, key id, and API key file.You need to export or create a Mac App Distribution and a Mac Installer
Distribution certificate to perform code signing and package a build archive.If you have existing certificates, you can export the
private keys by executing the following command for each certificate:Or you can create a new private key by executing the following command:Later, you can have CLI tools automatically create a new Mac App Distribution and
Mac Installer Distribution certificate. You can use the same private key for
each new certificate.Fetch the code signing files from App Store Connect:Where cert_key is either your exported Mac App Distribution certificate private key
or a new private key which automatically generates a new certificate.If you do not have a Mac Installer Distribution certificate,
you can create a new certificate by executing the following:Use cert_key of the private key you created earlier.Fetch the Mac Installer Distribution certificates:Set up a new temporary keychain to be used for code signing:Restore Login Keychain!
After running keychain initialize you must run the following:keychain use-loginThis sets your login keychain as the default to avoid potential
authentication issues with apps on your machine.Now add the fetched certificates to your keychain:Update the Xcode project settings to use fetched code signing profiles:Install Flutter dependencies:Install CocoaPods dependencies:Build the Flutter macOS project:Package the app:Publish the packaged app to App Store Connect:As mentioned earlier, don’t forget to set your login keychain
as the default to avoid authentication issues
with apps on your machine:<topic_end>
<topic_start>
Release your app on TestFlight
TestFlight allows developers to push their apps
to internal and external testers. This optional step
covers releasing your build on TestFlight.<topic_end>
<topic_start>
Distribute to registered devices
See distribution guide
to prepare an archive for distribution to designated Mac computers.<topic_end>
<topic_start>
Release your app to the App Store
When you’re ready to release your app to the world,
follow these steps to submit your app for review and
release to the App Store:Apple notifies you when their app review process is complete.
Your app is released according to the instructions you
specified in the Version Release section.For more details, see
Distribute an app through the App Store.<topic_end>
<topic_start>
Troubleshooting
The Distribute your app guide provides a
detailed overview of the process of releasing an app to the App Store.
<topic_end>
<topic_start>Build and release a Linux app to the Snap Store
During a typical development cycle,
you test an app using flutter run at the command line,
or by using the Run and Debug
options in your IDE. By default,
Flutter builds a debug version of your app.When you’re ready to prepare a release version of your app,
for example to publish to the Snap Store,
this page can help.<topic_end>
<topic_start>
Prerequisites
To build and publish to the Snap Store, you need the
following components:<topic_end>
<topic_start>
Set up the build environment
Use the following instructions to set up your build environment.<topic_end>
<topic_start>
Install snapcraft
At the command line, run the following:<topic_end>
<topic_start>
Install LXD
To install LXD, use the following command:LXD is required during the snap build process. Once installed, LXD needs to be
configured for use. The default answers are suitable for most use cases.On the first run, LXD might not be able to connect to its socket:This means you need to add your username to the LXD
(lxd) group, so log out of your session and then log back in:<topic_end>
<topic_start>
Overview of snapcraft
The snapcraft tool builds snaps based on the instructions
listed in a snapcraft.yaml file.
To get a basic understanding of snapcraft and its
core concepts, take a look at the Snap documentation
and the Introduction to snapcraft.
Additional links and information are listed at the
bottom of this page.<topic_end>
<topic_start>
Flutter snapcraft.yaml example
Place the YAML file in your Flutter
project under <project root>/snap/snapcraft.yaml.
(And remember that YAML files are sensitive to white space!)
For example:The following sections explain the various pieces of the YAML file.<topic_end>

while build-number uses CFBundleVersion.

Read more about iOS versioning at Core Foundation Keys

on the Apple Developer’s site.<topic_end>

<topic_start>

Add an app icon

When a new Flutter app is created, a placeholder icon set is created.

This step covers replacing these placeholder icons with your

app’s icons:<topic_end>

<topic_start>

Create a build archive with Xcode

This step covers creating a build archive and uploading

your build to App Store Connect using Xcode.During development, you’ve been building, debugging, and testing

with debug builds. When you’re ready to ship your app to users

on the App Store or TestFlight, you need to prepare a release build.

At this point, you might consider obfuscating your Dart code

to make it more difficult to reverse engineer. Obfuscating

your code involves adding a couple flags to your build command.In Xcode, configure the app version and build:Finally, create a build archive and upload it to App Store Connect:You should receive an email within 30 minutes notifying you that

your build has been validated and is available to release to testers

on TestFlight. At this point you can choose whether to release

on TestFlight, or go ahead and release your app to the App Store.For more details, see

Upload an app to App Store Connect.<topic_end>

<topic_start>

Create a build archive with Codemagic CLI tools

This step covers creating a build archive and uploading

your build to App Store Connect using Flutter build commands

and Codemagic CLI Tools executed in a terminal

in the Flutter project directory.Install the Codemagic CLI tools:You’ll need to generate an App Store Connect API Key

with App Manager access to automate operations with App Store Connect. To make

subsequent commands more concise, set the following environment variables from

the new key: issuer id, key id, and API key file.You need to export or create a Mac App Distribution and a Mac Installer

Distribution certificate to perform code signing and package a build archive.If you have existing certificates, you can export the

private keys by executing the following command for each certificate:Or you can create a new private key by executing the following command:Later, you can have CLI tools automatically create a new Mac App Distribution and

Mac Installer Distribution certificate. You can use the same private key for

each new certificate.Fetch the code signing files from App Store Connect:Where cert_key is either your exported Mac App Distribution certificate private key

or a new private key which automatically generates a new certificate.If you do not have a Mac Installer Distribution certificate,

you can create a new certificate by executing the following:Use cert_key of the private key you created earlier.Fetch the Mac Installer Distribution certificates:Set up a new temporary keychain to be used for code signing:Restore Login Keychain!

After running keychain initialize you must run the following:keychain use-loginThis sets your login keychain as the default to avoid potential

authentication issues with apps on your machine.Now add the fetched certificates to your keychain:Update the Xcode project settings to use fetched code signing profiles:Install Flutter dependencies:Install CocoaPods dependencies:Build the Flutter macOS project:Package the app:Publish the packaged app to App Store Connect:As mentioned earlier, don’t forget to set your login keychain

as the default to avoid authentication issues

with apps on your machine:<topic_end>

<topic_start>

Release your app on TestFlight

TestFlight allows developers to push their apps

to internal and external testers. This optional step

covers releasing your build on TestFlight.<topic_end>

<topic_start>

Distribute to registered devices

See distribution guide

to prepare an archive for distribution to designated Mac computers.<topic_end>

<topic_start>

Release your app to the App Store

When you’re ready to release your app to the world,

follow these steps to submit your app for review and

release to the App Store:Apple notifies you when their app review process is complete.

Your app is released according to the instructions you

specified in the Version Release section.For more details, see

Distribute an app through the App Store.<topic_end>

<topic_start>

Troubleshooting

The Distribute your app guide provides a

detailed overview of the process of releasing an app to the App Store.

<topic_end>

<topic_start>Build and release a Linux app to the Snap Store

During a typical development cycle,

you test an app using flutter run at the command line,

or by using the Run and Debug

options in your IDE. By default,

Flutter builds a debug version of your app.When you’re ready to prepare a release version of your app,

for example to publish to the Snap Store,

this page can help.<topic_end>

<topic_start>

Prerequisites

To build and publish to the Snap Store, you need the

following components:<topic_end>

<topic_start>

Set up the build environment

Use the following instructions to set up your build environment.<topic_end>

<topic_start>

Install snapcraft

At the command line, run the following:<topic_end>

<topic_start>

Install LXD

To install LXD, use the following command:LXD is required during the snap build process. Once installed, LXD needs to be

configured for use. The default answers are suitable for most use cases.On the first run, LXD might not be able to connect to its socket:This means you need to add your username to the LXD

(lxd) group, so log out of your session and then log back in:<topic_end>

<topic_start>

Overview of snapcraft

The snapcraft tool builds snaps based on the instructions

listed in a snapcraft.yaml file.

To get a basic understanding of snapcraft and its

core concepts, take a look at the Snap documentation

and the Introduction to snapcraft.

Additional links and information are listed at the

bottom of this page.<topic_end>

<topic_start>

Flutter snapcraft.yaml example

Place the YAML file in your Flutter

project under <project root>/snap/snapcraft.yaml.

(And remember that YAML files are sensitive to white space!)

For example:The following sections explain the various pieces of the YAML file.<topic_end>