Map vanishes when restart fom app-list

[Docmale]

When I open the list of background apps choosing another app and come back to 'Ehrenamt' the same way the map disappeared (black screen of one physikal device [Samsung A53; V14] , white one on the other [Samsung Note 8;V9]). The android emulator dosen't show this behaviour but sometimes crashes at this point.
I will ad ios behaviour later on.

To Reproduce
Steps to reproduce the behavior:

1. Start Ehrenamt
2. open background list
3. Choose whatever other app
4. come back to Ehrenamt the same way
5. open Map when not already open
6. find black/white screen
7. for heeling remove Ehrenamt from background list and start it again

Related to:maplibre/flutter-maplibre-gl#327
Should be fixed by this pr: maplibre/flutter-maplibre-gl#406

Update to latest maplibre release
It should be fixed by updating to https://github.com/maplibre/flutter-maplibre-gl/releases/tag/v0.20.0
Looks like kotlin plugin for android has also to be updated

Update: its not fixed by maplibre v0.20 -> Blocked, waiting for upstream fix

This bug happens on android 9 and android 14. You can upload your apk to browserstack for testing

[f1sh1918]

Hm maybe this a new Android 14 issue. I can not reproduce this on real device, but i only have Android 11
Can anyone else try to reproduce it with new store beta

[Docmale]

I see it on android9 and 14
not reproducable on emulator Pixel_3a_API_34 Android 14

[Docmale]

not reproducable on ios

[f1sh1918]

reproducable on android14 (Samsung S24 Ultra, not for Pixel 8 Pro) and android 9 on browserstack! Looks like to happen in some android versions but not in all
Looks like there is an open pr for this on flutter/maplibre
maplibre/flutter-maplibre-gl#364
I hope it will be fixed soon

It could also be fixed with impeller engine of a new flutter release. I'm gonna check this.
Impeller engine is by default enabled for ios and will be enabled also for android in flutter 3.22 which was released recently

Update: Still happens with impeller engine. So maybe we have to wait for the pr. Not sure if we can find a workaround. Looks like the mentioned open pr doesn't fix the issue. I forked it and tested :(