Julian Aßmann

I have a similiar problem: My `darkTheme` is as follows: ```dart NeumorphicThemeData.dark( accentColor: Colors.lightBlueAccent, defaultTextColor: Colors.white, lightSource: LightSource.topLeft, shadowLightColor: Colors.red, // for better visibility in the image below shadowLightColorEmboss: Colors.grey[700],...

You can wrap you modal widget in a `WillPopScope`: ```dart WillPopScope( onWillPop: () async { // TODO }, child: Scaffold( // ... ) ) ``` However, this will not differentiate...

Mmh interesting, I will investigate the issue when I have the time.

It's a bit weird, because as you said we already terminate the foreground service when the user swipes up, so I thought the app would be completely closed and terminated...

On which phone did you test this on?

Strange. I'm explicitly setting the WakeLock not to be referenced counted: https://github.com/JulianAssmann/flutter_background/blob/8f2dec361990d0e119701fd191ad641dc1d664f7/android/src/main/kotlin/de/julianassmann/flutter_background/IsolateHolderService.kt#L77 So one call to `release()` should release the WackeLock no matter how many `acquire()` calls there were prior...

Which version did you use and is the problem fixed in the latest version?

Unfortunately, I currently have no Android TV available for testing and therefore also no experience with developing for it. So I need help to solve this problem.

I'm currently not able to run an Android TV emulator, presumably because I'm on an Apple M1 Macbook. But if the plugin works under Android for Phones, there is probably...

@slowisfast168 @DanielusG Can you check if that error still exists with the current version (v. 1.1.0) and let me know?