fix(android): handle setDataProcessingOptions params correctly to avoid crash

[oscb]

Fixes #255

• Changed the argument types of setDataProcessingOptions method in the Android Native Module, replacing String[] for ReadableArray.
• Removed @Nullable as the TS types don't support nullable
• Removed setDataProcessingOptionsExtra and merged the country and state options into the base method as the setDataProcessingOptionsExtra is not being used in RN, yet the method supports country and state options.

Test Plan:

Verified in the generated Example app by adding the call the method after initialization:

// Ask for consent first if necessary
// Possibly only do this for iOS if no need to handle a GDPR-type flow
Settings.initializeSDK();

Settings.setDataProcessingOptions(['LDU'], 0, 0);

Verified the app compiles and runs, not crashing with the previous error.

[mikehardy]

Looks great - thanks for patching this up. Just pending CI now but I am curious - does it work on iOS? I guess if the NSArray and NSStringArray types are compatible that one just works already?

[oscb]

I guess if the NSArray and NSStringArray types are compatible that one just works already?

Yea, I believe NSStringArray is a typedef to NSArray<NSString *> in the React Native code.

[github-actions]

🎉 This PR is included in version 8.0.5 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