Observation feedback loop on simple Map() view declaration

Question

Created Jul ’25

Replies 2

Boosts 3

Participants 3

Project minimum iOS deployment is set to 16.4. When running this simple code in console we receive "Observation tracking feedback loop detected!" and map is unusable.

Run code:

Map(coordinateRegion: .constant(.init()))

Console report:

...
Observable object key path '\_UICornerProvider.<computed 0x00000001a2768bc0 (Optional<UICoordinateSpace>)>' changed; performing invalidation for [layout] of: <_TtGC7SwiftUI21UIKitPlatformViewHostGVS_P10$1a57c8f9c32PlatformViewRepresentableAdaptorGV15_MapKit_SwiftUI8_MapViewGSaVS2_P10$24ce3fc8014AnnotationData____: 0x10acc2d00; baseClass = _TtGC5UIKit22UICorePlatformViewHostGV7SwiftUIP10$1a57c8f9c32PlatformViewRepresentableAdaptorGV15_MapKit_SwiftUI8_MapViewGSaVS3_P10$24ce3fc8014AnnotationData____; frame = (0 0; 353 595); anchorPoint = (0, 0); tintColor = UIExtendedSRGBColorSpace 0.333333 0.333333 0.333333 1; layer = <CALayer: 0x12443a430>>
Observable object key path '\_UICornerProvider.<computed 0x00000001a2768bc0 (Optional<UICoordinateSpace>)>' changed; performing invalidation for [layout] of: <_MapKit_SwiftUI._SwiftUIMKMapView: 0x10ae8ce00; frame = (0 0; 353 595); clipsToBounds = YES; autoresize = W+H; layer = <CALayer: 0x113beb7e0>>
Observable object key path '\_UICornerProvider.<computed 0x00000001a2768bc0 (Optional<UICoordinateSpace>)>' changed; performing invalidation for [layout] of: <_MapKit_SwiftUI._SwiftUIMKMapView: 0x10ae8ce00; frame = (0 0; 353 595); clipsToBounds = YES; autoresize = W+H; layer = <CALayer: 0x113beb7e0>>
Observable object key path '\_UICornerProvider.<computed 0x00000001a2768bc0 (Optional<UICoordinateSpace>)>' changed; performing invalidation for [layout] of: <_MapKit_SwiftUI._SwiftUIMKMapView: 0x10ae8ce00; frame = (0 0; 353 595); clipsToBounds = YES; autoresize = W+H; layer = <CALayer: 0x113beb7e0>>
Observation tracking feedback loop detected! Make a symbolic breakpoint at UIObservationTrackingFeedbackLoopDetected to catch this in the debugger. Refer to the console logs for details about recent invalidations; you can also make a symbolic breakpoint at UIObservationTrackingInvalidated to catch invalidations in the debugger. Object receiving repeated [layout] invalidations: <_TtGC7SwiftUI21UIKitPlatformViewHostGVS_P10$1a57c8f9c32PlatformViewRepresentableAdaptorGV15_MapKit_SwiftUI8_MapViewGSaVS2_P10$24ce3fc8014AnnotationData____: 0x10acc2d00; baseClass = _TtGC5UIKit22UICorePlatformViewHostGV7SwiftUIP10$1a57c8f9c32PlatformViewRepresentableAdaptorGV15_MapKit_SwiftUI8_MapViewGSaVS3_P10$24ce3fc8014AnnotationData____; frame = (0 0; 353 595); anchorPoint = (0, 0); tintColor = UIExtendedSRGBColorSpace 0.333333 0.333333 0.333333 1; layer = <CALayer: 0x12443a430>>
Observation tracking feedback loop detected! Make a symbolic breakpoint at UIObservationTrackingFeedbackLoopDetected to catch this in the debugger. Refer to the console logs for details about recent invalidations; you can also make a symbolic breakpoint at UIObservationTrackingInvalidated to catch invalidations in the debugger. Object receiving repeated [layout] invalidations: <_MapKit_SwiftUI._SwiftUIMKMapView: 0x10ae8ce00; frame = (0 0; 353 595); clipsToBounds = YES; autoresize = W+H; layer = <CALayer: 0x113beb7e0>>

IDE: Xcode 26 Beta 3 Testing device: iPhone 15 Pro iOS 26 Beta 3 MacOS: Tahoe 26 Beta 3

Boost

Answer 1

kamilochel OP

Jul ’25

I'm facing a similar issue in my project.

Upon launching the app I'm getting similar Layout invalidations as @Jokerjko - except relating to my UIWindow

Map is not yet present anywhere in view hierarchy at this point, however as soon as I open a screen containing a Map(selection:scope:), the app hangs indefinitely, hammering a single core, and leaking memory: going up to over 1 gig within two minutes. Using Instruments I was able to track most of the activity to MKMapView _updateAttribution (with _layoutAttribution taking up 90% of the cpu time), followed by MKMapView _setPreferredConfiguration:onInit: _updateCartographicConfigurationOnInit:

Observable object key path '\_UICornerProvider.<computed 0x000000018527ffd8 (Optional<UICoordinateSpace>)>' changed; performing invalidation for [layout] of: <_MapKit_SwiftUI._SwiftUIMKMapView: 0x107909c00; frame = (0 0; 440 873); clipsToBounds = YES; autoresize = W+H; layer = <CALayer: 0x600000cc4ed0>>
Observable object key path '\_UICornerProvider.<computed 0x000000018527ffd8 (Optional<UICoordinateSpace>)>' changed; performing invalidation for [layout] of: <_TtGC7SwiftUI21UIKitPlatformViewHostGVS_P10$1d9259ab432PlatformViewRepresentableAdaptorGV15_MapKit_SwiftUI15MapBridgingViewV10Foundation4UUIDOs5Never___: 0x11e293d90; baseClass = _TtGC5UIKit22UICorePlatformViewHostGV7SwiftUIP10$1d9259ab432PlatformViewRepresentableAdaptorGV15_MapKit_SwiftUI15MapBridgingViewV10Foundation4UUIDOs5Never___; frame = (0 0; 440 873); anchorPoint = (0, 0); tintColor = UIExtendedSRGBColorSpace 1 1 1 1; layer = <CALayer: 0x600000cf4cc0>>
Observable object key path '\_UICornerProvider.<computed 0x000000018527ffd8 (Optional<UICoordinateSpace>)>' changed; performing invalidation for [layout] of: <_MapKit_SwiftUI._SwiftUIMKMapView: 0x107909c00; frame = (0 0; 440 873); clipsToBounds = YES; autoresize = W+H; layer = <CALayer: 0x600000cc4ed0>>
Observable object key path '\_UICornerProvider.<computed 0x000000018527ffd8 (Optional<UICoordinateSpace>)>' changed; performing invalidation for [layout] of: <_MapKit_SwiftUI._SwiftUIMKMapView: 0x107909c00; frame = (0 0; 440 873); clipsToBounds = YES; autoresize = W+H; layer = <CALayer: 0x600000cc4ed0>>
Observable object key path '\_UICornerProvider.<computed 0x000000018527ffd8 (Optional<UICoordinateSpace>)>' changed; performing invalidation for [layout] of: <_MapKit_SwiftUI._SwiftUIMKMapView: 0x107909c00; frame = (0 0; 440 873); clipsToBounds = YES; autoresize = W+H; layer = <CALayer: 0x600000cc4ed0>>

Tested on both Xcode 26 beta 3, and Xcode 16.4, on iOS Simulator 26.0 (23A5287g) and iPhone 15 Pro Max running iOS 26.0 (23A5297i).

1

Answer 2

diego.trevisan OP

4w

This issue began in iOS 26 Beta 3 and is still present in Beta 4. I reported it in FB18748908 a couple weeks ago, but there is no response yet.

It is also reported here: https://developer.apple.com/forums/thread/792820

I'd love to find a solution (yet if a temporary workaround) to fix this.

0