fix(android): handle setDataProcessingOptions params correctly to avoid crash #256
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.
Fixes #255
setDataProcessingOptions
method in the Android Native Module, replacingString[]
forReadableArray
.@Nullable
as the TS types don't support nullablesetDataProcessingOptionsExtra
and merged thecountry
andstate
options into the base method as thesetDataProcessingOptionsExtra
is not being used in RN, yet the method supportscountry
andstate
options.Test Plan:
Verified in the generated Example app by adding the call the method after initialization:
Verified the app compiles and runs, not crashing with the previous error.