text stringlengths 1 474 |
|---|
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. This allows you to create a build archive |
with full control of distribution certificates in a temporary keychain |
isolated from your login keychain.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 an iOS Distribution certificate to code sign 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 iOS Distribution from the private key.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.Fetch the code signing files from App Store Connect:Where cert_key is either your exported iOS Distribution certificate private key |
or a new private key which automatically generates a new certificate. The certificate |
will be created from the private key if it doesn’t exist in App Store Connect.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 the iOS project:Note that export_options.pl... |
Publish the 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: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.<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.For more details, see Distribute an app using TestFlight.<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 macOS app |
This guide provides a step-by-step walkthrough of releasing a |
Flutter app to the App Store.<topic_end> |
<topic_start> |
Preliminaries |
Before beginning the process of releasing your app, |
ensure that it meets |
Apple’s App Review Guidelines.In order to publish your app to the App Store, |
you must first enroll in the |
Apple Developer Program. |
You can read more about the various |
membership options in Apple’s |
Choosing a Membership guide.<topic_end> |
<topic_start> |
Register your app on App Store Connect |
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+1The 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 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.