I think this only occurs on Samsung phones, on Android 14.
It's a problem in our production app, but also easy to reproduce in a new Maui app (I shared my demo app here https://github.com/Felicity-R/EsriMapTest/issues).
Repro steps:
- Create a new Maui app (.Net 8 )
- Add reference to Esri Maps SDK (200.3). Add .UseArcGISRuntime() in MauiProgram and set up API key.
- Replace default controls in MainPage with a MapView - set up a basemap and load map.
- Launch the app on Android. Observe that the map loads and is interactable.
- Switch to a different Android app so your Maui app is backgrounded. Wait about 10 seconds\*.
- Switch back to the Maui app. The bug: Observe that the map is visible but won't visibly respond to interaction - is frozen. If you rotate your device (e.g. from portrait to landscape) then the map will 'wake up' and be interactable again.
- Extra info: If you have location display enabled, then the map will be blank/gray instead of just non-interactable, if the location indicator was in your extent when you backgrounded the app. Rotation still fixes it.
Possibly related to this issue someone reported in the Runtime SDK for Android: https://community.esri.com/t5/arcgis-runtime-sdk-for-android-questions/map-is-freezed-when-switching...
\* watching the logs, I know the map will be frozen after I see this message come up while backgrounded:
[Choreographer] CoreRune.SYSPERF_ACTIVE_APP_BBA_ENABLE : stop animation in background states