-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Allow any userIdentificationType to be used when initializing kit #48
fix: Allow any userIdentificationType to be used when initializing kit #48
Conversation
2f551bf
to
dd4c425
Compare
@@ -792,10 +794,13 @@ var constructor = function () { | |||
braze.addSdkMetadata(['mp']); | |||
primeBrazeWebPush(); | |||
|
|||
if (forwarderSettings.userIdentificationType === 'MPID' && mParticle.Identity != null && mParticle.Identity.getCurrentUser().getMPID() != null) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we're no longer referencing forwarderSettings
, we should remove it from the function parameters.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is still being passed to openSession
at the bottom of this function
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ooof. Missed that.
Co-authored-by: Alex S <[email protected]>
@@ -792,10 +794,13 @@ var constructor = function () { | |||
braze.addSdkMetadata(['mp']); | |||
primeBrazeWebPush(); | |||
|
|||
if (forwarderSettings.userIdentificationType === 'MPID' && mParticle.Identity != null && mParticle.Identity.getCurrentUser().getMPID() != null) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ooof. Missed that.
Instructions
development
- Since this is Braze and there is a v3 and a v4, this does not apply as we need to manually releaseSummary
Previously we allowed a user to be identified on initialization only if they chose
MPID
as theiruserIdentificationType
. This prevents customers from being able to use kit forwarding rules in Braze if they have any otheruserIdentificationType
picked. Removing this constraint fixes that.Testing Plan
Added a test setting email to be the
userIdentificationType
Reference Issue (For mParticle employees only. Ignore if you are an outside contributor)