My issue is essentially the same described in MKUserLocation stops updating when map is touched, except for Mapkit JS. That question has been left without answer and the chat has been removed so I'm left wondering what the outcome was.

In short, I create a Mapkit JS map, I set:

        map.tracksUserLocation = true;
        map.showsUserLocation = true;

This shows and tracks the user's position on the map.

Once I pan/zoom the map map.tracksUserLocation is set to false (as it should). However the user's dot stops updating entirely as well.

I have ran some testing and it looks that if I initially only set map.showsUserLocation to true but don't specify wether the map should track the user's location, the user's dot will simply not show up at all.

I can override this behaviour by constantly setting both variables to true, but as you can imagine the experience is awful.

My code is essentially the bare basics.

      const map = new mapkit.Map('map');
      map.tracksUserLocation = true;
      map.showsUserLocation = true;


      // ...


      <div id="map" />

I'm pretty sure this isn't supposed to happen, but it seems like a very obvious issue for it to be present for 5 years on both native and JS Mapkit libraries.