Use initWithEngine:nibName:bundle: method to create FlutterViewController, and then setInitialRoute not working #27216

JsouLiang · 2019-01-29T04:36:23Z

When I use initWithEngine:nibName:bundle: to create FlutterViewController, and then setInitialRoute: ;I find it doesn't work; When I use window.defaultRouteName in main.dart I get '/'
This is the code:

// Appdelegate

    FlutterEngine *engine = [[FlutterEngine alloc] initWithName:@"io.flutter" project:nil allowHeadlessExecution:YES];
    self.engine = engine;
    [self.engine runWithEntrypoint:nil];

// ViewController

    FlutterEngine *flutterEngine = [(AppDelegate *)[[UIApplication sharedApplication] delegate] engine];

    FlutterViewController* flutterViewController = [[FlutterViewController alloc] initWithEngine:flutterEngine nibName:nil bundle:nil];

    [flutterViewController setInitialRoute:@"myApp"];

// main.dart

    void main() => runApp(_widgetForRoute(window.defaultRouteName));

    Widget _widgetForRoute(String route) {
      switch (route) {
        case 'myApp':
          return new MyApp();
        case 'home':
          return new HomePage();
        default:
          return Center(
            child: Text('Unknown route: $route', textDirection: TextDirection.ltr),
          );
      }
    }

I always get a Text and content is ''Unknown route: /'

The text was updated successfully, but these errors were encountered:

kangwang1988 · 2019-01-29T07:30:48Z

@x-liang
flutter doctor -v and a minimal demo project which can reproduce this issue would be helpful.

JsouLiang · 2019-01-29T07:37:10Z

https://github.com/X-Liang/NativeWithFlutter This is Demo link

kangwang1988 · 2019-01-29T15:48:33Z

Look like : #23736
I've reproduced this issue using the latest master. It's again a custom engine related problem.

chengge0921 · 2019-02-11T02:51:11Z

When I use initWithEngine:nibName:bundle: to create FlutterViewController, and then setInitialRoute: ;I find it doesn't work; When I use window.defaultRouteName in main.dart I get '/'
This is the code:

// Appdelegate

    FlutterEngine *engine = [[FlutterEngine alloc] initWithName:@"io.flutter" project:nil allowHeadlessExecution:YES];
    self.engine = engine;
    [self.engine runWithEntrypoint:nil];

// ViewController

    FlutterEngine *flutterEngine = [(AppDelegate *)[[UIApplication sharedApplication] delegate] engine];

    FlutterViewController* flutterViewController = [[FlutterViewController alloc] initWithEngine:flutterEngine nibName:nil bundle:nil];

    [flutterViewController setInitialRoute:@"myApp"];

// main.dart

    void main() => runApp(_widgetForRoute(window.defaultRouteName));

    Widget _widgetForRoute(String route) {
      switch (route) {
        case 'myApp':
          return new MyApp();
        case 'home':
          return new HomePage();
        default:
          return Center(
            child: Text('Unknown route: $route', textDirection: TextDirection.ltr),
          );
      }
    }

I always get a Text and content is ''Unknown route: /'

你好，你的这个问题解决了吗？

lupeihong · 2019-02-13T13:52:02Z

I have the same problem

//AppDelegate
self.flutterEngine = [[FlutterEngine alloc] initWithName:@"io.flutter" project:nil];
[self.flutterEngine runWithEntrypoint:nil];
[GeneratedPluginRegistrant registerWithRegistry:self.flutterEngine];

//ViewController
FlutterViewController *flutterViewController = [FlutterViewController new];
 [flutterViewController setInitialRoute:@"myApp"];


//main.dart
window.defaultRouteName  Is always ‘/’

zoechi · 2019-02-13T16:11:55Z

@lupeihong if it's the same problem, why did you create another issue? #27882

yehot · 2019-02-14T10:00:37Z

Same problem.

But weird, use FlutterViewController *flutterViewController = [FlutterViewController new]; to init the FlutterViewController , the setInitialRoute work fine.

So what's different between [FlutterViewController new] and [[FlutterViewController alloc] initWithEngine:flutterEngine nibName:nil bundle:nil] ?

ps:
use FlutterViewController* flutterViewController = [[FlutterViewController alloc] initWithProject:nil nibName:nil bundle:nil]; work fine too.

zoechi · 2019-02-19T10:21:51Z

@ungacy
Using "add reaction" on the initial comment would increase priority while +1 comments are rather pointless and cause lots of people to get notified for no reason.
To get notified yourself use the [Subscribe] button to the top right instead.

DavidSonNguyen · 2019-02-22T04:19:08Z

I use Swift, and i found problem is self.flutterEngine?.run(withEntrypoint: nil) in document https://github.com/flutter/flutter/wiki/Add-Flutter-to-existing-apps. If you do like that, FlutterEngine will run before you create FlutterViewController so you cannot setInitialRoute.
To solve, you must remove that line in AppDelegate, init FlutterViewController without FlutterEngine let flutterViewController = FlutterViewController(nibName: nil, bundle: nil), and setInitialRoute, final call flutterEngine?.run(withEntrypoint: nil).

zoechi · 2019-02-26T08:34:55Z

@YoungJam
Using "add reaction" on the initial comment would increase priority while +1 comments are rather pointless and cause lots of people to get notified for no reason.
To get notified yourself use the [Subscribe] button to the top right instead.

kidzss · 2019-03-06T02:13:00Z

I solved the problem.
//=======================

@interface XXFlutterViewController : FlutterViewController

@EnD

(void)viewDidLoad {
[super viewDidLoad];
// Do any additional setup after loading the view.
FlutterEngine *flutterEngine = self.engine;

[GeneratedPluginRegistrant registerWithRegistry:flutterEngine];
//custom futter plugin
[XXXFlutterBridge registerWithRegistry:flutterEngine];
}

//open flutter vc
XXFlutterViewController *flutterViewController = [[XXFlutterViewController alloc] init];
[flutterViewController setInitialRoute:@"xxxxx/xxxx"];

kidzss · 2019-03-06T02:19:18Z

I solved the problem.
//=======================

@interface XXFlutterViewController : FlutterViewController

@EnD

(void)viewDidLoad {
[super viewDidLoad];
// Do any additional setup after loading the view.
FlutterEngine *flutterEngine = self.engine;

[GeneratedPluginRegistrant registerWithRegistry:flutterEngine];
//custom futter plugin
[XXXFlutterBridge registerWithRegistry:flutterEngine];
}

//open flutter vc
XXFlutterViewController *flutterViewController = [[XXFlutterViewController alloc] init];
[flutterViewController setInitialRoute:@"xxxxx/xxxx"];

ghost · 2019-03-06T02:26:28Z

it works on me @kidzss

michealstrong · 2019-03-14T14:01:26Z

I solved the problem.
//=======================

@interface XXFlutterViewController : FlutterViewController

@EnD

(void)viewDidLoad {
[super viewDidLoad];
// Do any additional setup after loading the view.
FlutterEngine *flutterEngine = self.engine;

[GeneratedPluginRegistrant registerWithRegistry:flutterEngine];
//custom futter plugin
[XXXFlutterBridge registerWithRegistry:flutterEngine];
}

//open flutter vc
XXFlutterViewController *flutterViewController = [[XXFlutterViewController alloc] init];
[flutterViewController setInitialRoute:@"xxxxx/xxxx"];

Didn't U find the flutterVC dont release in this way?

michael-chiu · 2019-03-15T11:30:19Z

I am still experiencing this issue on iOS platform, with the Flutter version shown below :

// --------- flutter doctor summary --------- //

Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel dev, v1.3.10, on Mac OS X 10.14 18A391, locale en-HK)
[!] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
! Some Android licenses not accepted. To resolve this, run: flutter doctor --android-licenses
[!] iOS toolchain - develop for iOS devices (Xcode 10.1)
✗ Verify that all connected devices have been paired with this computer in Xcode.
If all devices have been paired, libimobiledevice and ideviceinstaller may require updating.
To update with Brew, run:
brew update
brew uninstall --ignore-dependencies libimobiledevice
brew uninstall --ignore-dependencies usbmuxd
brew install --HEAD usbmuxd
brew unlink usbmuxd
brew link usbmuxd
brew install --HEAD libimobiledevice
brew install ideviceinstaller
[✓] Android Studio (version 3.3)
[✓] Connected device (3 available)

// --------- flutter doctor summary --------- //

I am following the official guide on https://github.com/flutter/flutter/wiki/Add-Flutter-to-existing-apps.

