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
Performing an update operation on a RawContact (or the parent Contact) and you have removed one or more group memberships from the RawContact, then for each group membership removed...
the group membership may not be deleted
arbitrary data (e.g. email, phone, relation, etc) may get deleted instead
For example, given the following rows in the data table;
## Data table (group membership rows, data1 refers to the groupId)
Data id: 1, data1: 3
Data id: 2, data1: 4
## Data table (arbitrary data rows, which could be email, name, etc)
Data id: 3
Data id: 4
If the Update or ProfileUpdate API are used such that the group membership with data id of 1 is removed from RawContactEntity.groupMemberships, then the data row with id of 3 is deleted instead of data row with id of 1.
The reason this occurs is because, in code, the groupId is mistakenly used to delete a data row id 🤦 🤦 🤦 🤦 🤦
Solution
Delete the data row with the corresponding group membership data row id instead of a group id... lol
The text was updated successfully, but these errors were encountered:
Problem
Performing an update operation on a RawContact (or the parent Contact) and you have removed one or more group memberships from the RawContact, then for each group membership removed...
For example, given the following rows in the data table;
If the
Update
orProfileUpdate
API are used such that the group membership with data id of 1 is removed fromRawContactEntity.groupMemberships
, then the data row with id of 3 is deleted instead of data row with id of 1.The reason this occurs is because, in code, the groupId is mistakenly used to delete a data row id 🤦 🤦 🤦 🤦 🤦
Solution
Delete the data row with the corresponding group membership data row id instead of a group id... lol
The text was updated successfully, but these errors were encountered: