Closed provokateurin closed 4 years ago
This should not have throw because we also change the navigation channel to OptionalMethodChannel. Do you have a repro?
It only happened once seemingly random. I've never seen it again.
This should not have throw because we also change the navigation channel to OptionalMethodChannel.
@chunhtai This isn't throwing; that message is coming from the go-flutter-desktop embedding, which logs every unrecognized method channel call.
I'm not sure why this embedding does that, given that it's at odds with the concept of OptionalMessageChannel
, but it's not a Flutter issue.
https://github.com/flutter/flutter/pull/60299