SetInitialRoute() is working when using FlutterViewController(project: nil, nibName: nil, bundle: nil), however, this seems make the Flutter plugins not found with the FlutterViewController, when I try to access methods in Flutter plugins, it throws MissingPluginException. It seems that because of those Plugins are register with FlutterEngine, the FlutterViewController will not find them if not connected with the FlutterEngine.

Using FlutterViewController(engine: flutterEngine, nibName: nil, bundle: nil), makes the plugins work, but SetInitialRoute() is not working.

Is there any way or alternative to solve this issue, making both setInitialRoute and plugins work in the same FlutterViewController? Thanks!

Lolingew · 2019-04-25T12:00:15Z

I solved the problem.
//=======================
@interface XXFlutterViewController : FlutterViewController
@EnD
(void)viewDidLoad {
[super viewDidLoad];
// Do any additional setup after loading the view.
FlutterEngine *flutterEngine = self.engine;
[GeneratedPluginRegistrant registerWithRegistry:flutterEngine];
//custom futter plugin
[XXXFlutterBridge registerWithRegistry:flutterEngine];
}
//open flutter vc
XXFlutterViewController *flutterViewController = [[XXFlutterViewController alloc] init];
[flutterViewController setInitialRoute:@"xxxxx/xxxx"];

Didn't U find the flutterVC dont release in this way?

I meet the problem... almost nothing released...

yxwandroid · 2019-05-10T16:10:02Z

When I use initWithEngine:nibName:bundle: to create FlutterViewController, and then setInitialRoute: ;I find it doesn't work; When I use window.defaultRouteName in main.dart I get '/'
This is the code:

// Appdelegate

    FlutterEngine *engine = [[FlutterEngine alloc] initWithName:@"io.flutter" project:nil allowHeadlessExecution:YES];
    self.engine = engine;
    [self.engine runWithEntrypoint:nil];

// ViewController

    FlutterEngine *flutterEngine = [(AppDelegate *)[[UIApplication sharedApplication] delegate] engine];

    FlutterViewController* flutterViewController = [[FlutterViewController alloc] initWithEngine:flutterEngine nibName:nil bundle:nil];

    [flutterViewController setInitialRoute:@"myApp"];

// main.dart

    void main() => runApp(_widgetForRoute(window.defaultRouteName));

    Widget _widgetForRoute(String route) {
      switch (route) {
        case 'myApp':
          return new MyApp();
        case 'home':
          return new HomePage();
        default:
          return Center(
            child: Text('Unknown route: $route', textDirection: TextDirection.ltr),
          );
      }
    }

I always get a Text and content is ''Unknown route: /'
我遇到同样的问题请问你解决了吗

kidzss · 2019-05-13T09:33:21Z

I solved the problem.
//=======================
@interface XXFlutterViewController : FlutterViewController
@EnD
(void)viewDidLoad {
[super viewDidLoad];
// Do any additional setup after loading the view.
FlutterEngine *flutterEngine = self.engine;
[GeneratedPluginRegistrant registerWithRegistry:flutterEngine];
//custom futter plugin
[XXXFlutterBridge registerWithRegistry:flutterEngine];
}
//open flutter vc
XXFlutterViewController *flutterViewController = [[XXFlutterViewController alloc] init];
[flutterViewController setInitialRoute:@"xxxxx/xxxx"];

Didn't U find the flutterVC dont release in this way?

I meet the problem... almost nothing released...
我使用flutter 1.2.1 在dealloc断点是有的

ghost · 2019-05-13T09:42:50Z

I solved the problem.
//=======================
@interface XXFlutterViewController : FlutterViewController
@EnD
(void)viewDidLoad {
[super viewDidLoad];
// Do any additional setup after loading the view.
FlutterEngine *flutterEngine = self.engine;
[GeneratedPluginRegistrant registerWithRegistry:flutterEngine];
//custom futter plugin
[XXXFlutterBridge registerWithRegistry:flutterEngine];
}
//open flutter vc
XXFlutterViewController *flutterViewController = [[XXFlutterViewController alloc] init];
[flutterViewController setInitialRoute:@"xxxxx/xxxx"];

Didn't U find the flutterVC dont release in this way?

I meet the problem... almost nothing released...
我使用flutter 1.2.1 在dealloc断点是有的

i use the same solution and it fixed.But official should also give a solution.

