Then the expected behaviour (as per v1 SDK) is to merge the externalId of both the identify events giving higher preference to the second identify event externalId. The final payload will look like this:
ISSUE: In v2, this wasn't the case, it was simply adding both identify externalIds values and no merging was taking place. So the externalId data was incorrect.
About the fix
We have solved the merging issues of the externalId's and added new test cases.
Type of change
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
Checklist:
[ ] Version upgraded (project, README, gradle, podspec etc)
[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have added unit tests for the code
[ ] I have made corresponding changes to the documentation
About the issue
I observed an issue while setting the
externalId's
in identify event. Suppose when two identify events are made:Then the expected behaviour (as per v1 SDK) is to merge the externalId of both the identify events giving higher preference to the second identify event externalId. The final payload will look like this:
ISSUE: In v2, this wasn't the case, it was simply adding both identify externalIds values and no merging was taking place. So the externalId data was incorrect.
About the fix
We have solved the merging issues of the externalId's and added new test cases.
Type of change
Checklist: