@Septiem, please see this thread for more info about the issue:
This is fixed starting with the SDK 4.25.3.