Lolingew · 2019-05-14T02:25:04Z

I solved the problem.
//=======================
@interface XXFlutterViewController : FlutterViewController
@EnD
(void)viewDidLoad {
[super viewDidLoad];
// Do any additional setup after loading the view.
FlutterEngine *flutterEngine = self.engine;
[GeneratedPluginRegistrant registerWithRegistry:flutterEngine];
//custom futter plugin
[XXXFlutterBridge registerWithRegistry:flutterEngine];
}
//open flutter vc
XXFlutterViewController *flutterViewController = [[XXFlutterViewController alloc] init];
[flutterViewController setInitialRoute:@"xxxxx/xxxx"];

Didn't U find the flutterVC dont release in this way?

I meet the problem... almost nothing released...
我使用flutter 1.2.1 在dealloc断点是有的

I update 1.2.1 last week. Do you mean, at 1.2.1 version, this solution will release memory normally? I used this before and found memory increased linearly. I'll try 1.2.1 and test it.

zhangyihui-whalevii · 2019-05-15T03:20:43Z

WVFlutterViewController *controller = [[WVFlutterViewController alloc] init];
[GeneratedPluginRegistrant registerWithRegistry:controller];
[controller setInitialRoute:route];

使用这种方式可以成功传递route，并且不会影响插件的注册

ly05010419 · 2019-06-27T15:12:31Z

the same Problem!

hucong730 · 2019-07-17T11:15:15Z

WVFlutterViewController *controller = [[WVFlutterViewController alloc] init];
[GeneratedPluginRegistrant registerWithRegistry:controller];
[controller setInitialRoute:route];

使用这种方式可以成功传递route，并且不会影响插件的注册

这个方式有效果，感谢。

zzjjob · 2019-09-11T09:53:12Z

create FlutterEngine
[_engine.get() createShell:nil libraryURI:nil];
[_engine.navigationChannel invokeMethod:@"setInitialRoute" arguments:route];
self.flutterVc = [[FlutterViewController alloc] initWithEngine:engine nibName:nil bundle:nil];
[engine launchEngine:nil libraryURI:nil];
[engine setViewController:self.flutterVc];

binjiayou66 · 2019-09-23T09:55:52Z

I solved the problem.
//=======================
@interface XXFlutterViewController : FlutterViewController
@EnD
(void)viewDidLoad {
[super viewDidLoad];
// Do any additional setup after loading the view.
FlutterEngine *flutterEngine = self.engine;
[GeneratedPluginRegistrant registerWithRegistry:flutterEngine];
//custom futter plugin
[XXXFlutterBridge registerWithRegistry:flutterEngine];
}
//open flutter vc
XXFlutterViewController *flutterViewController = [[XXFlutterViewController alloc] init];
[flutterViewController setInitialRoute:@"xxxxx/xxxx"];

Didn't U find the flutterVC dont release in this way?

I meet the problem... almost nothing released...
我使用flutter 1.2.1 在dealloc断点是有的

i use the same solution and it fixed.But official should also give a solution.

Creating a new FlutterViewController in the new or alloc init way does deliver routeName, but this way creates multiple flutter.io/gpu/ui threads over and over again.

Aronlong1001 · 2019-09-25T10:10:17Z

I am still experiencing this issue on iOS platform, with the Flutter version shown below :

// --------- flutter doctor summary --------- //

Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel dev, v1.3.10, on Mac OS X 10.14 18A391, locale en-HK)
[!] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
! Some Android licenses not accepted. To resolve this, run: flutter doctor --android-licenses
[!] iOS toolchain - develop for iOS devices (Xcode 10.1)
✗ Verify that all connected devices have been paired with this computer in Xcode.
If all devices have been paired, libimobiledevice and ideviceinstaller may require updating.
To update with Brew, run:
brew update
brew uninstall --ignore-dependencies libimobiledevice
brew uninstall --ignore-dependencies usbmuxd
brew install --HEAD usbmuxd
brew unlink usbmuxd
brew link usbmuxd
brew install --HEAD libimobiledevice
brew install ideviceinstaller
[✓] Android Studio (version 3.3)
[✓] Connected device (3 available)

// --------- flutter doctor summary --------- //

I am following the official guide on https://github.com/flutter/flutter/wiki/Add-Flutter-to-existing-apps.

SetInitialRoute() is working when using FlutterViewController(project: nil, nibName: nil, bundle: nil), however, this seems make the Flutter plugins not found with the FlutterViewController, when I try to access methods in Flutter plugins, it throws MissingPluginException. It seems that because of those Plugins are register with FlutterEngine, the FlutterViewController will not find them if not connected with the FlutterEngine.

Using FlutterViewController(engine: flutterEngine, nibName: nil, bundle: nil), makes the plugins work, but SetInitialRoute() is not working.

Is there any way or alternative to solve this issue, making both setInitialRoute and plugins work in the same FlutterViewController? Thanks!

i have the same question, have you solved it, please?

lyc2345 · 2019-10-16T08:05:20Z

I am still experiencing this issue on iOS platform, with the Flutter version shown below :
// --------- flutter doctor summary --------- //
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel dev, v1.3.10, on Mac OS X 10.14 18A391, locale en-HK)
[!] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
! Some Android licenses not accepted. To resolve this, run: flutter doctor --android-licenses
[!] iOS toolchain - develop for iOS devices (Xcode 10.1)
✗ Verify that all connected devices have been paired with this computer in Xcode.
If all devices have been paired, libimobiledevice and ideviceinstaller may require updating.
To update with Brew, run:
brew update
brew uninstall --ignore-dependencies libimobiledevice
brew uninstall --ignore-dependencies usbmuxd
brew install --HEAD usbmuxd
brew unlink usbmuxd
brew link usbmuxd
brew install --HEAD libimobiledevice
brew install ideviceinstaller
[✓] Android Studio (version 3.3)
[✓] Connected device (3 available)
// --------- flutter doctor summary --------- //
I am following the official guide on https://github.com/flutter/flutter/wiki/Add-Flutter-to-existing-apps.
SetInitialRoute() is working when using FlutterViewController(project: nil, nibName: nil, bundle: nil), however, this seems make the Flutter plugins not found with the FlutterViewController, when I try to access methods in Flutter plugins, it throws MissingPluginException. It seems that because of those Plugins are register with FlutterEngine, the FlutterViewController will not find them if not connected with the FlutterEngine.
Using FlutterViewController(engine: flutterEngine, nibName: nil, bundle: nil), makes the plugins work, but SetInitialRoute() is not working.
Is there any way or alternative to solve this issue, making both setInitialRoute and plugins work in the same FlutterViewController? Thanks!

i have the same question, have you solved it, please?

When you create a FlutterViewController don't use FlutterEngine

let flutterViewController = FlutterViewController(nibName: nil, bundle: nil)
flutterVC.setInitialRoute("RouteName")

Use this way is working!

xx-li · 2019-10-31T10:24:37Z

I use [FlutterViewController new] replace [[FlutterViewController alloc] initWithEngine:flutterEngine nibName:nil bundle:nil]， setInitialRoute is working， but when native push this FlutterViewController firsh show splashScreen。 Anyone encounter the same problem，how to avoid show splashScreen？

my env is :

Xcode11.2 / iOS13 
Flutter 1.10.14 • channel dev • https://github.com/flutter/flutter.git
Framework • revision 1946fc4da0 (3 weeks ago) • 2019-10-07 15:23:31 -0700
Engine • revision 1d62160fdb
Tools • Dart 2.6.0 (build 2.6.0-dev.1.0 d6c6d12ebf)

ungacy · 2019-11-01T05:47:07Z

I use [FlutterViewController new] replace [[FlutterViewController alloc] initWithEngine:flutterEngine nibName:nil bundle:nil]， setInitialRoute is working， but when native push this FlutterViewController firsh show splashScreen。 Anyone encounter the same problem，how to avoid show splashScreen？

my env is :
Xcode11.2 / iOS13 
Flutter 1.10.14 • channel dev • https://github.com/flutter/flutter.git
Framework • revision 1946fc4da0 (3 weeks ago) • 2019-10-07 15:23:31 -0700
Engine • revision 1d62160fdb
Tools • Dart 2.6.0 (build 2.6.0-dev.1.0 d6c6d12ebf)

try to set a view to propertysplashScreenView to the instance of FlutterViewController

xx-li · 2019-11-01T06:06:18Z

I use [FlutterViewController new] replace [[FlutterViewController alloc] initWithEngine:flutterEngine nibName:nil bundle:nil]， setInitialRoute is working， but when native push this FlutterViewController firsh show splashScreen。 Anyone encounter the same problem，how to avoid show splashScreen？
my env is :
Xcode11.2 / iOS13 
Flutter 1.10.14 • channel dev • https://github.com/flutter/flutter.git
Framework • revision 1946fc4da0 (3 weeks ago) • 2019-10-07 15:23:31 -0700
Engine • revision 1d62160fdb
Tools • Dart 2.6.0 (build 2.6.0-dev.1.0 d6c6d12ebf)
try to set a view to propertysplashScreenView to the instance of FlutterViewController

tks，I am so tried，push animation is not normal

ungacy · 2019-11-01T06:15:44Z

    FlutterViewController *some = [FlutterViewController new];
    UIView *view = [[UIView alloc] initWithFrame:UIApplication.sharedApplication.keyWindow.bounds];
    view.backgroundColor = [UIColor whiteColor];
    some.splashScreenView = view;

xx-li · 2019-11-01T06:20:59Z

    FlutterViewController *some = [FlutterViewController new];
    UIView *view = [[UIView alloc] initWithFrame:UIApplication.sharedApplication.keyWindow.bounds];
    view.backgroundColor = [UIColor whiteColor];
    some.splashScreenView = view;

tks, I am also try so, push animation firsh show white splashScreenView， I need to avoid show splashScreen.

zyg1982527 · 2019-11-01T09:12:35Z

我搞定了，可以传入routeName，又能保证交互好用。it work well

let flutterViewController = FlutterViewController.init(project: nil , nibName: nil, bundle: nil)!;
flutterViewController.splashScreenView = FlutterSplashViewController().view
GeneratedPluginRegistrant.register(with: flutterViewController)
flutterViewController.setInitialRoute("test1");
flutterViewController.view.frame = UIScreen.main.bounds;
self.navigationController?.pushViewController(flutterViewController, animated: true)
self.flutterEngine = FlutterEngine(name: "io.flutter", project: nil)
self.flutterEngine?.run(withEntrypoint: nil)
GeneratedPluginRegistrant.register(with: self.flutterEngine)

xx-li · 2019-11-04T03:28:48Z

Use [FlutterViewController new] replace [[FlutterViewController alloc] initWithEngine:flutterEngine nibName:nil bundle:nil] cause other problems。 I have two problems encountered now.

Can't avoid show splashScreenView
Case package_info not normal work。（Suspected that the native and Flutter could not communicate properly）

zyg1982527 · 2019-11-04T03:36:19Z

yes ,splashScreenView cannot be ignored. Use my code flutter plugin can work normal. Do you try other plugin?for example flutter share_preference | | 自己 | | 邮箱：zyg1982527@126.com | 签名由网易邮箱大师定制 On 11/04/2019 11:31, Stellar wrote: Use [FlutterViewController new] replace [[FlutterViewController alloc] initWithEngine:flutterEngine nibName:nil bundle:nil] cause other problems。 I have two problems encountered now. Can't avoid show splashScreenView Case package_info not normal work。（Suspected that the native and Flutter could not communicate properly） — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

xx-li · 2019-11-04T03:43:34Z

@zyg1982527 Should be caused by plugin registration issues， use [GeneratedPluginRegistrant registerWithRegistry:flutterViewController]; after FlutterViewController init can resolve it。 A little worried about whether other problems will be introduced later。

freedom-shen · 2019-11-14T06:13:51Z

仔细研究了下Flutter/Engine里面的源码，setInitialRoute要在launchEngine:libraryURI:之前，
使用了initWithEngine方法，要求自定义的FlutterEngine初始化完毕，并且运行runWithEntrypoint:libraryURI:（内部还是会调用launchEngine:libraryURI:）。
所以使用initWithEngine初始化，setInitialRoute是无效的。
所以只能使用initWithProject（init,new都会调用该方法），但是带来了新问题会加载Launch图。

贴一个简单的思路，新建一个FlutterViewController的子类CSFlutterController，去除和launch有关的部分。

@interface CSFlutterViewController ()  {
    BOOL _enigneNeedsLaunch;
}
@end

@implementation CSFlutterViewController

#pragma mark - Rewrite

- (BOOL)loadDefaultSplashScreenView {
    return NO;
}

- (void)installSplashScreenViewIfNecessary {
}

