Setup Visual Studio Code to build your Wrapply Flutter source code
If you downloaded the complete Flutter source code from Wrapply, you can open it in Visual Studio Code, install Flutter and Dart tools, configure Android and iOS environments, run the app locally and build APK, AAB or IPA files in a few minutes.
What you need to install
To build a Flutter app from Wrapply source code, install the editor, Flutter SDK and the platform tools required for Android or iOS builds.
The recommended lightweight editor to open and edit the generated Flutter project. Flutter SDK
Required to run Flutter commands such as
flutter pub get, flutter run and build commands.
Android Studio / Android SDKRequired to build Android APK and AAB files. Android Studio also installs Android SDK tools. Xcode for iOS
Required only for iOS builds. Xcode works on macOS and is needed for IPA generation and Apple signing.
Install VS Code Flutter extensions
After installing Visual Studio Code, add the official Flutter and Dart extensions. These extensions provide syntax support, debugging, Flutter commands and device selection directly inside VS Code.
Open Visual Studio Code
Launch VS Code after installation.
Open Extensions
Click the Extensions icon on the left sidebar or press Ctrl + Shift + X on Windows/Linux or Cmd + Shift + X on macOS.
Install Flutter
Search for Flutter and install the official Flutter extension. The Dart extension is usually installed automatically as a dependency.
Restart VS Code
Restart the editor after installing the extensions to make sure all Flutter tools are loaded correctly.
Open your Wrapply source code
The source code package generated by Wrapply is a complete Flutter project. Open the root folder, not a single file.
Extract the ZIP file
Download the source code ZIP from the Wrapply email and extract it into a clean folder on your computer.
Open the project folder
In VS Code, choose File → Open Folder and select the root folder containing pubspec.yaml.
Open the terminal
In VS Code, open Terminal → New Terminal. The terminal should start inside your project folder.
Install dependencies
Run flutter pub get to download all packages used by the generated app.
flutter pub get
Check your Flutter environment
Before building, verify that Flutter can detect your editor, Android SDK, devices and iOS tools if you are on macOS.
Run Flutter Doctor
This command checks whether Flutter, Android SDK, Xcode and connected devices are correctly configured.
Fix missing Android licenses
If Flutter reports Android license issues, accept them with flutter doctor --android-licenses.
Connect or start a device
Use an Android emulator, a physical Android device, an iOS simulator on Mac, or a real iPhone with Xcode signing configured.
flutter doctor
flutter doctor --android-licenses
flutter devices
Build the app in a few minutes
Once the project is open and dependencies are installed, you can run and build the app using standard Flutter commands.
Use this to test the app on an emulator or connected device.
Creates an installable Android file for testing, demos or direct installation.
Creates a Google Play-ready Android App Bundle.
Requires macOS, Xcode and Apple signing. Used for Apple distribution workflows.
flutter pub get
flutter run
flutter build apk --release
flutter build appbundle --release
flutter build ipa --release
Where the build files are created
After running build commands, Flutter creates output files inside the build folder.
Usually generated in
build/app/outputs/flutter-apk/.
Usually generated in
build/app/outputs/bundle/release/.
Generated through Flutter and Xcode depending on your signing and archive workflow.
This folder is generated automatically. You normally do not edit it manually.
Before creating production builds
Before publishing on Google Play or the App Store, review identity, branding and permissions.
Update the name shown on the device and in store metadata.
Use a unique package name such as
com.company.appname.
Use a unique Bundle ID configured in Xcode and App Store Connect.
Replace the default icon with your final brand icon.
Check AndroidManifest.xml and iOS Info.plist if you use camera, location, notifications or file access.
Update version and build number before submitting new releases.
Recommended workflow for Wrapply projects
This is the simplest workflow when you receive the complete Flutter source code.
Generate your app with Wrapply
Use the online tool to configure AppBar, BottomNavigationBar, FloatingActionButton and receive ready files by email.
Download the Flutter source code
Extract the source code and open it in VS Code.
Run the project
Use flutter pub get and flutter run to test the app locally.
Make deeper customizations
Modify UI, navigation, app name, package name, icons, Firebase integrations or mobile-specific logic from the code.
Build production files
Generate APK, AAB or IPA depending on your target platform.
Common setup issues
VS Code does not recognize Flutter
Make sure Flutter SDK is installed, added to your PATH and that the Flutter extension is installed in VS Code.
Android build fails because licenses are missing
Run flutter doctor --android-licenses and accept the required Android SDK licenses.
No devices are detected
Start an emulator, connect a physical device or run flutter devices to check available targets.
iOS build fails on Windows
iOS builds require macOS and Xcode. On Windows you can build Android APK/AAB, but iOS needs a Mac or managed iOS support.
Need help building or publishing?
Wrapply can generate signed Android files, assist with iOS builds, apply deeper customizations from source code and manage store publishing for clients.