Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
馃敼 JIRA Ticket(s) if any
鉁忥笍 Description
The updateEmail method in the RN SDK does pass down the
onFailureHandler
oronSuccessHandler
that are available inthe Native SDKs -> expose these methods to the RN side.
Scenario and Use Case
When launching the app the an 'anonymous' user is created using the
setUserId
method. In the current implementation if a user logs in we will want toupdateEmail
orsetEmail
based on if the user's is currently registered with Iterable. Because there is no way to know this before, we will have to assume that we will want to update the user's email and associate a 'non-placeholder email address with that user'. However if we try andupdateEmail
on a user's email address that already exists in Iterable theupdateEmail
call will fail silently because theonFailureHandler
has not been passed down.Resolve a promise back across the RN bridge with the message from the failed API call. So that we can then
setEmail({theEmailTheUserHasLoggedinWith})