Non-platform thread

[senorrelentless]

Hi we are trying to implement health_kit_reporter and we have done so in our main Widget, called with runApp(...)

Immediately in the main widget we setup the listeners.

Even though everything seems to work it is a bit worry some to get this kind of error message. What is the approach here? Cannot health_kit_reporter work with Riverpod?

[ERROR:flutter/shell/common/shell.cc(1015)] The 'health_kit_reporter_event_channel_observer_query' 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.

[Famous-guy]

It seems like you're encountering an error related to platform channel communication in Flutter, specifically when using the health_kit_reporter plugin. This error typically occurs when a platform channel message is sent from a non-platform thread, which violates Flutter's threading model and can lead to issues like data loss or crashes.

To address this issue, you'll need to ensure that platform channel messages are sent on the platform thread. Here are some steps you can take to troubleshoot and potentially fix the problem:

Check Plugin Implementation: First, ensure that the health_kit_reporter plugin is implemented correctly and adheres to Flutter's platform channel threading requirements. Review the plugin's source code, particularly the parts related to channel communication, to see if there are any obvious threading issues.

Isolate Channel Communication: If the plugin's implementation seems correct, consider isolating the channel communication to ensure that messages are sent from the platform thread. This might involve restructuring your code to move channel communication logic to a platform-specific implementation (e.g., in Kotlin/Java for Android or Swift/Objective-C for iOS) and invoking it from Dart code using platform channels.

Check Usage in Widgets: Review how you're using the health_kit_reporter plugin in your Flutter widgets. Ensure that any calls to the plugin's methods are made in the appropriate context and on the main thread. Avoid making blocking or long-running calls on the main thread, as this can lead to performance issues and potentially trigger the error you're seeing.

Consider Threading Models: If you're using Riverpod for state management, consider how it interacts with platform channels and threading. Ensure that any state changes or side effects triggered by health_kit_reporter events are handled appropriately within Riverpod's threading model.

Debugging: Use debugging tools like Flutter's DevTools to inspect the application's threading behavior and identify any potential issues with platform channel communication. Look for patterns or conditions that might lead to messages being sent from non-platform threads.

Consult Plugin Documentation or Community: Check the documentation for the health_kit_reporter plugin to see if there are any specific guidelines or recommendations for handling threading issues. Additionally, consider reaching out to the plugin's developers or the Flutter community for assistance, as others may have encountered similar issues and can provide insights or solutions.

By carefully reviewing your code, checking plugin implementation, and considering threading models, you should be able to identify and address the underlying cause of the error related to platform channel threading in your Flutter application.

[senorrelentless]

Exactly. And since The main App runs on the main thread is why I posted here ie I think that maybe the plugin needs patching.

From what I've found is that the plugin code needs to be wrapped with
dispatch_async(dispatch_get_main_queue(), ^{});

[senorrelentless]

A thing similar fixed with firebase now.

firebase/flutterfire#11628

[Famous-guy]

Wrapping the plugin code with dispatch_async(dispatch_get_main_queue(), ^{} is a common approach in iOS development to ensure that certain tasks are executed on the main thread, especially when dealing with UI updates or interactions. However, in Flutter, you typically don't need to manually manage threads like you would in native iOS development.

Flutter manages its own event loop and automatically runs Dart code on the main UI thread. When communicating with platform-specific code (such as through platform channels), Flutter ensures that messages are sent and received on the appropriate threads.

If you're encountering issues with the health_kit_reporter plugin, it's more likely due to how the plugin itself handles threading internally or how it interacts with Flutter's threading model. Wrapping the plugin code with dispatch_async(dispatch_get_main_queue(), ^{} directly within the plugin might not be the correct solution in this context.

Instead, I would recommend reviewing the plugin's source code to ensure that it correctly handles threading and platform channel communication according to Flutter's conventions. If you suspect that the plugin has threading issues, you may need to address them within the plugin itself or consider alternatives if the issues persist.

Exactly. And since The main App runs on the main thread is why I posted here ie I think that maybe the plugin needs patching.

From what I've found is that the plugin code needs to be wrapped with dispatch_async(dispatch_get_main_queue(), ^{});

[senorrelentless]

ChatGPT much yeah?

Well I am not the plugin developer. Which is why we have this thread....

[senorrelentless]

Any news?

[senorrelentless]

Bah.... reopened.

[armanso]

I do see this error as well; it usually happens with a fresh install of my app.

[This message has been written by a human being]

[Famous-guy]

whats the new error?

[vilorel]

Any news? I came across it too...

Here are the details:
[ERROR:flutter/shell/common/shell.cc(1055)] The 'health_kit_reporter_event_channel_observer_query' 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.

[senorrelentless]

Same for me....

…

On Mon, Jul 29, 2024 at 6:24 PM vilorel ***@***.***> wrote: Any news? I came across it too... Here are the details: [ERROR:flutter/shell/common/shell.cc(1055)] The 'health_kit_reporter_event_channel_observer_query' 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. — Reply to this email directly, view it on GitHub <#68 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AZTNFJL4ELCKTVUCSTBGDWTZOZUENAVCNFSM6AAAAABK5MK7SSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJWGM3TKOBZGE> . You are receiving this because you modified the open/close state.Message ID: ***@***.***>