The custom fields with null value were giving the custom field key itself as a value instead, it's fixed now and it returns null as it should.
(Due to automation issues, the changes are available in this version, but the changelog entry is available on v17.5.1.)