<?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: Could not build for iOS since upgrading to 200.8.1 - Could not find part of the path in .NET Maps SDK Questions</title>
    <link>https://community.esri.com/t5/net-maps-sdk-questions/could-not-build-for-ios-since-upgrading-to-200-8-1/m-p/1691631#M13895</link>
    <description>&lt;P&gt;You're most likely hitting a max-path issue with Windows. The quick fix is to place your source code in a folder close to the root to avoid this, or look into some of the Windows settings to better handle long path filenames:&amp;nbsp;&lt;A href="https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=registry#registry-setting-to-enable-long-paths" target="_blank"&gt;https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=registry#registry-setting-to-enable-long-paths&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For what it's worth we agree the filenames has gotten a bit long, so in the next major update we've significantly reduced the filepath length, so it'll be much less likely that you'll hit this Windows limitation.&lt;/P&gt;</description>
    <pubDate>Fri, 20 Mar 2026 01:03:11 GMT</pubDate>
    <dc:creator>dotMorten_esri</dc:creator>
    <dc:date>2026-03-20T01:03:11Z</dc:date>
    <item>
      <title>Could not build for iOS since upgrading to 200.8.1 - Could not find part of the path</title>
      <link>https://community.esri.com/t5/net-maps-sdk-questions/could-not-build-for-ios-since-upgrading-to-200-8-1/m-p/1691623#M13894</link>
      <description>&lt;P&gt;Warning MSB3026: Could not copy "...\esri.arcgisruntime.ios\200.8.1\resources\shaders\arm64\rt_tile_draw_v_square_grid_bgnd_v_terr_occ_on_v_nodecal_v_vsclip_ps.metallib" to "...\Local\Temp\Xamarin\HotRestart\Signing\{app name}.app\out\Payload\{app name}.app\{app name}.content \RuntimeCoreNet\resources\shaders\rt_tile_draw_v_square_grid_bgnd_v_terr_occ_on_v_nodecal_v_vsclip_ps.metallib". &lt;STRONG&gt;Could not find a part of the path&lt;/STRONG&gt; '...\Local\Temp\Xamarin\HotRestart\Signing\{app name}.app\out\Payload\{app name}.app\{app name}.content \RuntimeCoreNet\resources\shaders\rt_tile_draw_v_square_grid_bgnd_v_terr_occ_on_v_nodecal_v_vsclip_ps.metallib'.&lt;/P&gt;&lt;P&gt;Since upgrading to 200.8.1 from 200.7.0 of ArcGIS runtime, I have been unable to build for iOS in Visual Studio with the above error. In my ...\RuntimeCoreNet\resources\shaders\ folder I see that its missing all the shaders with the '_nodecal' prefix. The "_nodecal" shaders don't seem to be present in 200.7.0 so I assume its added in 200.8. I tried clearing my Temp and .nuget folders but it didn't resolve the issue. I'm using .NET ver. 9.0.311 with Maui version 9.0.120.&lt;/P&gt;&lt;P&gt;Could someone help me figure out whether this is an issue with ArcGIS, Visual Studio, or my setup ? Thank you.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 20 Mar 2026 00:12:44 GMT</pubDate>
      <guid>https://community.esri.com/t5/net-maps-sdk-questions/could-not-build-for-ios-since-upgrading-to-200-8-1/m-p/1691623#M13894</guid>
      <dc:creator>EricLiu</dc:creator>
      <dc:date>2026-03-20T00:12:44Z</dc:date>
    </item>
    <item>
      <title>Re: Could not build for iOS since upgrading to 200.8.1 - Could not find part of the path</title>
      <link>https://community.esri.com/t5/net-maps-sdk-questions/could-not-build-for-ios-since-upgrading-to-200-8-1/m-p/1691631#M13895</link>
      <description>&lt;P&gt;You're most likely hitting a max-path issue with Windows. The quick fix is to place your source code in a folder close to the root to avoid this, or look into some of the Windows settings to better handle long path filenames:&amp;nbsp;&lt;A href="https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=registry#registry-setting-to-enable-long-paths" target="_blank"&gt;https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=registry#registry-setting-to-enable-long-paths&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For what it's worth we agree the filenames has gotten a bit long, so in the next major update we've significantly reduced the filepath length, so it'll be much less likely that you'll hit this Windows limitation.&lt;/P&gt;</description>
      <pubDate>Fri, 20 Mar 2026 01:03:11 GMT</pubDate>
      <guid>https://community.esri.com/t5/net-maps-sdk-questions/could-not-build-for-ios-since-upgrading-to-200-8-1/m-p/1691631#M13895</guid>
      <dc:creator>dotMorten_esri</dc:creator>
      <dc:date>2026-03-20T01:03:11Z</dc:date>
    </item>
    <item>
      <title>Re: Could not build for iOS since upgrading to 200.8.1 - Could not find part of the path</title>
      <link>https://community.esri.com/t5/net-maps-sdk-questions/could-not-build-for-ios-since-upgrading-to-200-8-1/m-p/1691731#M13896</link>
      <description>&lt;P&gt;Thanks for the workaround !&lt;/P&gt;</description>
      <pubDate>Fri, 20 Mar 2026 16:02:20 GMT</pubDate>
      <guid>https://community.esri.com/t5/net-maps-sdk-questions/could-not-build-for-ios-since-upgrading-to-200-8-1/m-p/1691731#M13896</guid>
      <dc:creator>EricLiu</dc:creator>
      <dc:date>2026-03-20T16:02:20Z</dc:date>
    </item>
  </channel>
</rss>

