Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

message from native to Flutter on a non-platform thread #1

Open
majindageta opened this issue Dec 14, 2023 · 2 comments
Open

message from native to Flutter on a non-platform thread #1

majindageta opened this issue Dec 14, 2023 · 2 comments

Comments

@majindageta
Copy link

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.

@chadpav
Copy link

chadpav commented Jan 4, 2024

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.

I'll report back soon.

@chadpav
Copy link

chadpav commented Jan 5, 2024

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

We should close this as a duplicate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants