You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 8, 2023. It is now read-only.
The addition of even one custom MGLAnnotationView make the map unusable. The attached image shows the profiler where the mapbox rendering call is taking the most of the cpu. There is only a basic map showing one custom annotation. On iOS 13 this runs butter smooth. The Map is displayed via a UIViewRepresentable in SwiftUI.
Steps to reproduce
On iOS 14, create a MGLMapView and display one custom MGLAnnotationView.
The addition of even one custom MGLAnnotationView make the map unusable. The attached image shows the profiler where the mapbox rendering call is taking the most of the cpu. There is only a basic map showing one custom annotation. On iOS 13 this runs butter smooth. The Map is displayed via a UIViewRepresentable in SwiftUI.
Steps to reproduce
Expected behavior
Map runs smooth
Actual behavior
Map is unusable slow
Configuration
The used custom MGLAnnotationView:
Mapbox SDK version: 6.0.0
iOS versions: iPad OS 14 / iOS 13.6
Device/simulator models: iPad Pro 1st Gen (iOS 14 device) / iPhone Xs (iOS 13 device)
Xcode version: 12.0 b2
The text was updated successfully, but these errors were encountered: