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". Could not find a part of the path '...\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'.
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.
Could someone help me figure out whether this is an issue with ArcGIS, Visual Studio, or my setup ? Thank you.
Solved! Go to Solution.
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: https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=registry#re...
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.
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: https://learn.microsoft.com/en-us/windows/win32/fileio/maximum-file-path-limitation?tabs=registry#re...
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.
Thanks for the workaround !