About not using .handover but .interactive

[XueshiQiao]

MultipathTester/MultipathTester/Tests/TCP/TCPStreamTest.swift

Lines 274 to 283 in fa08341

	if multipath {
	switch runCfg.multipathServiceVar {
	case .aggregate:
	config.multipathServiceType = URLSessionConfiguration.MultipathServiceType.aggregate
	case .handover:
	// Don't run handover here, but interactive instead
	runCfg.multipathServiceVar = .interactive
	config.multipathServiceType = URLSessionConfiguration.MultipathServiceType.interactive
	case .interactive:
	config.multipathServiceType = URLSessionConfiguration.MultipathServiceType.interactive

I found that when I using .handover multipath type in NSURLSessionStreamTask, it do not work well. for example, when I have Wifi and 5G, when I turn off Wifi, the connection will close, but works well in .interactive mode, it will use 5G instead of closing the connection.

And I found it works well when using NWConnection with configing its parameter's multipath type to be .handover.

I have search the world, only notice you avoid using .handover here (//Don't run handover here, but interactive instead ), have you encountered the same problem, do you find any resolution for this problem?