nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Map Freeze after MAUI ShareFileRequest on Samsung

pclark_3gis

Minimum reproducible repo: https://gitlab.com/pclark3/arcgisruntime-maui-freeze

Device Model: SM-T738U (Galaxy Tab S7 FE 5G)

Device Android Version: 14

Samsung One UI Version: 6.1

After using Share.Default.RequestAsync on a Samsung tablet, the MapView becomes frozen. There is a similar post to this issue but the workaround presented in that post does not work for this issue.

Thank you.

Najděte více příspěvků označených jako

Maui

Android

Accepted answers

SomeGISGuy

Yes a fix was included in v200.8.2
See release notes: https://developers.arcgis.com/net/v200/release-notes/release-notes-for-200-8/

All comments

SomeGISGuy

Yes a fix was included in v200.8.2
See release notes: https://developers.arcgis.com/net/v200/release-notes/release-notes-for-200-8/

pclark_3gis

Any update on this? For us, this means we cannot deploy the app to customers that use Samsung devices since our application makes use of the file sharing capabilities in MAUI (Share.Default.RequestAsync, MediaPicker.Default.PickPhotosAsync).

Marc_Alx

Still occuring on 200.8.1.

I did fill a case from my local vendor and have receive a BUG-000... number. Actually this bug is "in review".

What I can say is that I'm locked in 200.4.0 and thus subject to Android app rejection due to 16ko page requirements (supported by later version of ArcGIS SDK).

pclark_3gis

Yep we are still seeing this issue with 200.8.0.

SomeGISGuy

I do see our bug fix history that something like this was fixed. Are you still seeing this with 200.8.0 ?

Marc_Alx

Hi,

I'm also experiencing this issue on Samsung A35 (up to date).

To me this issue has been introduced with version 200.5.0 as I don't reproduce the bug with 200.4.0 versions.

Any news on that ?

SomeGISGuy

I'm not entirely if you're saying the above log was with replacing with a new mapview on resume? If that's the case, could you try it with just leaving the mapview alone as in the original sample you shared? (it's fine that the map is blank - but I'd like to understand if something on your device is not triggering these lifecycle events, since the MapView heavily relies on these to resume rendering).

I do find it curious so far that you are seeing destroy+create. That could be the root of how these devices behave differently. If you repeat this on a device that does work, do you see a version of mine or your log?

Lastly what does "TextureView does some things" mean?

pclark_3gis

Attached is the log file with your lifecycle logging

I began logging right before clicking the share button, and stopped logging immediately upon returning to the map. What I see on my end:

***Lifecycle.OnPause
***Lifecycle.OnStop
***Lifecycle.OnDestroy
***Lifecycle.OnCreate
***Lifecycle.OnStart
***Lifecycle.OnResume
TextureView does some things

There was no "TextureView Paused by user" or "stopping pulse" messages prior to the Lifecycle.OnPause like in your reply.

It is worth noting that I tried simply re-adding the mapview to the view hierarchy but this resulted in a blank map (with ESRI logo banner at bottom). The log files were with this commented out.

var mapView = AbsLayout.Children[0] as MapView;
AbsLayout.Children.RemoveAt(0);

AbsLayout.Children.Insert(0, mapView);
AbsoluteLayout.SetLayoutBounds(mapView, new Rect(0, 0, 1, 1));
AbsoluteLayout.SetLayoutFlags(mapView, AbsoluteLayoutFlags.SizeProportional);

samsung-log-with-lifecycle.txt

SomeGISGuy

Thanks for confirming. You shouldn't have to re-create a new MapView. Just re-insert the same one.

One more thing to also try. Could you try and add this to MainActivity?

    public class MainActivity : MauiAppCompatActivity
    {
        public MainActivity()
        {
            Lifecycle.AddObserver(new Observer());
        }

        private class Observer : Java.Lang.Object, AndroidX.Lifecycle.IDefaultLifecycleObserver, AndroidX.Lifecycle.ILifecycleObserver
        {
            void IDefaultLifecycleObserver.OnCreate(ILifecycleOwner p0) => System.Diagnostics.Debug.WriteLine("***Lifecycle.OnCreate");
            void IDefaultLifecycleObserver.OnDestroy(ILifecycleOwner p0) => System.Diagnostics.Debug.WriteLine("***Lifecycle.OnDestroy");
            void IDefaultLifecycleObserver.OnPause(ILifecycleOwner p0) => System.Diagnostics.Debug.WriteLine("***Lifecycle.OnPause");
            void IDefaultLifecycleObserver.OnResume(ILifecycleOwner p0) => System.Diagnostics.Debug.WriteLine("***Lifecycle.OnResume");
            void IDefaultLifecycleObserver.OnStart(ILifecycleOwner p0) => System.Diagnostics.Debug.WriteLine("***Lifecycle.OnStart");
            void IDefaultLifecycleObserver.OnStop(ILifecycleOwner p0) => System.Diagnostics.Debug.WriteLine("***Lifecycle.OnStop");
        }
    }

When I do this, this is what I see in the output window once the app comes back from the sharing operation. I'd be curious if that differs on your Samsung device:

[TextureView] Paused by user
[TextureView] Stopping pulse
[0:] ***Lifecycle.OnPause
[0:] ***Lifecycle.OnStop
[0:] ***Lifecycle.OnStart
[0:] ***Lifecycle.OnResume
[TextureView] Resumed by user. Texture view available: True
[TextureView] Starting pulse

pclark_3gis

I added the following code immediately after await Share.Default.RequestAsync and it does result in a fresh map that can be interacted with.

AbsLayout.Children.RemoveAt(0);
var mapView = new MapView();
mapView.Map = new Map(new Basemap([new OpenStreetMapLayer()]));

AbsLayout.Children.Insert(0, mapView);
AbsoluteLayout.SetLayoutBounds(mapView, new Rect(0, 0, 1, 1));
AbsoluteLayout.SetLayoutFlags(mapView, AbsoluteLayoutFlags.SizeProportional);

SomeGISGuy

Thank you for sharing the log. I do see the rendering stops for the mapview on share (which is expected), but I don't see a resume. As an experiment could you after sharing, try and remove the mapview from the view and re-insert it? Would that make it start up again? That would confirm if we're having some issues detecting resume.

pclark_3gis

My other devices are a Pixel 8 XL and the usual Android Studio emulators. Not a huge repertoire, but yes, currently only reproducible on my Samsung tablet (and my coworker's Samsung tablet).

Actually not sure how to upload a file here, but I did not see anything of interest in logcat. Also very possible I'm not experienced enough to find it. Here is a pastebin of the logcat from before clicking the button to after coming back to the map: https://pastebin.com/ix88Ptiz

SomeGISGuy

Do you _only_ see the issue on this device, or is it the only device you've been testing on? (what devices do you have that it worked on?)

Does LogCat give any indication of an issue with the application?

Připojte se k diskusi

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Rychlé odkazy

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.