Temporarily fix by swizzling resourcePath. But I think it's probably a bug of Matal.framework

Sorry for my late reply, I have created a feedback with number FB9022420, thanks! Indeed this sounds like a bug in the Metal framework. Please create ticket with Feedback Assistant. If you post the number back here I will able to get it to the right engineers more quickly.

Because our project targets to multiple platforms, So shaders are compiled at runtime. We analyzed call stack of newLibraryWithSource, it will call TLLibraryBuilder::newLibraryWithSource which acquired resourcePath of mainBundle to serve as the working directory to compile shaders(a parameter named -working-directory). So I think there are some relationships between bundle path and shader compilation. Our workaround is swizzling resourcePath to "." when call newLibraryWithSource.

sorry for typo in above link, try this: https://github.com/FinleyPan/Metal_newLibraryWithSource_Test

Cool! Look forward to your fix :)