[x] Are you changing anything with the public API?
Yes, this should be merged for a subsequent release, after #143 has been released on its own.
[x] Are your changes backwards compatible with previous SDK Versions?
No, this should get merged by or before major version 1.0.
Changelog / Code Overview
Remove profile keys corresponding to identifiers.
Test Plan
Confirmed that with the deletion, you can't call setProfileAttribute with identifier keys, unless you go out of your way to use a custom key with a value like "email". Even then, I kept the little patch in the swift bridge code from the previous PR, so that would still get routed to the explicit setter on iOS like it does on Android.
Description
Following #143, remove the deprecated keys
Check List
Changelog / Code Overview
Test Plan
Confirmed that with the deletion, you can't call
setProfileAttributewith identifier keys, unless you go out of your way to use a custom key with a value like"email". Even then, I kept the little patch in the swift bridge code from the previous PR, so that would still get routed to the explicit setter on iOS like it does on Android.Related Issues/Tickets
143
CHNL-6998