<?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 Re: findAddressCandidates with magicKey drops matchId in ArcGIS Location Platform Developers Ques.</title>
    <link>https://community.esri.com/t5/arcgis-location-platform-developers-ques/findaddresscandidates-with-magickey-drops-matchid/m-p/1638406#M155</link>
    <description>&lt;P&gt;Ok thanks. For now my workaround is to not use the magicKey returned from the suggest response in the findAddressCandidates request. This will likely affect accuracy of some results so it's not ideal. Looking forward to the fix.&lt;/P&gt;</description>
    <pubDate>Fri, 01 Aug 2025 16:11:52 GMT</pubDate>
    <dc:creator>msuk1</dc:creator>
    <dc:date>2025-08-01T16:11:52Z</dc:date>
    <item>
      <title>findAddressCandidates with magicKey drops matchId</title>
      <link>https://community.esri.com/t5/arcgis-location-platform-developers-ques/findaddresscandidates-with-magickey-drops-matchid/m-p/1636498#M153</link>
      <description>&lt;P&gt;Hi team,&lt;BR /&gt;&lt;BR /&gt;I appreciate that Arcgis now returns matchId in responses. An issue I've found is that when I search with the magicKey specified, I no longer get a matchId. The same request without a magicKey returns a matchId. I have noticed this issue consistently at multiple locations, eg if you search for Eiffel Tower.&lt;/P&gt;&lt;P&gt;Please resolve as I don't see a reason as to why the matchId wouldn't be returned in this case.&lt;BR /&gt;&lt;BR /&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Fri, 25 Jul 2025 17:13:17 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-location-platform-developers-ques/findaddresscandidates-with-magickey-drops-matchid/m-p/1636498#M153</guid>
      <dc:creator>msuk1</dc:creator>
      <dc:date>2025-07-25T17:13:17Z</dc:date>
    </item>
    <item>
      <title>Re: findAddressCandidates with magicKey drops matchId</title>
      <link>https://community.esri.com/t5/arcgis-location-platform-developers-ques/findaddresscandidates-with-magickey-drops-matchid/m-p/1638120#M154</link>
      <description>&lt;P&gt;We have confirmed the issue you are seeing and will look into a fix for a future update.&lt;/P&gt;&lt;P&gt;Brad&lt;/P&gt;</description>
      <pubDate>Thu, 31 Jul 2025 17:52:11 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-location-platform-developers-ques/findaddresscandidates-with-magickey-drops-matchid/m-p/1638120#M154</guid>
      <dc:creator>BradNiemand</dc:creator>
      <dc:date>2025-07-31T17:52:11Z</dc:date>
    </item>
    <item>
      <title>Re: findAddressCandidates with magicKey drops matchId</title>
      <link>https://community.esri.com/t5/arcgis-location-platform-developers-ques/findaddresscandidates-with-magickey-drops-matchid/m-p/1638406#M155</link>
      <description>&lt;P&gt;Ok thanks. For now my workaround is to not use the magicKey returned from the suggest response in the findAddressCandidates request. This will likely affect accuracy of some results so it's not ideal. Looking forward to the fix.&lt;/P&gt;</description>
      <pubDate>Fri, 01 Aug 2025 16:11:52 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-location-platform-developers-ques/findaddresscandidates-with-magickey-drops-matchid/m-p/1638406#M155</guid>
      <dc:creator>msuk1</dc:creator>
      <dc:date>2025-08-01T16:11:52Z</dc:date>
    </item>
  </channel>
</rss>

