Datasets:
Ekhlass
/
flutter_docs

Dataset card Data Studio Files
xet
Community
1
text
stringlengths
1
372
every iOS 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 of the general tab:
in the signing & capabilities tab:
in the deployment section of the build settings tab:
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>
updating the app’s deployment version
if you changed deployment target in your xcode project,
open ios/Flutter/AppframeworkInfo.plist in your flutter app
and update the MinimumOSVersion value to match.
<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>
add a launch image
similar to the app icon,
you can also replace the placeholder launch image:
<topic_end>
<topic_start>
create a build archive and upload to app store connect
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.
<topic_end>
<topic_start>
update the app’s build and version numbers
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:
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 build ipa by specifying --build-name and --build-number,
respectively.
in iOS, build-name uses CFBundleShortVersionString
while build-number uses CFBundleVersion.
read more about iOS versioning at core foundation keys
on the apple developer’s site.
you can also override the pubspec.yaml build name and number in xcode:
<topic_end>
<topic_start>
create an app bundle
run flutter build ipa to produce an xcode build archive (.xcarchive file)
in your project’s build/ios/archive/ directory and an app store app
bundle (.ipa file) in build/ios/ipa.
consider adding the --obfuscate and --split-debug-info flags to
obfuscate your dart code to make it more difficult
to reverse engineer.
if you are not distributing to the app store, you can optionally
choose a different export method by
adding the option --export-method ad-hoc,
--export-method development or --export-method enterprise.
info note
on versions of flutter where flutter build ipa --export-method is unavailable,
open build/ios/archive/MyApp.xcarchive and follow the instructions below
to validate and distribute the app from xcode.
<topic_end>
<topic_start>
upload the app bundle to app store connect
once the app bundle is created, upload it to
app store connect by either:
install and open the apple transport macOS app.
drag and drop the build/ios/ipa/*.ipa app bundle into the app.
or upload the app bundle from the command line by running:
run man altool for details about how to authenticate with the app store connect API key.
or open build/ios/archive/MyApp.xcarchive in xcode.
click the validate app button. if any issues are reported,
address them and produce another build. you can reuse the same
build ID until you upload an archive.
after the archive has been successfully validated, click
distribute app.
info note
when you export your app at the end of distribute app,
xcode will create a directory containing