Go here https://developer.apple.com/download/all/ And look for Additional Tools for Xcode 27 or whatever version of Xcode you got You can download a CarPlay Simulator which in my view, is much better than the one integrated into the Simulator simply because it mimics a real life CarPlay device. You can't simulate driving but at least you can test your app. (You can simulate driving actually, I take my laptop inside my car and drive with the CarPlay Simulator open)

Oh my word, I’m so embarrassed right now. I didn’t know the Standard button was clickable! And I’ve been using CarPlay Simulator for 5 months now. Thank you dude

My God... Why they do this

Thanks for the reply I'm using the standalone CarPlay Simulator.app (from Additional Tools for Xcode, in the Hardware folder), which projects from a physically connected iPhone. Everything you linked and quoted describes the other tool, the iOS Simulator's CarPlay window I have searched the docs can't find anything on how to change the screen resolution on this standalone app. Here is a link attached to confirm on which app I'm talking about. Ta https://myimgs.org/image/FLid0BSX

Ah, It makes sense now. Thank you. Standard mode works spot on

Yes, I'll fill out a bug report. It does depend on the zoom level, if you are zoomed out, it nicely shows the traffic layer above the MapPolyline. However, once you zoom in, it shows the traffic layer underneath the MapPolyline instead (depending on where you are testing this). I found this because my app is a navigation app for vehicles, so zooming out is not helpful since users need to see the roads up close. Thanks for getting back to me and confirming that this is a bug.

was meant to say MapPolyline is still rendered above the traffic layer*. Sorry

Yes, I'm familiar with that, but it's not applicable here. No errors are thrown. You can go back and retry hundreds of times and nothing changes, which tells me the issue isn't on my side but rather something failing in Apple's processing pipeline

Yes... I'm familiar with that, but it's not applicable here. No errors are thrown. You can go back and retry hundreds of times and nothing changes, which tells me the issue isn't on my side but rather something failing in Apple's processing pipeline... or it may take even longer to process?