MapKit is logging messages..

Question

Mike_T OP

Created Nov ’16

Replies 5

Boosts 1

Views 2.0k

Participants 5

I keep getting this message in my Xcode console when I'm running my app. I assume it is coming from MapKit.

Calling IOPPFGetProperty thermally_optimized_maps!

Interestingly, A Google search with that string turns up nothing, not a single search result, so I'm assuming that I'm the only one getting it.

I'm working on a Sierra app and I have a MapView in my document view. That message is logged the first time the MapView appears on screen and it appears to happen only once during the app life cycle. I can't find it in the Console.app logs.

For now I'm just ignoring it as the MapView appears to be working fine. If there is a way to suppress it though, I'd like to know how to do it.

Boost

Answer 1

cliffr OP

Nov ’16

Im seeing it too. I use MapKit in my Mac App.

1

Answer 2

jancornelissen OP

Apr ’17

Me too. Looks like it has something to do with the CPU or a CPU instruction of your machine. At least that's what Google indicates when searching for IOPPF or thermally_optimized_maps.

0

Answer 3

andrewbuilder OP

Jun ’20

Using MBP, macOS 10.15.5, Xcode 11.5 (11E608c).

Writing SwiftUI for macOS 10.15 deployment target.

SwiftUI, using MapKit with NSViewRepresentable.

Also seeing the same error message.

(Incidentally also see the same error messages in the macOS app in SwiftUI tutorial Creating a macOS app.

Console error... at breakpoint...

Calling IOPPFGetProperty thermally_optimized_maps!

Then console dumps a huge number of these messages...

=== AttributeGraph: cycle detected through attribute xx ===

[SwiftUI] NSHostingView is being laid out reentrantly while rendering its SwiftUI content. This is not supported and the current layout pass will be skipped.

Issue Navigator under Runtime (only this 1 issue)...

runtime: SwiftUI: NSHostingView is being laid out reentrantly while rendering its SwiftUI content. This is not supported and the current layout pass will be skipped.

Copied from the Debug Navigator...

Thread 7 Queue : com.apple.CoreAnalytics::Client (serial)

#0 0x00007fff6f3da1ac in __cxa_begin_catch ()

#1 0x00007fff4f962dbf in FrameworkConfiguration::init() ()

#2 0x00007fff4f962a98 in FrameworkConfiguration::create(applesauce::xpc::object) ()

#3 0x00007fff4f962742 in CoreAnalytics::Client::handleConfigurationChange_sync(applesauce::xpc::dict const&) ()

#4 0x00007fff4f962542 in CoreAnalytics::Client::handleServerMessage_sync(applesauce::xpc::dict) ()

#5 0x00007fff4f9748cf in ___ZZN13CoreAnalytics6Client4initEvENK3$_1clEv_block_invoke ()

#6 0x00007fff722ee2bc in _xpc_connection_call_event_handler ()

#7 0x00007fff722ed1cb in _xpc_connection_mach_event ()

#8 0x00000001004f28c6 in _dispatch_client_callout4 ()

#9 0x000000010050fbcc in _dispatch_mach_msg_invoke ()

#10 0x00000001004f9be6 in _dispatch_lane_serial_drain ()

#11 0x0000000100510f6c in _dispatch_mach_invoke ()

#12 0x00000001004f9be6 in _dispatch_lane_serial_drain ()

#13 0x00000001004fab90 in _dispatch_lane_invoke ()

#14 0x0000000100507fe0 in _dispatch_workloop_worker_thread ()

#15 0x0000000100580361 in _pthread_wqthread ()

#16 0x000000010057f49b in start_wqthread ()

0

Answer 4

ChristianVirtual OP

Jan ’21

Get the same still on BigSur 11.1 on MBP using Xcode 12.3 ...

0

Answer 5

ChristianVirtual OP

Jan ’21

When I read about reentry, I thought maybe try to put it into a dispatch on main in async block

Code Block       let region = MKCoordinateRegion(center: visibleArea.coordinate,
                                                latitudinalMeters: 500, longitudinalMeters: 500)
      mapView.mapType = .hybrid
      DispatchQueue.main.async
      {
         mapView.setRegion(region, animated: true)
      }

It remove the violet warning message in Xcode 12.3 and also don't overload the console with redundant messages.
Its a workaround and I hope that our dear Apple Dev find the real cause and a better fix

0