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; } } }

100.6 LocationDisplay always null

CalebPourchot

I upgraded to 100.6 for Forms. With no other changes I started crashing when displaying the map because I set LocationDisplay.Enabled to true. However, LocationDisplay is now always null. This is on both Android and iOS.

on iOS, I have Always Enabled location permissions on and they are working because I am getting location updates.

on Android, I have location permissions on as well and they are working.

Please advise,

Caleb

Find more posts tagged with

Accepted answers

ZackAllen

Hi Caleb! Thanks for asking about this issue. This is due to a behavior change in 100.6. You must wait for the LocationDisplay of your MapView to load before enabling it and changing it's properties. You can add an event handler for the PropertyChanged event in your MapView to enable your location display once it is loaded.

MyMapView<SPAN class="punctuation token">.</SPAN>PropertyChanged <SPAN class="operator token">+</SPAN><SPAN class="operator token">=</SPAN> <SPAN class="punctuation token">(</SPAN>o<SPAN class="punctuation token">,</SPAN> e<SPAN class="punctuation token">)</SPAN> <SPAN class="operator token">=</SPAN><SPAN class="operator token">></SPAN>
<SPAN class="punctuation token">{</SPAN>
    <SPAN class="keyword token">if</SPAN> <SPAN class="punctuation token">(</SPAN>e<SPAN class="punctuation token">.</SPAN>PropertyName <SPAN class="operator token">==</SPAN> <SPAN class="token function">nameof</SPAN><SPAN class="punctuation token">(</SPAN>MyMapView<SPAN class="punctuation token">.</SPAN>LocationDisplay<SPAN class="punctuation token">)</SPAN> <SPAN class="operator token">&&</SPAN> MyMapView<SPAN class="punctuation token">.</SPAN>LocationDisplay <SPAN class="operator token">!=</SPAN> <SPAN class="keyword token">null</SPAN><SPAN class="punctuation token">)</SPAN>
    <SPAN class="punctuation token">{</SPAN>
        <SPAN class="comment token">// Enable your location display.</SPAN>
        MyMapView<SPAN class="punctuation token">.</SPAN>LocationDisplay<SPAN class="punctuation token">.</SPAN>IsEnabled <SPAN class="operator token">=</SPAN> <SPAN class="keyword token">true</SPAN><SPAN class="punctuation token">;</SPAN>
    <SPAN class="punctuation token">}</SPAN>
<SPAN class="punctuation token">}</SPAN><SPAN class="punctuation token">;</SPAN>‍‍‍‍‍‍‍<SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

We use this pattern in our Show location history sample.

I hope that this helps,

Zack

All comments

msilvatavares

Hello guys,

I know that this is an old topic, but I'm trying to implement the functionalities of the MapView using the MVVM and even for the version 100.11, the LocationDisplay is returning null.

I would like to know if this issue was already fixed.

if so, could somebody provide some documentation/code snippet in how to initialize correctly the MapView base on MVVM implementation.

Thanks in advance,

Marcio

MichaelHamsa

This just hit me as well - I did not see anything in the release notes. Going to have to change a few things around to get this working again.

Mike...

CalebPourchot

I had it attached to the Map.MapLoaded event, so apparently that fires

before Page.OnAppearing. Is this guaranteed? Are there things that

shouldn't be touched if OnAppearing has fired, but the map isn't quite

loaded?

Thanks,

Caleb

SomeGISGuy

A slightly different/simpler approach is just to wait for the Page.OnAppearing event to fire. This event ensures the Xamarin.Forms renderers are correctly hooked up to the native underlying view. Generally I'd recommend to wait with doing too much to the MapView until this event fires.

Currently LocationDisplay isn't settable, which prevents us from linking it to the native view until that link has been established (we're hoping to make it settable so this specific change in behavior could go away). It was, believe it or not, a bug that there was an underlying native view prior to the appearing event, which caused a slew of life-cycle issues. that we now addressed in Update 6. Unfortunately you might see a couple of these behavioral changes due to us fixing this problem.

Good feedback that we should have documented this change in behavior. We'll try and get that addressed.

CalebPourchot

Thank you Zack,

I appreciate this info. It would've been great if changes like these were

well noted in the release notes. If I missed it, I apologize.

All the best,

Caleb

ZackAllen

MyMapView<SPAN class="punctuation token">.</SPAN>PropertyChanged <SPAN class="operator token">+</SPAN><SPAN class="operator token">=</SPAN> <SPAN class="punctuation token">(</SPAN>o<SPAN class="punctuation token">,</SPAN> e<SPAN class="punctuation token">)</SPAN> <SPAN class="operator token">=</SPAN><SPAN class="operator token">></SPAN>
<SPAN class="punctuation token">{</SPAN>
    <SPAN class="keyword token">if</SPAN> <SPAN class="punctuation token">(</SPAN>e<SPAN class="punctuation token">.</SPAN>PropertyName <SPAN class="operator token">==</SPAN> <SPAN class="token function">nameof</SPAN><SPAN class="punctuation token">(</SPAN>MyMapView<SPAN class="punctuation token">.</SPAN>LocationDisplay<SPAN class="punctuation token">)</SPAN> <SPAN class="operator token">&&</SPAN> MyMapView<SPAN class="punctuation token">.</SPAN>LocationDisplay <SPAN class="operator token">!=</SPAN> <SPAN class="keyword token">null</SPAN><SPAN class="punctuation token">)</SPAN>
    <SPAN class="punctuation token">{</SPAN>
        <SPAN class="comment token">// Enable your location display.</SPAN>
        MyMapView<SPAN class="punctuation token">.</SPAN>LocationDisplay<SPAN class="punctuation token">.</SPAN>IsEnabled <SPAN class="operator token">=</SPAN> <SPAN class="keyword token">true</SPAN><SPAN class="punctuation token">;</SPAN>
    <SPAN class="punctuation token">}</SPAN>
<SPAN class="punctuation token">}</SPAN><SPAN class="punctuation token">;</SPAN>‍‍‍‍‍‍‍<SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

We use this pattern in our Show location history sample.

I hope that this helps,

Zack

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

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