Integrating Flutter into iOS Apps: Mixed Development, Configuration, and Debugging Guide

This article is the final installment of a Flutter series, focusing on practical integration of Flutter into iOS applications through mixed development.

Required files : before mixing iOS and Flutter you must add xcode_backend.sh (provided by the Flutter toolchain) and the automatically generated xcconfig files ( Debug.xcconfig , Release.xcconfig , Generated.xcconfig ) to the Xcode project.

Project -> Info -> Development Target -> Configurations

Script file : add a Run Script phase in the target’s Build Phases and paste the following commands (remember the leading /bin/sh ):

/bin/sh "$FLUTTER_ROOT/packages/flutter_tools/bin/xcode_backend.sh" build
/bin/sh "$FLUTTER_ROOT/packages/flutter_tools/bin/xcode_backend.sh" embed

iOS integration steps :

Change AppDelegate to inherit from FlutterAppDelegate and conform to FlutterAppLifeCycleProvider .

Create a FlutterPluginAppLifeCycleDelegate instance in AppDelegate to forward lifecycle events.

Instantiate a FlutterViewController and present it where needed.

MethodChannel communication :

Flutter calls native code via a MethodChannel :

import 'package:flutter/services.dart';
Future
playVideo() async {
  var methodChannel = MethodChannel('flutterChannelName');
  var params = {'playID':'302998298','duration':'2520','name':'三生三世十里桃花'};
  String result = await methodChannel.invokeMethod('PlayAlbumVideo', params);
}

Native side registers a handler:

NSString *channelName = @"flutterChannelName";
FlutterMethodChannel *methodChannel = [FlutterMethodChannel methodChannelWithName:channelName binaryMessenger:flutterVC];
[methodChannel setMethodCallHandler:^(FlutterMethodCall *call, FlutterResult result) {
  if ([call.method isEqualToString:@"PlayAlbumVideo"]) {
    NSDictionary *params = call.arguments;
    // handle params and return a string
    result([NSString stringWithFormat:@"播放状态 %@", playStatus]);
  }
}];

Common errors include missing FLUTTER_ROOT in Generated.xcconfig , permission issues in the script, and path problems for xcode_backend.sh .

Debugging tools :

Enable performance overlay in VSCode via the Command Palette → Toggle Performance Overlay .

Use Dart DevTools (Inspector, Memory, Debug Paint) for UI inspection, memory profiling, and layout debugging.

Routing :

Static routes are defined in MaterialApp.routes as a map of String keys to Widget builders, while dynamic routes use Navigator.of(context).push(PageRouteBuilder(...)) with custom transitions and can pass data via MethodChannel callbacks.

Both approaches have drawbacks such as black‑screen flashes and loss of widget state when new instances are created.