🍎 iOS publishing

App Store publishing guide for Wrapply apps

Use this guide to understand the iOS publishing workflow for Wrapply Flutter source code, including Xcode signing, Bundle Identifier, TestFlight, App Store Connect and version updates.

Generate your app Back to tutorials

What you need before publishing on the App Store

iOS publishing requires Apple Developer account access, App Store Connect setup, Xcode signing and a valid iOS build/archive.

Apple Developer account
Required for certificates, identifiers, TestFlight and App Store publishing.

App Store Connect access
Used to create the app listing, upload builds and submit for review.

macOS and Xcode
Required for signing, archive creation and iOS build management.

Bundle Identifier
Unique iOS identifier, usually like com.company.appname.

Unlike Android, iOS builds cannot be created directly on Windows. You need macOS/Xcode or managed iOS build support.

App Store publishing flow

Prepare the Flutter source code

Open the project, install dependencies and check that the app runs correctly.

Configure Bundle Identifier

Open ios/Runner.xcworkspace in Xcode and set the Bundle Identifier under Runner → Signing & Capabilities.

Configure signing

Select the Apple Developer Team and enable automatic signing when possible.

Create app in App Store Connect

Create a new app listing with the same Bundle Identifier.

Archive and upload

Build/archive from Xcode or use Flutter build commands, then upload to App Store Connect/TestFlight.

Complete App Store metadata

Add screenshots, description, privacy details, age rating, support URL and review information.

Submit for review

After TestFlight or production preparation, submit the app to Apple review.

Updating an existing iOS app

Like Android, iOS updates depend on what changed: app code or website content.

Update Flutter code
If you change navigation, native permissions, Firebase, icons, Bundle ID settings or app behavior, rebuild and submit a new iOS build.

Update website content
If only the website loaded inside the app changes, update the source website URL/content directly.

Update version in pubspec.yaml
Increase version/build number before submitting a new build to App Store Connect.

Upload new build
Use Xcode or Flutter commands to create and upload the new build.

Example version in pubspec.yaml:
version: 1.0.1+2

iOS commands:
flutter clean
flutter pub get
cd ios && pod install && cd ..
flutter build ipa --release

Important iOS publishing checks

Bundle Identifier
Must match App Store Connect and Apple Developer identifiers.

Signing & Capabilities
Check Push Notifications, Associated Domains, camera/location permissions if used.

Info.plist usage descriptions
Apple requires clear descriptions for camera, location, photos, microphone and tracking.

App Review notes
If login is required, provide Apple with demo credentials and review instructions.

FAQ

Can Wrapply generate iOS builds?

Wrapply can support iOS builds on request because Apple signing is account-specific.

Can I publish iOS without a Mac?

Normally no. iOS build and signing require macOS and Xcode unless you use a managed build service.

Do I rebuild when the website content changes?

Usually no. If the app loads web content from your URL, update the website itself. Rebuild only when app code/configuration changes.