Error in FerrostarMapLibreUI 0.46.0: 'MapView' has no member 'mapViewContentInset'

[kabouter]

I'm encountering an issue and I am unsure if it is a configuration mistake on my end or a bug in Ferrostar. I have added Ferrostar 0.46.0 to my project, but I am receiving two errors from FerrostarMapLibreUI. The errors are:

/Users/Library/Developer/Xcode/DerivedData/fijuxxmeanbbwoflubeszlkpcwsp/SourcePackages/checkouts/ferrostar/apple/Sources/FerrostarMapLibreUI/Views/NavigationMapView.swift:75:14 Value of type 'MapView' has no member 'mapViewContentInset'

/Users/Library/Developer/Xcode/DerivedData/fijuxxmeanbbwoflubeszlkpcwsp/SourcePackages/checkouts/ferrostar/apple/Sources/FerrostarMapLibreUI/Views/NavigationMapView.swift:80:31 Cannot infer contextual base in reference to member 'all'

The code containing the error is in the NavigationMapView file, which is a package file.

ferrostar/apple/Sources/FerrostarMapLibreUI/Views/NavigationMapView.swift

Lines 59 to 82 in 4cabf20

	public var body: some View {
	GeometryReader { geometry in
	MapView(
	styleURL: styleURL,
	camera: $camera,
	locationManager: locationManager,
	activity: activity
	) {
	// TODO: Create logic and style for route previews. Unless ferrostarCore will handle this internally.
	routeConfig.routeOverlay(navigationState)
	updateCameraIfNeeded()
	// Overlay any additional user layers.
	userLayers
	}
	.mapViewContentInset(calculatedMapViewInsets(for: geometry).uiEdgeInsets)
	.mapControls {
	// No controls
	}
	.onStyleLoaded(onStyleLoaded)
	.ignoresSafeArea(.all)
	}
	}

Is this a bug or not? And if not, how can I fix it? I have already removed the package multiple times, cleared the cache, and cleaned the build folder.

[ianthetechie]

Thanks for the issue report @kabouter! This is in fact a bug caused by your use of the latest MapLibre SwiftUI DSL, like a normal person :) It looks like we broke a few things with the API upstream as part of some naming convention cleanup, so using the latest release breaks things. Our CI didn't catch it because it just uses whatever we had previously built with (0.17 in this case).

If you need this fixed right now, you can pin your MapLibre SwiftUI DSL version to 0.17.0 (or maybe a bit higher?). Otherwise, we'll get a release out pretty soon which supports the latest MapLibre version.

[ianthetechie]

Fixed in 0.46.1