Isolate name in the call stack shown as main in vs code

[abdimussa87]

Whenever I try and run the example code, the call stack found in the debug panel shows it being main and not the isolate name. Is this on purpose? I tried using the inbuilt Isolate.spawn and it does show the method name in the call stack. Is there a way to programmatically check if the method to be called in the isolate is indeed being called from the isolate or the main thread?

[deakjahn]

Frankly, now that this plugin is no longer necessary because, starting from Flutter 3.7, isolates and even background isolates can directly use plugins, I didn't pay attention. I guess I'd need to mark it obsolete... Although, the "handler" part still has advantages.

[abdimussa87]

There's this function in FlutterLocalNotifications plugin that cancels all scheduled notifications _flutterLocalNotification.cancelAll();. Whenever I try to run this function in either an isolate or on the main, it keeps hanging the UI. I was wondering how this can be resolved