so true story...our backend at one point sent fields that are null in our REST API responses but then at some point took that out. It was inconsistent which APIs did what....depending on who configured which API. When they finally took out the null fields from the responses, web/iOS blew up of course because they treated the dictionaries as tri-state.... exists/null/missing. And on the Android side, we were using a streaming deserializer which was dependent on the order of fields 🤦♂️ . Yes, you can imagine the carnage when this change happened 😞
Luckily we could version the APIs and config for this...but consistency is important IMHO...