Ekhlass/flutter_docs · Datasets at Hugging Face

text stringlengths 1 372
manage your app’s life cycle on
app store connect (formerly iTunes connect).
you define your app name and description, add screenshots,
set pricing, and manage releases to the app store and TestFlight.
registering your app involves two steps: registering a unique
bundle ID, and creating an application record on app store connect.
for a detailed overview of app store connect, see the
app store connect guide.
<topic_end>
<topic_start>
register a bundle ID
every macOS application is associated with a bundle ID,
a unique identifier registered with apple.
to register a bundle ID for your app, follow these steps:
<topic_end>
<topic_start>
create an application record on app store connect
register your app on app store connect:
for a detailed overview,
see add an app to your account.
<topic_end>
<topic_start>
review xcode project settings
this step covers reviewing the most important settings
in the xcode workspace.
for detailed procedures and descriptions, see
prepare for app distribution.
navigate to your target’s settings in xcode:
verify the most important settings.
in the identity section:
in the deployment info section:
in the signing & capabilities section:
the general tab of your project settings should resemble
the following:
for a detailed overview of app signing, see
create, export, and delete signing certificates.
<topic_end>
<topic_start>
configuring the app’s name, bundle identifier and copyright
the configuration for the product identifiers are centralized
in macos/Runner/Configs/AppInfo.xcconfig. for the app’s name,
set PRODUCT_NAME, for the copyright set PRODUCT_COPYRIGHT,
and finally set PRODUCT_BUNDLE_IDENTIFIER for the app’s
bundle identifier.
<topic_end>
<topic_start>
updating the app’s version number
the default version number of the app is 1.0.0.
to update it, navigate to the pubspec.yaml file
and update the following line:
version: 1.0.0+1
the version number is three numbers separated by dots,
such as 1.0.0 in the example above, followed by an optional
build number such as 1 in the example above, separated by a +.
both the version and the build number can be overridden in flutter’s
build by specifying --build-name and --build-number,
respectively.
in macOS, build-name uses CFBundleShortVersionString
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.

manage your app’s life cycle on

app store connect (formerly iTunes connect).

you define your app name and description, add screenshots,

set pricing, and manage releases to the app store and TestFlight.

registering your app involves two steps: registering a unique

bundle ID, and creating an application record on app store connect.

for a detailed overview of app store connect, see the

app store connect guide.

<topic_end>

<topic_start>

register a bundle ID

every macOS application is associated with a bundle ID,

a unique identifier registered with apple.

to register a bundle ID for your app, follow these steps:

<topic_end>

<topic_start>

create an application record on app store connect

register your app on app store connect:

for a detailed overview,

see add an app to your account.

<topic_end>

<topic_start>

review xcode project settings

this step covers reviewing the most important settings

in the xcode workspace.

for detailed procedures and descriptions, see

prepare for app distribution.

navigate to your target’s settings in xcode:

verify the most important settings.

in the identity section:

in the deployment info section:

in the signing & capabilities section:

the general tab of your project settings should resemble

the following:

for a detailed overview of app signing, see

create, export, and delete signing certificates.

<topic_end>

<topic_start>

configuring the app’s name, bundle identifier and copyright

the configuration for the product identifiers are centralized

in macos/Runner/Configs/AppInfo.xcconfig. for the app’s name,

set PRODUCT_NAME, for the copyright set PRODUCT_COPYRIGHT,

and finally set PRODUCT_BUNDLE_IDENTIFIER for the app’s

bundle identifier.

<topic_end>

<topic_start>

updating the app’s version number

the default version number of the app is 1.0.0.

to update it, navigate to the pubspec.yaml file

and update the following line:

version: 1.0.0+1

the version number is three numbers separated by dots,

such as 1.0.0 in the example above, followed by an optional

build number such as 1 in the example above, separated by a +.

both the version and the build number can be overridden in flutter’s

build by specifying --build-name and --build-number,

respectively.

in macOS, build-name uses CFBundleShortVersionString

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.