Luis

I had the same error described in this issue and opted to find another WebView implementation which allows me to manage certificate validation. I finally ended up using [flutter_inappwebview](https://pub.dev/packages/flutter_inappwebview) with...

Check https://github.com/letsar/flutter_slidable/issues/318

@aqinfh you can use: ```dart flutter_compass: #^0.7.0 # Here the git ref is used because current 0.7.0 forces android min sdk to be 23 git: url: https://github.com/hemanthrajv/flutter_compass.git ref: 14e134f0aed3c9fe09065bea05281f2c26f171d1 ```...

With `OneSignal#onClickNotification` happens similar, in this case as it's a manual event you have to add a listener for that event, so when calling `addClickListener(...)` it's triggering a `_channel.invokeMethod("OneSignal#addNativeClickListener");`, so...

Sure, the remove listener should be properly called, but note in my description above I'm talking about **Hot Restart** not Hot Reload, and also about the **OneSignal#onWillDisplayNotification** it doesn't matter...

The call to `OneSignal.Notifications.addForegroundWillDisplayListener(listener);` is being handled only on dart side, I mean the listener you add there will be added only to: `_willDisplayListeners.add(listener);`, later when some notification is received...

Nope, I just avoid onesignal initialization during debug unless I need to test something related to notifications which is sporadical.

Hi @nan-li and thanks for your feedback, but note that in my first comment I state **Hot Restarts** not **Hot Reloads** > The callback for _handleMethod(MethodCall call) function on OneSignalNotifications...

Hi @nan-li thanks again for you feedback and your tests, oki then we are on the same page with the **Hot Restart** _(by the way you mentioned **Hot Reloads** again...

Ok let's break this into parts: 1. **IMPORTANT**: the issue identified in this thread has nothing to do with SDK users adding/removing listeners. 2. Back to my initial comment I...