- (void)removeSplashScreenView:(dispatch_block_t _Nullable)onComplete {
    onComplete();
}

#pragma mark - Init Rewrite

- (instancetype)initWithProject:(FlutterDartProject *)project nibName:(NSString *)nibName bundle:(NSBundle *)nibBundle {
    self = [super initWithProject:project nibName:nibName bundle:nibBundle];
    if (self) {
        _enigneNeedsLaunch = NO;
        [self setInitialRoute:@"/userCenter"];
        [self.engine performSelector:@selector(launchEngine:libraryURI:) withObject:nil withObject:nil];
        [self.engine runWithEntrypoint:nil libraryURI:nil];
        [self.engine setViewController:self];
    }
    return self;
}

@end

amazingrace · 2019-11-19T11:28:09Z

WVFlutterViewController *controller = [[WVFlutterViewController alloc] init];
[GeneratedPluginRegistrant registerWithRegistry:controller];
[controller setInitialRoute:route];

使用这种方式可以成功传递route，并且不会影响插件的注册

Yes, it woks for me. You saved my 2 days time, thanks a lot.

亲们，这个法子真的可以啊，[GeneratedPluginRegistrant registerWithRegistry:controller]; 而不是[GeneratedPluginRegistrant registerWithRegistry:self.engine];
官网害死人啦。
---------来自被这个问题搞疯了两天的程序媛。。

zyg1982527 · 2019-11-19T11:32:57Z

哈哈，能帮到大家我很开心 | | 自己 | | 邮箱：zyg1982527@126.com | 签名由网易邮箱大师定制 On 11/19/2019 19:30, amazingrace wrote: WVFlutterViewController *controller = [[WVFlutterViewController alloc] init]; [GeneratedPluginRegistrant registerWithRegistry:controller]; [controller setInitialRoute:route]; 使用这种方式可以成功传递route，并且不会影响插件的注册 Yes, it woks for me. You saved my 2 days time, thanks a lot. 亲们，这个法子真的可以啊，[GeneratedPluginRegistrant registerWithRegistry:controller]; 而不是[GeneratedPluginRegistrant registerWithRegistry:self.engine]; 官网害死人啦。 ---------来自被这个问题搞疯了两天的程序媛。。 — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

xster · 2019-12-11T23:57:41Z

This is somewhat the same as #31185 and now covered under #31185. Also adding some clarifications in flutter/engine#14367.

To be fair, this API is indeed unclear and confusing. I think we want to gradually discourage its use but don't have a great alternative yet.

In general, we should make all custom interop easier #32930 so you can pass any initialization data you'd like at startup, not only route.

Also, if we were to make built-in concepts like route easier, we should do it on top of the upcoming navigator APIs rather than adding more to the current imperative navigator APIs. #45938

WinJayQ · 2020-01-07T11:06:20Z

I use Swift, and i found problem is self.flutterEngine?.run(withEntrypoint: nil) in document https://github.com/flutter/flutter/wiki/Add-Flutter-to-existing-apps. If you do like that, FlutterEngine will run before you create FlutterViewController so you cannot setInitialRoute.
To solve, you must remove that line in AppDelegate, init FlutterViewController without FlutterEngine let flutterViewController = FlutterViewController(nibName: nil, bundle: nil), and setInitialRoute, final call flutterEngine?.run(withEntrypoint: nil).

Yes, it woks for me.

jitesh-sharma · 2020-01-14T07:33:34Z

I use Swift, and i found problem is self.flutterEngine?.run(withEntrypoint: nil) in document https://github.com/flutter/flutter/wiki/Add-Flutter-to-existing-apps. If you do like that, FlutterEngine will run before you create FlutterViewController so you cannot setInitialRoute.
To solve, you must remove that line in AppDelegate, init FlutterViewController without FlutterEngine let flutterViewController = FlutterViewController(nibName: nil, bundle: nil), and setInitialRoute, final call flutterEngine?.run(withEntrypoint: nil).

Yes, it woks for me.

its working, but showing splash screen before pushing to flutterViewController and when we are trying to pop from flutterViewController its pop to black screen instead of our native iOS ViewController. Also we have another issue when we create flutterView without flutterengine like getting MissingPluginException for FlutterMethodChannel.

github-actions · 2021-08-14T06:00:51Z

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

