Map loading very slow in Xamarin

[SinanSinan]

Hi,

I created a simple ArcGIS App with Xamarin.Forms in Visual Studio 2015( Default template 'ArcGIS Runtime App(Xamarin.Forms.Shared)' ). I added Topography map as basemap. If i run the app, the map can be loaded successfully but if i zoom in, map can not be loaded properly cause it’s so slow. After approximately 1 minute, it is fully loaded. Even if i preview the code on mobile device, there’s no change, stil slow. But when i code this in Java environment, it is perfect. I have added my screen capture video.

How can i fix this?

My environment:

Visual Studio 2015

ArcGIS Runtime 100 .Net SDK

Xamarin.forms

Thanks in advance,

Sinan

[OleNowak]

Hi,

I've got the same problems here. Just startet with a new Visual Studio Project based on the Template "ArcGIS Runtime App(Xamarin.Forms.Shared)".

On my Android devices the tiles are loaded very slowly, if at all.

And if I continue panning, zooming, panning again... the app will freeze and crash finally.

It seems to be an Android problem because I couldn't reproduce it on iOS devices. There the map is a lot faster and the tiles were loaded correctly.

I reported this issue to Esri support. I'll keep you up to date.

Regards

Ole

[SinanSinan]

Thank you @Ole,

I waiting your answer.

I tried in iOS, you're right, it faster than Android.

I hope it can be solve as soon as

Regards

Sinan

[KostaBidoshi]

Ole,

We are experiencing the same problem as you and Sinan. Any answer from ESRI Support that you can share here.

Thanks,

Kosta

[dotMorten_esri]

Thank you for sharing the video. That's very helpful to understand what you're seeing.

Could you try and repeat it without the debugger attached? Will the tiles load much faster in that case?

[OleNowak]

Hi,

Compiling the app in release mode doesn't help. The tiles are loaded slowly until the app freezes finally.

I know that Esri Inc. is working on this issue. Hope it will be fixed in the following release of Runtime SDK.

I don't have any release date. Keep on waiting...

Regards

Ole

[dotMorten_esri]

I didn't mean release mode. I meant, run with debugging in Visual Studio. "Debug -> Start without debugging", or "CTRL+F5", or just launch the app directly from the device outside VS.

We are aware of the slow loading of tiles when the debugger is attached. It was an explicit choice between that, or really poor zoom/pan performance while debugging. We're still hopeful we can work around a problem in how Visual Studio creates a huge debugging overhead, so we can get comparable performance to running without debugging, but don't have a solution just yet. 

Just to be clear: Only the developer would see this while debugging, and it won't happen in production on Android.

[NicholasDang]

I am also noticing that the map rendering is significantly slower in Android devices compared to IOS.  The rendering times get better with more powerful phones, obviously.  Would love to know if/when this does get fixed.

[dotMorten_esri]

Just to confirm: You're seeing this _without_ the Visual Studio or Xamarin Studio debugger attached to your Android device?

[ChadYoder1]

I've been watching this thread and similar to monitor things as we have long thought there is a significant difference between the Android vs. iOS (and even UWP) rendering.  iOS seems the best, UWP next, then Android.

We have delivered apps that are installed on multiple Android devices running different versions of Android and the general rendering, particularly of the base maps seems much slower.  These are apps loaded from an APK, so there is definitely not a debugger attached.

In some cases, we struggled because clients were using AirWatch/VMWare tunneling, but with or without the tunneling, the rendering seems slower.

Anything we can do to help, let me know.  We have an APK version and AdHoc/TestFlight version we could share for your review and testing.  Although it should be pretty simple to create a test app to use for analysis on the different platforms.