Create Raster Dataset tool doesn't work for GDB

MaxMax2

It seems that 'Create Raster Dataset' geoprocessing tool doesn't work at all for GDB, either programmatically or not. My code:

<SPAN class="keyword token">var</SPAN> args <SPAN class="operator token">=</SPAN> Geoprocessing<SPAN class="punctuation token">.</SPAN><SPAN class="token function">MakeValueArray</SPAN><SPAN class="punctuation token">(</SPAN>datastorePath<SPAN class="punctuation token">,</SPAN> RasterDatasetName<SPAN class="punctuation token">,</SPAN> <SPAN class="keyword token">null</SPAN><SPAN class="punctuation token">,</SPAN> <SPAN class="string token">"8_BIT_SIGNED"</SPAN><SPAN class="punctuation token">,</SPAN> <SPAN class="keyword token">null</SPAN><SPAN class="punctuation token">,</SPAN> <SPAN class="number token">3</SPAN><SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">;</SPAN>
<SPAN class="keyword token">var</SPAN> env <SPAN class="operator token">=</SPAN> Geoprocessing<SPAN class="punctuation token">.</SPAN><SPAN class="token function">MakeEnvironmentArray</SPAN><SPAN class="punctuation token">(</SPAN>outputCoordinateSystem<SPAN class="punctuation token">:</SPAN> SpatialReferences<SPAN class="punctuation token">.</SPAN>WGS84<SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">;</SPAN>
<SPAN class="keyword token">var</SPAN> gpResult <SPAN class="operator token">=</SPAN> <SPAN class="keyword token">await</SPAN> Geoprocessing<SPAN class="punctuation token">.</SPAN><SPAN class="token function">ExecuteToolAsync</SPAN><SPAN class="punctuation token">(</SPAN><SPAN class="string token">"CreateRasterDataset_management"</SPAN><SPAN class="punctuation token">,</SPAN> args<SPAN class="punctuation token">,</SPAN> env<SPAN class="punctuation token">,</SPAN> can<SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

When tool executing, program crashes. If I try to create raster dataset manually in ArcGIS Pro, ArcGIS Pro crashes.

How can I create raster dataset in GDB?

MaxMax2

OK, but I need to support earlier versions too. In my case I can easily work around the problem using WGS84 spatial reference. So just instead of default map's spatial reference I specify WGS84 (from added layer with this SR) and tool works.

Thanks for fixing this in 2.4.