For the following pipeline:
There is a possible workaround for this:
Here the server has no issues with calling native code function.
Looks like little extra logic should be able to handle such cases even if hard to fix in the core. Making the error message more readable would certainly help as well.