It is ya. To replicate the bug migrate the version 1.0.4 to a new 4.17 project and you should get the same error.