kangwang1988 added the waiting for customer response label Jan 29, 2019

no-response bot removed the waiting for customer response label Jan 29, 2019

zoechi added f: routes a: existing-apps labels Jan 29, 2019

zoechi added this to the Goals milestone Jan 29, 2019

kangwang1988 closed this as completed Jan 29, 2019

kangwang1988 reopened this Jan 29, 2019

zoechi added the engine label Jan 29, 2019

kangwang1988 mentioned this issue Jan 29, 2019

Make sure that 'setInitialRoute' works fine for a developer create engine. flutter/engine#7627

Closed

zoechi changed the title ~~Use initWithEngine:nibName:bundle: method to create FlutterViewController, and then setInitialRoute doesn't working~~ Use initWithEngine:nibName:bundle: method to create FlutterViewController, and then setInitialRoute not working Feb 11, 2019

spemagic mentioned this issue Feb 20, 2019

iOS 如何路由到不同的 Flutter 界面？官方 SDK 路由好像有 Bug 没修复 jiisd/YHFlutterAdapter#5

Open

This comment has been minimized.

Sign in to view

xster mentioned this issue Aug 29, 2019

Reconcile Android/iOS on usage of a builder when creating activity/vc #33098

Closed

xster mentioned this issue Dec 11, 2019

objcdoc fix for some ambiguity flutter/engine#14367

Merged

xster closed this as completed in flutter/engine#14367 Dec 12, 2019

github-actions bot locked as resolved and limited conversation to collaborators Aug 14, 2021

Use initWithEngine:nibName:bundle: method to create FlutterViewController, and then setInitialRoute not working #27216

Use initWithEngine:nibName:bundle: method to create FlutterViewController, and then setInitialRoute not working #27216

Comments

JsouLiang commented Jan 29, 2019 • edited by zoechi Loading

kangwang1988 commented Jan 29, 2019

JsouLiang commented Jan 29, 2019

kangwang1988 commented Jan 29, 2019 • edited Loading

chengge0921 commented Feb 11, 2019

lupeihong commented Feb 13, 2019 • edited by zoechi Loading

zoechi commented Feb 13, 2019

yehot commented Feb 14, 2019 • edited Loading

zoechi commented Feb 19, 2019

DavidSonNguyen commented Feb 22, 2019 • edited Loading

This comment has been minimized.

zoechi commented Feb 26, 2019

kidzss commented Mar 6, 2019

kidzss commented Mar 6, 2019

ghost commented Mar 6, 2019

michealstrong commented Mar 14, 2019

michael-chiu commented Mar 15, 2019

Lolingew commented Apr 25, 2019

yxwandroid commented May 10, 2019

kidzss commented May 13, 2019

ghost commented May 13, 2019

Lolingew commented May 14, 2019

zhangyihui-whalevii commented May 15, 2019

ly05010419 commented Jun 27, 2019

hucong730 commented Jul 17, 2019

zzjjob commented Sep 11, 2019

binjiayou66 commented Sep 23, 2019

Aronlong1001 commented Sep 25, 2019

lyc2345 commented Oct 16, 2019

xx-li commented Oct 31, 2019

ungacy commented Nov 1, 2019

xx-li commented Nov 1, 2019

ungacy commented Nov 1, 2019

xx-li commented Nov 1, 2019

zyg1982527 commented Nov 1, 2019

xx-li commented Nov 4, 2019

zyg1982527 commented Nov 4, 2019 via email

xx-li commented Nov 4, 2019

freedom-shen commented Nov 14, 2019 • edited Loading

amazingrace commented Nov 19, 2019

zyg1982527 commented Nov 19, 2019 via email

xster commented Dec 11, 2019

WinJayQ commented Jan 7, 2020

jitesh-sharma commented Jan 14, 2020 • edited Loading

github-actions bot commented Aug 14, 2021

JsouLiang commented Jan 29, 2019 •

edited by zoechi

Loading

kangwang1988 commented Jan 29, 2019 •

edited

Loading

lupeihong commented Feb 13, 2019 •

edited by zoechi

Loading

yehot commented Feb 14, 2019 •

edited

Loading

DavidSonNguyen commented Feb 22, 2019 •

edited

Loading

freedom-shen commented Nov 14, 2019 •

edited

Loading

jitesh-sharma commented Jan 14, 2020 •

edited

Loading