You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, a developer must resupply all email, postal and phone fields back to the library when updating them.
So, if a dev wants to update or add an email address, they must resupply all.
This might be ok, but I'm interested in the potential issues. Are there any? What if the order of the addresses change when sent back to the developer? If a developer was using postalAddresses[0] and then saves, but iOS/Android send back the addresses in a different order, could that be an issue?
The text was updated successfully, but these errors were encountered:
Currently, a developer must resupply all email, postal and phone fields back to the library when updating them.
So, if a dev wants to update or add an email address, they must resupply all.
This might be ok, but I'm interested in the potential issues. Are there any? What if the order of the addresses change when sent back to the developer? If a developer was using postalAddresses[0] and then saves, but iOS/Android send back the addresses in a different order, could that be an issue?
The text was updated successfully, but these errors were encountered: