<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Error in telemetry - &amp;quot;Modifications to the layout engine must not be performed from a background thread...&amp;quot; in .NET Maps SDK Questions</title>
    <link>https://community.esri.com/t5/net-maps-sdk-questions/error-in-telemetry-quot-modifications-to-the/m-p/1073506#M10217</link>
    <description>&lt;P&gt;We see the following crash error on occasion from 100.10. We haven't shipped our app with 100.11 yet, so we don't have any telemetry from it yet. A note for the Runtime teams to look out for possible issues here. Let me know if you would like the full crash logs.&lt;/P&gt;&lt;P&gt;mono_handle_exception_internal&lt;BR /&gt;mini-exceptions.c, line 2782&lt;/P&gt;&lt;P&gt;SIGTRAP: Objective-C exception thrown. Name: NSInternalInconsistencyException Reason: Modifications to the layout engine must not be performed from a background thread after it has been accessed from the main thread. Native stack trace: 0 CoreFoundation 0x0000000186beb9ec F3021642-E3C0-33F8-9911-DD303A6056D0 + 1157612 1 libobjc.A.dylib 0x000000019af6eb54 objc_exception_throw + 56 2 CoreAutoLayout 0x000000019b1f1640 011F5CA5-D31B-3CDC-83C2-C7CB66064075 + 63040 3 CoreAutoLayout 0x000000019b1f1318 011F5CA5-D31B-3CDC-83C2-C7CB66064075 + 62232 4 CoreAutoLayout 0x000000019b1f0e78 011F5CA5-D31B-3CDC-83C2-C7CB66064075 + 61048 5 CoreAutoLayout 0x000000019b1ecb58 011F5CA5-D31B-3CDC-83C2-C7CB66064075 + 43864 6 UIKitCore 0x0000000189960780 CC6E5AC7-8248-35F6-8B42-2E25C93DCF0A + 17008512 7 QuartzCore 0x0000000189e65df4 461501DD-204F-3516-9F5D-BDD0BA19FDA1 + 1400308 8 QuartzCore 0x0000000189e6c398 461501DD-204F-3516-9F5D-BDD0BA19FDA1 + 1426328 9 QuartzCore 0x0000000189e776e8 461501DD-204F-3516-9F5D-BDD0BA19FDA1 + 1472232 10 QuartzCore 0x0000000189dc2d7c 461501DD-204F-3516-9F5D-BDD0BA19FDA1 + 732540 11 QuartzCore 0x0000000189decf40 461501DD-204F-3516-9F5D-BDD0BA19FDA1 + 905024 12 QuartzCore 0x0000000189ded74c 461501DD-204F-3516-9F5D-BDD0BA19FDA1 + 907084 13 libsystem_pthread.dylib 0x00000001ce688110 CD2075FF-948B-313A-8A02-E2AD1E676A74 + 53520 14 libsystem_pthread.dylib 0x00000001ce683cf8 CD2075FF-948B-313A-8A02-E2AD1E676A74 + 36088 15 libsystem_pthread.dylib 0x00000001ce67ba00 pthread_exit + 60 16 SE.Geospatial.Mobile.Viewer.iOS 0x0000000105a7a7ac _ZN7plcrash2MS5async24dwarf_cfa_state_iteratorIyxE4nextEPjPNS1_28plcrash_dwarf_cfa_reg_rule_tEPy + 84658592 17 SE.Geospatial.Mobile.Viewer.iOS 0x0000000105a10fd4 _ZN7plcrash2MS5async24dwarf_cfa_state_iteratorIyxE4nextEPjPNS1_28plcrash_dwarf_cfa_reg_rule_tEPy + 84226504 18 libsystem_pthread.dylib 0x00000001ce683c9c _pthread_start + 288 19 libsystem_pthread.dylib 0x00000001ce688880 thread_start + 8&lt;/P&gt;</description>
    <pubDate>Mon, 28 Jun 2021 22:49:48 GMT</pubDate>
    <dc:creator>JeremyBridges</dc:creator>
    <dc:date>2021-06-28T22:49:48Z</dc:date>
    <item>
      <title>Error in telemetry - "Modifications to the layout engine must not be performed from a background thread..."</title>
      <link>https://community.esri.com/t5/net-maps-sdk-questions/error-in-telemetry-quot-modifications-to-the/m-p/1073506#M10217</link>
      <description>&lt;P&gt;We see the following crash error on occasion from 100.10. We haven't shipped our app with 100.11 yet, so we don't have any telemetry from it yet. A note for the Runtime teams to look out for possible issues here. Let me know if you would like the full crash logs.&lt;/P&gt;&lt;P&gt;mono_handle_exception_internal&lt;BR /&gt;mini-exceptions.c, line 2782&lt;/P&gt;&lt;P&gt;SIGTRAP: Objective-C exception thrown. Name: NSInternalInconsistencyException Reason: Modifications to the layout engine must not be performed from a background thread after it has been accessed from the main thread. Native stack trace: 0 CoreFoundation 0x0000000186beb9ec F3021642-E3C0-33F8-9911-DD303A6056D0 + 1157612 1 libobjc.A.dylib 0x000000019af6eb54 objc_exception_throw + 56 2 CoreAutoLayout 0x000000019b1f1640 011F5CA5-D31B-3CDC-83C2-C7CB66064075 + 63040 3 CoreAutoLayout 0x000000019b1f1318 011F5CA5-D31B-3CDC-83C2-C7CB66064075 + 62232 4 CoreAutoLayout 0x000000019b1f0e78 011F5CA5-D31B-3CDC-83C2-C7CB66064075 + 61048 5 CoreAutoLayout 0x000000019b1ecb58 011F5CA5-D31B-3CDC-83C2-C7CB66064075 + 43864 6 UIKitCore 0x0000000189960780 CC6E5AC7-8248-35F6-8B42-2E25C93DCF0A + 17008512 7 QuartzCore 0x0000000189e65df4 461501DD-204F-3516-9F5D-BDD0BA19FDA1 + 1400308 8 QuartzCore 0x0000000189e6c398 461501DD-204F-3516-9F5D-BDD0BA19FDA1 + 1426328 9 QuartzCore 0x0000000189e776e8 461501DD-204F-3516-9F5D-BDD0BA19FDA1 + 1472232 10 QuartzCore 0x0000000189dc2d7c 461501DD-204F-3516-9F5D-BDD0BA19FDA1 + 732540 11 QuartzCore 0x0000000189decf40 461501DD-204F-3516-9F5D-BDD0BA19FDA1 + 905024 12 QuartzCore 0x0000000189ded74c 461501DD-204F-3516-9F5D-BDD0BA19FDA1 + 907084 13 libsystem_pthread.dylib 0x00000001ce688110 CD2075FF-948B-313A-8A02-E2AD1E676A74 + 53520 14 libsystem_pthread.dylib 0x00000001ce683cf8 CD2075FF-948B-313A-8A02-E2AD1E676A74 + 36088 15 libsystem_pthread.dylib 0x00000001ce67ba00 pthread_exit + 60 16 SE.Geospatial.Mobile.Viewer.iOS 0x0000000105a7a7ac _ZN7plcrash2MS5async24dwarf_cfa_state_iteratorIyxE4nextEPjPNS1_28plcrash_dwarf_cfa_reg_rule_tEPy + 84658592 17 SE.Geospatial.Mobile.Viewer.iOS 0x0000000105a10fd4 _ZN7plcrash2MS5async24dwarf_cfa_state_iteratorIyxE4nextEPjPNS1_28plcrash_dwarf_cfa_reg_rule_tEPy + 84226504 18 libsystem_pthread.dylib 0x00000001ce683c9c _pthread_start + 288 19 libsystem_pthread.dylib 0x00000001ce688880 thread_start + 8&lt;/P&gt;</description>
      <pubDate>Mon, 28 Jun 2021 22:49:48 GMT</pubDate>
      <guid>https://community.esri.com/t5/net-maps-sdk-questions/error-in-telemetry-quot-modifications-to-the/m-p/1073506#M10217</guid>
      <dc:creator>JeremyBridges</dc:creator>
      <dc:date>2021-06-28T22:49:48Z</dc:date>
    </item>
  </channel>
</rss>

