Thanks [mention removed]! Glad we got to the bottom of the root cause. Would you be able to reply here with the work around that you decide upon? I’d be keen to merge that in favour of my work around.
“In the meantime, you should be able to simplify your workaround by only calling FinalBundlePath.FixupCoreRedirects()” - Yeah, I thought about this, I ended up going for the full thing out of safety.
“Or, if you resave the original asset that had the issue in the editor it should go away as that also calls FixupCoreRedirects” - Yes, this is definitely a fix however, due to the lack of reporting it’s not trivial to know which asset needs resaving, if there was a clearer error message stating which asset contains the bad reference then we would probably just do that instead however, it’s not always possible to resave all affected assets when applying a redirector so, some kind of code solution is needed.