I'm trying to understand why App Preview uploads are stuck in this state even after 24 hours without any errors thrown My current video has the following specs which follows Apple requirements for Video Specifications for App previews. Video codec: H.264 High Profile Level 4.0 — meets requirement Resolution: 886×1920 — correct for 6.9" Frame rate: ~28.9 fps (under 30) — meets requirement Format: MP4 — meets requirement Duration: 28.08s (under 30s) — meets requirement Audio codec: AAC — meets requirement Audio bitrate: 256kbps — meets requirement Audio sample rate: 44.1kHz — meets requirement Audio channels: stereo — meets requirement

Anyone worked with MapKit's MapCameraPosition in SwiftUI? I'm building a navigation app and ran into a limitation I can't find a clean solution for when using .userLocation(followsHeading: true) MapKit takes full control of the camera, smooth heading tracking, follows the user automatically. Perfect. But there's no way to set a custom pitch (tilt) on it. The only initializer available is... .userLocation(followsHeading: true, fallback: .automatic) No pitch, no distance parameters.... The workaround I found is setting .camera(MapCamera(..., pitch: 60)) first, waiting 200ms, then switching to .userLocation(followsHeading: true), MapKit inherits the pitch from the rendered camera state before handing off to user tracking.... It works, but it's clearly exploiting an undocumented behaviour in MapKit's state machine rather than a proper API Has anyone found a cleaner way to achieve this? Or is UIViewRepresentable wrapping MKMapView the only proper solution? It would be awesome to have something like this cameraPosition = .userLocation( followsHeading: true, pitch: 60, distance: 800, fallback: .automatic )

MapKit offers showsTraffic: Bool, which is great for displaying live traffic data on the map. However, MapPolyline sits above it, which makes it quite useless. Is this the expected behaviour?