You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
running the app on a simulator with iOS 17.2 on Ventura 13.6.3 with xCode 15.1 on a iPhone 15 pro Max, i'm receiving this warning:
[VERBOSE-2:FlutterDarwinContextMetalImpeller.mm(37)] Using the Impeller rendering backend.
Debug service listening on ws://127.0.0.1:63400/KhLvgbCn7Q4=/ws
Syncing files to device iPhone 15 Pro Max...
[VERBOSE-2:shell.cc(1004)] The 'sstonn/flutter_watch_os_connectivity_callback' channel sent a message from native to Flutter on a non-platform thread. Platform channel messages must be sent on the platform thread. Failure to do so may result in data loss or crashes, and must be fixed in the plugin or application code creating that channel.
See https://docs.flutter.dev/platform-integration/platform-channels#channels-and-platform-threading for more information.
No problem or crash, just trying to figure out if this may cause serious problems or just a warning.
The text was updated successfully, but these errors were encountered:
I was just coming here to check if anyone else had addressed this issue. I had some hard to reproduce bugs in my app due to not calling flutter from the main thread on iOS.
I think we should fix this and submit a PR. I don't know if this repo is actively being maintained though.
To people coming here, the way this package is structured it actually delegates this functionality to another package maintained by the same person.
The bug is coming from the flutter_watch_os_connectivity package and there is an open issue in that repo tracking this issue here: ssttonn/flutter_watch_os_connectivity#4
UPDATE: I opened a PR resolving this issue in that repo
Hello,
running the app on a simulator with iOS 17.2 on Ventura 13.6.3 with xCode 15.1 on a iPhone 15 pro Max, i'm receiving this warning:
No problem or crash, just trying to figure out if this may cause serious problems or just a warning.
The text was updated successfully, but these errors were encountered: