Putting the app on background and resuming may lead in a white map

[VuillaumeGautier]

Hello !

On a low perfomance phone, putting the app on background, and resuming it afterward may result in the map widget being completly white.

This happens on a Samsung Galaxy A40, Android 11 and a Oppo A9, both being slow phones. Seemingly no issue on iOS or Samsung Galaxy S20 with Android 12.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[ranjithbobby89]

any update on the above issue? any fixes?

[VuillaumeGautier]

Seems to be still happening. No idea what to do to reproduce the exact bug. It can happen on any device.
It also happens occasionally when poping a route to the screen containing the map.
No workaround, no bug hint and no reproducible path yet on our side.

[ranjithbobby89]

yeah, we can place the Mapbox on the resume state and open the native camera or any new app then instead of clicking a recent button and opening Mapbox it goes blank white screen.

[ranjithbobby89]

#1218 , #1277

[ranjithbobby89]

@VuillaumeGautier any update on the issue still facing the mapbox vanish issue? You're able to reproduce the issue at mentioned above steps.

Thanks!

[steveneal]

This is affecting our users too... any updates please ????

[srmncnk]

AFAIR we put the map in an lifecycle observable and disposed its controller as soon as app got out of focus. And when in focus, we triggered map rebuild to get a new controller. Worked well.

[steveneal]

AFAIR we put the map in an lifecycle observable and disposed its controller as soon as app got out of focus. And when in focus, we triggered map rebuild to get a new controller. Worked well.

@srmanc

Can you share more details of your work-around this please?

I've been trying things like this for a couple of days now and am getting nowhere.

[sKY02644]

@steveneal did you get a solution please #1339 i am facing similar issue kindly assist @srmncnk

[sKY02644]

@srmncnk can you tell how you fixed it please

[srmncnk]

@sKY02644 @steveneal Not sure if you have the same issue, but we went like this.

1. First problem is that you shouldn't do anywhing with the map once it's out of focus. Bad things happen on Android with it. So we put a Lifecycle observer and as soon as map was out of focus (when switching between apps and also when you pull down a system menu), it should be disposed and recreated, once map is in focus again.

2. Second problem with Flutter 3.x was a disposal bug - native code was touching the widget source after it was disposed. There was a workaround with the delayed disposal from me, but the real fix was from @felix-ht who dove into the framework and found the correct fix: Fix flutter 3.x crashes #1293

[sKY02644]

@srmncnk can you assist me to implement that i am unable to do it currently

[srmncnk]

You should be fine if you use version from master. @sKY02644

[sKY02644]

@srmncnk okay will give it a try and let you know before close of work today thank you

[sKY02644]

@srmncnk thanks soo far soo good everything is working fine