We're seeing the same crash class — all frames inside Apple's MapKit/VectorKit/Metal stack, none in our app code. With Metal API validation enabled we captured a more specific signal: -[MTLDebugDevice notifyExternalReferencesNonZeroOnDealloc:] failed assertion: "CAMetalLayer Display Drawable is being destroyed while still required to be alive by the command buffer" This points to a map view's GPU rendering surface being torn down while a frame is still in flight — a MapKit-internal Metal lifecycle issue, not something we can control from app code. Our crash data skews heavily to iOS 26 (~92%), suggesting this OS release significantly increased frequency of a pre-existing MapKit/VectorKit defect (similar reports exist going back to iOS 13). We tested several app-side mitigations (map resize timing, navigation frequency, camera/overlay update rate) without finding a reliable fix, reinforcing that this is a framework-level issue.

i am facing the same issue does anyone got any reply from apple?