<?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 identifyLayers crash in Qt Maps SDK Questions</title>
    <link>https://community.esri.com/t5/qt-maps-sdk-questions/identifylayers-crash/m-p/1543715#M5312</link>
    <description>&lt;P&gt;I found a bug in the library,&lt;/P&gt;&lt;P&gt;by using enclayers for s57, when using identifyLayers for searching objects represented in the map a crash occurs.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;By trying to understand if I was making something wrong, I found that the bug happens if an identifyLayers is running and the user move the map.&amp;nbsp;&lt;BR /&gt;I was able to reproduce this using arcgis V100.15 and V200.3.&lt;BR /&gt;The same happens by using identifyLayers (deprecated) or identifyLayersAsync (new method).&lt;/P&gt;&lt;P&gt;I tried to find a workaround, but there is no way to solve this. I think it should be corrected in the library:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;I tryed to intercept the begin of maps movement operation (navigatingChanged event) to protect the identifyLayers operation. but No luck&lt;/LI&gt;&lt;LI&gt;I removed all my code, just to be sure that was not a problem of mine.&amp;nbsp;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Does someone have idea to solve it?&lt;/P&gt;&lt;P&gt;In attachment there is a simple software (made with QtCreator) that issues identifyLayers requests and moves the cartography position, the crash timing is randomic but it always happens within a minute after start.&lt;/P&gt;&lt;P&gt;N.B.: I tried to contact directly the customer-care, but they answered:&lt;BR /&gt;&lt;STRONG&gt;Unfortunately, the information you provided does not appear to be a report of a bug&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;I think they answered without trying the attached source code.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 30 Sep 2024 07:07:22 GMT</pubDate>
    <dc:creator>VittorioBarulli</dc:creator>
    <dc:date>2024-09-30T07:07:22Z</dc:date>
    <item>
      <title>identifyLayers crash</title>
      <link>https://community.esri.com/t5/qt-maps-sdk-questions/identifylayers-crash/m-p/1543715#M5312</link>
      <description>&lt;P&gt;I found a bug in the library,&lt;/P&gt;&lt;P&gt;by using enclayers for s57, when using identifyLayers for searching objects represented in the map a crash occurs.&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;By trying to understand if I was making something wrong, I found that the bug happens if an identifyLayers is running and the user move the map.&amp;nbsp;&lt;BR /&gt;I was able to reproduce this using arcgis V100.15 and V200.3.&lt;BR /&gt;The same happens by using identifyLayers (deprecated) or identifyLayersAsync (new method).&lt;/P&gt;&lt;P&gt;I tried to find a workaround, but there is no way to solve this. I think it should be corrected in the library:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;I tryed to intercept the begin of maps movement operation (navigatingChanged event) to protect the identifyLayers operation. but No luck&lt;/LI&gt;&lt;LI&gt;I removed all my code, just to be sure that was not a problem of mine.&amp;nbsp;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Does someone have idea to solve it?&lt;/P&gt;&lt;P&gt;In attachment there is a simple software (made with QtCreator) that issues identifyLayers requests and moves the cartography position, the crash timing is randomic but it always happens within a minute after start.&lt;/P&gt;&lt;P&gt;N.B.: I tried to contact directly the customer-care, but they answered:&lt;BR /&gt;&lt;STRONG&gt;Unfortunately, the information you provided does not appear to be a report of a bug&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;I think they answered without trying the attached source code.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 30 Sep 2024 07:07:22 GMT</pubDate>
      <guid>https://community.esri.com/t5/qt-maps-sdk-questions/identifylayers-crash/m-p/1543715#M5312</guid>
      <dc:creator>VittorioBarulli</dc:creator>
      <dc:date>2024-09-30T07:07:22Z</dc:date>
    </item>
    <item>
      <title>Re: identifyLayers crash</title>
      <link>https://community.esri.com/t5/qt-maps-sdk-questions/identifylayers-crash/m-p/1543802#M5313</link>
      <description>&lt;P&gt;Hey&amp;nbsp;&lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/637850"&gt;@VittorioBarulli&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I think you left your API key in the example code you provided. You may want to remove that and repost the code.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 30 Sep 2024 14:53:50 GMT</pubDate>
      <guid>https://community.esri.com/t5/qt-maps-sdk-questions/identifylayers-crash/m-p/1543802#M5313</guid>
      <dc:creator>bnoble0110</dc:creator>
      <dc:date>2024-09-30T14:53:50Z</dc:date>
    </item>
    <item>
      <title>Re: identifyLayers crash</title>
      <link>https://community.esri.com/t5/qt-maps-sdk-questions/identifylayers-crash/m-p/1554018#M5358</link>
      <description>&lt;P&gt;We've confirmed this issue, thank you for pointing this out to us&amp;nbsp;&lt;a href="https://community.esri.com/t5/user/viewprofilepage/user-id/637850"&gt;@VittorioBarulli&lt;/a&gt;.&lt;/P&gt;
&lt;P&gt;We've implemented a crash prevention measure (but not a full solution) for the 200.6 release. So while your application won't crash, it will return return an empty set of results in the case where a crash would have occurred. We realize this isn't an ideal solution, and we're investigating a solution that will return the expected results.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 30 Oct 2024 21:49:25 GMT</pubDate>
      <guid>https://community.esri.com/t5/qt-maps-sdk-questions/identifylayers-crash/m-p/1554018#M5358</guid>
      <dc:creator>bnoble0110</dc:creator>
      <dc:date>2024-10-30T21:49:25Z</dc:date>
    </item>
  </channel>
</rss>

