Hi @fguru! After reaching out to our internal team, we got to know that this is now an intentional behaviour because the team had to change how the response is encoded to a scheme where strings can’t be null.
We would request you to please update your code to handle all false values (e.g: empty and null). The team should soon share the details for this change.
We hope this answers your question.