[Bug]: addClickListener not triggered when app is killed

[Debabrataroy]

What happened?

OneSignal.Notifications.addClickListener does not fire on the push notification tap when the app is killed (android).
Also, I run in release mode but the result is the same.

Here are the logs when I run in release mode.
W/FlutterJNI(19398): Tried to send a platform message to Flutter, but FlutterJNI was detached from native C++. Could not send. Channel: OneSignal#notifications. Response ID: 35
W/FlutterJNI(19398): Tried to send a platform message to Flutter, but FlutterJNI was detached from native C++. Could not send. Channel: OneSignal#notifications. Response ID: 14
W/FlutterJNI(19398): Tried to send a platform message to Flutter, but FlutterJNI was detached from native C++. Could not send. Channel: OneSignal#notifications. Response ID: 9

Package Info:
onesignal_flutter:
dependency: "direct main"
description:
name: onesignal_flutter
url: "https://pub.dev"
source: hosted
version: "5.1.0"

Let me know if you need anything else.
Thanks

Steps to reproduce?

1. kill the app
2. click on the received notification

What did you expect to happen?

addClickListener should be triggered when app open

OneSignal Flutter SDK version

5.1.0

Which platform(s) are affected?

• iOS
• Android

Relevant log output

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[mwaqassatti]

I'm also facing the same issue, did any one found the solution!

[nan-li]

Hi @Debabrataroy and @mwaqassatti thank you for reporting.
You are seeing this "Tried to send a platform message to Flutter, but FlutterJNI was detached from native C++. Could not send" error every time notification is clicked from an app killed state? Or only sometimes?

Can you share your flutter doctor?

[margherital]

Hi @nan-li ! I am facing the same issue. I get the error you mentioned every time a notification is clicked from the app in killed state. If I kill the app again and send a new notification I get the same error multiple times.

This is what I got after 3 notifications:

W/FlutterJNI(11668): Tried to send a platform message to Flutter, but FlutterJNI was detached from native C++. Could not send. Channel: OneSignal#notifications. Response ID: 16
W/FlutterJNI(11668): Tried to send a platform message to Flutter, but FlutterJNI was detached from native C++. Could not send. Channel: OneSignal#notifications. Response ID: 17
W/FlutterJNI(11668): Tried to send a platform message to Flutter, but FlutterJNI was detached from native C++. Could not send. Channel: OneSignal#notifications. Response ID: 9
W/FlutterJNI(11668): Tried to send a platform message to Flutter, but FlutterJNI was detached from native C++. Could not send. Channel: OneSignal#notifications. Response ID: 18
W/FlutterJNI(11668): Tried to send a platform message to Flutter, but FlutterJNI was detached from native C++. Could not send. Channel: OneSignal#notifications. Response ID: 10
W/FlutterJNI(11668): Tried to send a platform message to Flutter, but FlutterJNI was detached from native C++. Could not send. Channel: OneSignal#notifications. Response ID: 9

This is my flutter doctor:

Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 3.19.6, on Microsoft Windows [Versione 10.0.22631.3593], locale it-IT)
[√] Windows Version (Installed version of Windows is version 10 or higher)
[√] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
[√] Chrome - develop for the web
[√] Visual Studio - develop Windows apps (Visual Studio Community 2022 17.6.4)
[√] Android Studio (version 2022.1)
[√] VS Code (version 1.89.1)
[√] Connected device (4 available)
[√] Network resources

Do you have any updates?

[ihijazi]

Been having similar behavior, not only on cold start.

My app uses some native code for some other SDK. The other SDK had GeneratedPluginRegistrant.register(with: "xxx"), and it was placed AFTER GeneratedPluginRegistrant.register(with: self).

The GeneratedPluginRegistrant.register(with: self) has to be at the very end, for both Android and iOS.

example for swift:

        GeneratedPluginRegistrant.register(with: xxx)
        
        GeneratedPluginRegistrant.register(with: self) // this has to be at the very end

        return super.application(application, didFinishLaunchingWithOptions: launchOptions)
    }

Tested with latest 5.2.2 and working fine.. all handlers as expected.

Hope this helps someone.

[abishekmuthian]

W/FlutterJNI( 4474): Tried to send a platform message to Flutter, but FlutterJNI was detached from native C++. Could not send. Channel: OneSignal#notifications. Response ID: 64

Have been facing the same issue with onesignal_flutter: ^5.3.4

Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.35.2, on Fedora Linux 42 (Workstation Edition) 6.16.3-200.fc42.x86_64, locale en_US.UTF-8)
[✓] Android toolchain - develop for Android devices (Android SDK version 36.1.0-rc1)
[✓] Chrome - develop for the web
[✓] Linux toolchain - develop for Linux desktop
[✓] Android Studio (version 2023.2)
[✓] VS Code (version 1.103.2)
[✓] Connected device (4 available)
[✓] Network resources

• No issues found!

Edit:

I'm trying to navigate the user to a particular region in the app based on the notification and this bug doesn't let it happen during cold start.

I would be happy to test the fix and share results.

[nan-li]

Hi @abishekmuthian does your app use any native code?

[abishekmuthian]

@nan-li Thanks for getting back. No native code, It's pure flutter app.

[anjana1904]

@abishekmuthian, I faced the same issue where addClickListener was not triggered when the app was killed.

What worked for me was:

1. Making sure addClickListener is registered as early as possible during app startup, before calling runApp().
2. Marking the notification click handler with @pragma("vm:entry-point")

Version: 5.3.5

Future initializeOneSignal() async {
if (_isInitialized) return;

OneSignal.initialize(oneSignalAppId);

await OneSignal.Notifications.requestPermission(true);

OneSignal.Notifications.addClickListener(_handleNotificationClick);

_isInitialized = true;
}

@pragma("vm:entry-point")
void _handleNotificationClick(OSNotificationClickEvent event) {
final data = event.notification.additionalData;

if (data != null && data.isNotEmpty) {
_handleNotificationNavigation(data);
}
}

[fadi-george]

@abishekmuthian does anjana's suggestion help you?

[fadi-george]

@Debabrataroy Should work for release mode for latest version.

[abishekmuthian]

@abishekmuthian does anjana's suggestion help you?

I will test and update soon