MapUserTrackingMode.follow is Ambiguous about map HOT 8 CLOSED

Hey - thank you very much for your kind words. No worries about asking questions.

I think the issue here is that you are either importing both MapKit and Map in the file this error occurs or neither. If you require both imports, you can use a Map. prefix to differentiate between the two different values from the two frameworks. In this case, it might make sense to change the line above to @State private var userTrackingMode = Map.MapUserTrackingMode.follow

from map.

Yeah. I tried this before contacting you, but I get another error:

Not sure what the problem is...

from map.

Okay, this is happening due to a name clash of the Map-struct inside the Map module and the Map module 😓

One workaround would be to use a custom name in your model for this one file - just for now - I will try to find a solution to this - probably by renaming MapUserTrackingMode to UserTrackingMode or getting rid of it altogether and using the MapKit one directly.

That additional file would only be the following:

import Map

typealias UserTrackingMode = MapUserTrackingMode

Then in your existing file, replace all usages of MapUserTrackingMode with UserTrackingMode

from map.

Yes this works, thanks!

from map.

Ah ah. No it does not.

I get this now:

and this is directly connected to setting userTrackingMode: $userTrackingMode with @State private var userTrackingMode: UserTrackingMode = .follow

from map.

Yes, it is because it automatically sets showsUserLocation to true, which is then creating an annotation for that user location. Please simply update your package version and this assertion should be gone.

from map.

Switching to main instead of 0.1.0 does indeed solve the problem :-) Thanks!

from map.

Hey @rderimay ! I have just opened a new PR #16 which changes the type of the userTrackingMode to the previous MapKit MKUserTrackingMode value instead of creating a new custom type for this.

What do you think about this change?

from map.